AdForm publisher integration instructions

In order to use AudienceProject data in AdForm SSP and PPAS for targeting purposes, a few steps are needed:

  1. Modify the placements code snippet
  2. Add the AudienceProject code snippet to the website
  3. Configure AdForm account

This guide will describe how to setup the integration and how the data can be used.

Configuring the data synchronisation

1. Modify placements code snippet

AdForm has a synchronous and an asynchronous version of the placement code.

First, you need to get the asynchronous version of the code.

Second, you need remove the last <script> tag that loads // (adx.js going further), so the code looks like this:

<!-- Adform publisher tag -->

<!-- Tag for Default Publisher - Test placement placement -->

<script data-adfscript=""> </script>

You can still use all snippet customizations that are documented. The key thing that adx.js should not referenced on the page - it will be injected by the AudienceProject code snippet.

If you do not modify all placements on page, so some of them still load adx.js, targeting data may be not applied.

2. Add the AudienceProject code snippet to website

The AudienceProject script is simple and looks like this:


<script src="//" async></script>


You should place it in beginning of the web page, e.g. in the <head> tag or in the beginning of <body>.

It will set targeting data for all non-initialized placements through AdForm setTargeting API and load adx.js that will request ads for your placements.

In order to ensure that Ads will be requested whatever happens it is required to place additional script to website that will ensure that adx.js will be added.


It is recommended to put this code right before </body> tag. If you want to concat both tags into one it is recommended to increase 1000 to 2000. This number is actually the threshold (in milliseconds) to wait for targeting data and requesting adx.js.

3. Configure AdForm account

AudienceProject only sends obfuscated data to AdForm, for instance key ap_a stands for Gender and key 1 stands for Male.

It is possible to apply human readable labels on keys and values by following this documentation. Keys, values and labels for them will be send to you together with contract details.

Not all keys and values will appear immediately. Keys and values will appear when users from different segments visit the pages where the data synchronisation is running.

Using the targeting data

When creating line items it will be possible to set targeting criteria





Powered by Zendesk