Otherwise known as ‘server-side’ pixels, post-back pixels are used for tracking mobile app installs. You will need to work with a third-party mobile attribution partner such as HasOffers, AD-X (Criteo), Appsflyer, Flurry, Singular, TapStream, Kochava, etc. Post-back conversion attribution pixels allow attribution servers to callback to the Pontiac conversion pixel and attribute mobile app installs that stem from Pontiac campaigns. 

Note post-backing can only be done with hosted creatives on the platform and not for third-party tags, as the ${SSP_DATA} macro needs to be populated by the creative’s ad server.

1. Create an Advertiser in Pontiac, then create a Standard Conversion Pixel.
   (Appsflyer specific note: You will need to make sure that the Conversion Pixel Name in Pontiac is the same as the SDK event name in Appsflyer. Otherwise, the conversion will not be passed to Pontiac.)
   
2. Once you create the conversion pixel, provide the pixel ID to the Third-Party Vendor, this is the number string following ‘id=’ in the pixel code.
   For example: <img src=https://secure.adnxs.com/px?id=1234567&t=2 width=”1″ height=”1″ />, the ID would be 1234567
   
3. If the Third-Party Vendor prompts you to select an origin platform for the pixel, select ‘Appnexus’ or ‘Xandr’.
   
4. The server-side pixel (post-back URL) is below, replace the ‘XXXXXXX’ with the Pixel ID from part 2. The [SSPDATA] will also need to be replaced with your third-party vendor’s click id macro.
   http://sspx-router.adnxs.net/sspx?id=XXXXXXX&sspdata=[SSPDATA]
   If your vendor requests just the endpoint, enter the following: http://sspx-router.adnxs.net/sspx and you will need to provide the parameter &sspdata, this will need to be populated by their click ID macro.
   
5. The Third Party Vendor should provide you with a URL template that they will use to track conversions. You may want to add additional macros to the URL if you wish to collect additional data, all Pontiac macros can be found here: Creative Macros
   The URL you get from the Third-Party Vendor must use the macro ${SSP_DATA} as the click ID. This click ID will be used in the “post-back” call the vendor makes to report a successful app install. If this macro is not included in the URL, Pontiac will not be able to record the conversion.
   For example:
   http://wetrackinstalls.com/serve?action=click&publisher_id=[publisher_id]&site_id=[site_id]&offer_id=[offer_id] &odin=${DEVICE_ODIN}&open_udid=${DEVICE_OPENUDID}&ios_ifa=${DEVICE_APPLE_IDA}&ref_id=${SSP_DATA}
   
6. Set the landing page of the creative (the click URL) to the URL provided by the Third Party Vendor.
   
7. Add the Pontiac conversion pixel to your Line Item to attribute conversions from this campaign.