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

To this end, a code of a third party is loaded into the ad server. This code is loaded / displayed before any delivery logic of the ad server accesses the AdServer. The code executes and returns information to the AdServver back. The ad server can then use parameters via targeting to campaigns auszusteuern this information. Proceed as follows:

1. In Settings> pretargeting settings a new pretargeting to
2. Put in any case, a synchronous and asynchronous code (!)
3. The synchronous HTML code must be (it must not be mixed) in each case synchronously. The synchronous code should load the code of the third party and then the function window.asm_pretargeting (x) call. Where x is a string in the form of URL parameters (a = 1 b = 2 c = 3 ...)
4. The asnychrone HTML code also calls the code of a third party and must then call the function window.asm_async_data.addPretargeting ( "% placementid%", x). Please note that placementid%% is a macro that needs to be replaced by AdSpirit - hence the call to the function must necessarily take place in stored in AdSpirit code.
5. Create a campaign and choose among parameters targeting the source, the applied pretargeting. As a parameter name and value name / value can then be used, which were handed over by the third party to the two functions (in this example, the x).

Pretargeting via CSV

Here are two CSV be uploaded to the ad server. The CSV 1 (CSV for matching) includes a list of values ​​to be compared (eg, URLs, or user IDs) and for each matching a list of IDs. The CSV 2 (CSV data) includes a list of all CSV 1 occurring IDs and associated values ​​(eg name). The ad server will then before delivery for example, the URL or the user ID to compare with the matching list and raussuchen to those found in matching IDs matching values ​​from the value list. To do this, follow these steps:

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.

Example CSV for matching:
meineseite.de/,1;3
meineseite.de/sport/,4;5
meineseite.de/finanzen/,1;2;4

example CSV values:
1, General
2, Finance
3, News
4 Men
5, sports

Please note that the matching only exaktive hit takes (ie, the URL in the matching must exactly match the referrer match). URLs are shortened by http:// and www. before matching.

 https://support.adspirit.de/hc/en-us/articles/360022385052

Keywords: pretargeting, headerbidding