Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

AdEngine supports custom targeting for each ad-unit served. This can be done by setting a value between 1-100 to the snigelPubConf.adengine.targeting.key1.

Examples

Associating article pages to their authors to measure the impressions they have generated

Sites might have multiple authors writing articles, and it is required to know how many impressions each individual has generated with their content, that's possible using the Custom Targeting.
For example, there are three authors Lili, Robin and Barney, if each one of them is associated to a number, it can be used to set the target using those numbers and fetch reports with the individual data for each author.

Find out trends for different page categories

It's important to know which page categories are generating views and what categories are not so that we can focus more on the first, that's possible using the Custom Targeting.
For example, there are pages related to Computing and Technology, and on these pages are the following categories News, Sales and Reviews. Each category has a a unique number assigned that is used for targeting, to then fetch reports with the individual data for each category.

Syntax

Custom targeting can be configured using AdEngine Declarative Configuration.
Setting an integer from 1-100 in the snigelPubConf.adengine.targeting.key1 associate that value to all the units served by AdEngine on this page.

<script data-cfasync="false" type="text/javascript">
  window.snigelPubConf = {
    "adengine":{
      "targeting": {
        "key1": Number
      }
    }
  };
</script>
<script data-cfasync="false" async src="https://cdn.snigelweb.com/adengine/**site.domain**/loader.js" type="text/javascript"></script>

Note:

  • "key1" must always have a single number (1-100) associated, eg: "key1": 54.

  • Please let your account manager know in case you you need more key-value pairs.

  • Replace **site.domain** with the actual site domain

  • No labels