Pretargeting

By pretargeting Values ​​from third parties are loaded into the ad server so as to enable targeting. Application examples:

• Retargeting provider checks before delivery via pretargeting whether the user is relevant for him
• so-called header Bidding. RTB provider checks before delivery if there are bids for that impression
• Semantic Targeting: Targeting providers like the URL with their own data, thus enabling targeting

Pretargeting is possible in three ways:

1. via HTML code
2. via CSV upload
3. via Server 2 Server Request (only on request, please ask your AdSpirit support Report)

Pretargeting via HTML code

For this purpose, a third-party code is loaded into the AdServer. This code is loaded/displayed by the AdServer before any delivery logic of the AdServer takes effect. The code is executed and returns information to the ad server. The AdServer can then use this information via parameter targeting to target campaigns. To do this, proceed as follows:

1. Create a new pretargeting under Settings > Pretargeting Settings.
2. Create in any case a synchronous and an asynchronous code (!)
3. The synchronous HTML code must be synchronous in any case (it must not be mixed). The synchronous code should load the third party code and then call the window.asm_pretargeting(x) function. Here x is a string in the form of URL parameters (&a=1&b=2&c=3...).
4. The asnychronous HTML code also calls the third party code and must then call window.asm_async_data.addPretargeting("%placementid%",x). Note here that %placementid% is a macro that must be replaced by AdSpirit - the call to the function must therefore necessarily take place in the code stored in AdSpirit.
5. Create a campaign and select the created pretargeting as the source under Parameter targeting. The names/values passed by the third party to the two functions (the x in the example) can then be used as the parameter name and values.

Pretargeting via CSV

For this purpose, two CSVs are uploaded to the ad server. CSV 1 (CSV for matching) contains a list of all values to be compared (e.g. URLs or user IDs) as well as a list of IDs for each matching. CSV 2 (CSV for values) contains a list of all IDs occurring in CSV 1 and associated values (e.g. names). The AdServer will then compare e.g. the URL or the user ID with the matching list and pick out the values from the value list that match the IDs found in the matching. Proceed as follows:

1. In Settings> pretargeting settings a new pretargeting to
2. Choose a type of CSV and CSV type referrer or user ID
3. Leave the URL data, column separator (recommendation: comma), interval etc .. Please note when creating the CSV that the column separator and the separator of the IDs in CSV 1 are not the same (as an ID separator can commas or semicolons be used)
4. The data is then imported from AdServer
5. Create a campaign and choose among parameters targeting the source, the applied pretargeting. As a parameter name, please enter a "value". The value data from CSV 2 are used.

1. Create a new pretargeting under Settings > Pretargeting Settings.
2. Select as type CSV and CSV-Type Referrer or User-ID.
3. Store the URL data, column separator (recommendation: comma), interval, etc. When creating the CSV, please note that the column separator and the ID separator in CSV 1 are not the same (comma or semicolon can be used as ID separator).
4. The data will be imported from the AdServer afterwards
5. Create a campaign and select the created pretargeting as source under Parameter targeting. As parameter name please enter "value". The data from CSV 2 will be used as the value.

Example CSV for matching:
mypage.com/,1;3
mypage.com/sport/,4;5
mypage.com/finances/,1;2;4

example CSV values:
1,general
2,finances
3,news
4,men
5,sports

Please note that matching only finds exactive matches (i.e. the URL in the matching must exactly match the referrer). URLs are shortened by http:// and www. before matching.

Information on how to set up the pretargeting API

Keywords: pretargeting, headerbidding