How to embed my retargeting pixel?
Last updated
Last updated
After setting up and validating your Brand lift, go to the “Pixels” section to retrieve them. We provide pixels to be used on desktop, mobile or CTV environments, wherever your ads are displayed. The pixel collect IP addresses, Device ID, cookies... a single integration is therefore necessary. To streamline DSP integration, the pixels are generated in a DSP-specific format.No modifications are required.
Select from the list the DSP you want to run your ad campaign on;
If your DSP is not listed, select the “Other” option
Once the pixel has been generated, click on the “Copy” button to copy the pixel version adapted to your DSP.
The content of the pixel below is adapted for use within "TTD" DSP
(The Trade Desk). Example : https://www.axprtbggl.com/ebeacon consent=%%TTD_GDPR_CONSENT_STRING%%&l=18489&m=i&redir=https%3A%2F%2Fwww.rtghd.com%2Febeacon%3Fconsent%3D%%TTD_GDPR_CONSENT_STRING%%%26l%3D18486%26m%3Du%26udid%3D%%TTD_DEVICEID%%%26redir%3Dhttps%253A%252F%252Fsecure.adnxs.com%252Fseg%253Fadd%253D36976425%2526gdpr_consent%253D%%TTD_GDPR_CONSENT_STRING%%
After retrieving your pixel:
Paste the pixel directly (without modification) into the pixel section of your DSP.
Once you have configured and validated your Brand lift, go to the "Exposure data" tab to retrieve it. We provide pixel for use on all desktop, mobile or CTV environments on which your ads are broadcasted. The pixel collect IP addresses, Devices ID, cookies... a single integration is required.
Pixels generated by selecting the "Other/Don't know DSP" option are not adapted to the format of your DSP. Follow the steps below to simplify the DSP integration process.
If your DSP is not listed, select the “Other” option.
Once the pixel has been generated, look at the the macros in bold to simplify the integration step within the DSP.
Click on the "Copy" button to retrieve the pixel.
Indicate the DSP you use in the field provided.
This will allow our teams to identify potential DSPs to add to the list.
It is therefore necessary to make the following changes before integration :
Example : https://www.axprtbggl.com/ebeacon?consent={{GDPR_CONSENT_STRING}}&l=18489&m=i&redir=https%3A%2F%2Fwww.rtghd.com%2Febeacon%3Fconsent%3D{{GDPR_CONSENT_STRING}}%26l%3D18486%26m%3Du%26udid%3D{{USER_ID}}%26redir%3Dhttps%253A%252F%252Fsecure.adnxs.com%252Fseg%253Fadd%253D36976425%2526gdpr_consent%253D{{GDPR_CONSENT_STRING}}
After retrieving your pixel:
Replace all the parts in bold:
- {{GDPR_CONSENT_STRING}} by your DSP's consent macro.
- {{USER_ID}} by your DSP's device ID macro.
Paste the adapted version of the pixel directly into the section of your DSP dedicated to pixels.
⚠️ To find out more about the DSP macro, please consult the DSP documentation or contact your account manager.
The content of the DV360 pixel shown below is generated for use with CM only.
Example : https://www.axprtbggl.com/ebeacon?consent=${GDPR_CONSENT_4594}&l=18489&m=i&redir=https%3A%2F%2Fsecure.adnxs.com%2Fseg%3Fadd%3D36976425%26gdpr_consent%3D${GDPR_CONSENT_550}
After retrieving your pixel:
Go to the CM platform, then create a new ad creative, and select the Vast (Video Instream) format.
Scroll to the bottom of the “Creative” page, and paste the pixel.
CTV pixels are generated following the selection of "Connected TV" media when configuring the Brand lift, and are adapted to this type of environment. Follow the steps below to simplify the process of integrating the CTV pixel within your DSP.
Brand lift Set up - "Media" selection step
Once you have configured and validated your Brand lift, go to the "Exposure data" tab to retrieve it. We provide pixel for use on all desktop, mobile or CTV environments on which your ads are broadcasted. The pixel collect IP addresses, Devices ID, cookies... a single integration is required.
Pixels generated by selecting the "Other/Don't know DSP" option are not adapted to the format of your DSP. Follow the steps below to simplify the DSP integration process.
Select from the list the DSP you want to run your ad campaign on. If your DSP is not listed, select the “Other” option
Once the pixel has been generated, look at the the macros in bold to simplify the integration stage within the DSP.
Click on the "Copy" button to retrieve the pixel.
Indicate the DSP you use in the field provided.
This will allow our teams to identify potential DSPs to add to the list.
The content of the pixel below is adapted for use within "TTD" DSP (The Trade Desk).
Example: https://www.axprtbggl.com/ebeacon?consent={{GDPR_CONSENT_STRING}}&l=18930&m=i/
After retrieving your pixel :
Paste the pixel directly (without modification) into the pixel section of your DSP.
Pixels generated by selecting the "Other/Don't know DSP" option are not adapted to the format of your DSP. Follow the steps below to simplify the DSP integration process.
Example : <img src="<https://www.axprtbggl.com/ebeacon?consent={{GDPR_CONSENT_STRING}>}&l=12157&m=i" height="1" width="1" />
After retrieving your pixel :
Replace the part in bold: {{GDPR_CONSENT_STRING}} by your DSP's consent macro.
Paste the adapted version of the pixel directly into the section of your DSP dedicated to pixels.
It is not necessary to replace the consent macros if you are broadcasting your campaign in a zone outside the European Union.
Custom macros are generally mentioned in the DSP documentation.
DV360 does not allow user device IDs to be retrieved during an INAPP campaign. It is therefore not possible for Happydemics to retarget individuals exposed to your campaign.
If you have a VAST creative, the pixel must be integrated via the DSP CM (Campaign Manager).
If you use a VAST creative and your DSP does not allow you to implement the pixel directly, please integrate it into your adserver (dcm ..)
Embedding the retargeting pixel works the same way as for a regular impression pixel. Each DSP, ad-server or website specialized in managing advertising campaigns has a dedicated section for embedding the pixel. Once you’ve retrieved the pixel available on Happydemics’ platform, simply copy and paste it into the dedicated section of your ad-serving software.
.avif?alt=media&token=5f62e7f7-897a-44dc-b938-93c3c3f73fd8)
.avif?alt=media&token=0d88e9ce-7a09-4803-8a2b-f690d6329dd0)
