Table of Contents
Setting up Your Cuebiq Pixel
Please follow the instructions listed below in order to properly implement our 1x1 tracking pixel to your campaign creative. The following parameters come prepopulated with placeholder values (i.e. PLACE_DID_HERE) and should be replaced with the proper macros/hardcoded value:
- DSP: Field to identify which DSP the pixel will be placed. This will be automatically populated when creating your pixel after having completed the initial campaign setup.
- did: plain device ID macro. This is a mandatory value for campaigns running any in-app inventory. If the campaign is running cross device inventory then you may leave the placeholder as is or can remove the placeholder.
- lat: latitude macro, if applicable.
- lng: longitude macro, if applicable.
Note: Any macros used should be native to the environment that the pixel is implemented in. i.e., if implementing the Cuebiq pixel at the AdServer level, the pixel should include AdServer macros. Having DSP macros in the pixel for instance for a pixel that’s implemented at the AdServer level will cause pixel misfires.
The Cuebiq pixel has 8 different customizable parameters (SIDs) that can be filled with any kind of macro, combination of macros, or fixed text string that could be useful for real-time campaign reporting and/or optimization. Any value input in these parameters can be measured. The 8 customizable parameters include:
- Creative Name
- Creative Type
- Placement ID
- Publisher ID
The Cuebiq platform and downloadable CSV files will display their insights for each single parameter received through the pixel. Here is an example of a Cuebiq pixel with placeholder parameters included:
Note: Fields are added to the pixel during pixel generation on Cuebiq’s end, and only fields specified upfront are included in the pixel. Please specify with your Cuebiq representative which fields you wish to have included/added in your pixel(s).
Q: Can I use any value when hardcoding?
A: SIDs should not include white spaces or dashes, otherwise the URL could break and Cuebiq wouldn’t receive correct data. Please avoid using special characters and only use letters, numbers, and “_” or “-”.
Q: I see fields for creative, placement ID, etc. What are the other SID fields for?
A: The SIDs can be used for any parameter not included in the prepopulated options. Almost any macro can be supported (please check with your Cuebiq representative). Some examples might be a zip code macro or hardcoded audience targeting tactic.
Q: What if I don’t need all of these parameters?
A: If you don’t need a parameter, you have a few options - it can either be left as is (it won’t affect your reporting), you can remove the PLACE_X_HERE placeholder, or you can remove the entire parameter (&placementid=PLACE_PLACEMENT_ID_HERE).
In your Measurement report, you will be able to use the Advanced Comparison Tool to compare up to two parameters at a time. The CSV download option will allow you to compare all included parameters. Examples below:
Q: Do I delete the brackets when replacing a value in the pixel?
A: Yes, please remove the brackets in the fields.
Q: What can I use instead of space?
A: Instead of white space or dash, you can substitute with an underscore “_”, e.g. SID_WITH_NO_WHITESPACES. See below some examples of using SID parameters.
Q: Is there a character limit to how long the hardcoded value can be?
A: Cuebiq recommends staying under 30 characters.
Q: What if multiple partners are running on the campaign?
A: If there are multiple partners running and you need to decipher between them, Cuebiq will hardcode the partner name in a SID value. If it needs to be de-identified, Cuebiq will implement a numerical ID and provide you with the key.
Q: What if I am not interested in using SIDs and only need a pixel, is that feasible?
A. Cuebiq can provide a blank tag with no parameters included or the tag provided (regardless of whether there are parameters or not) can be implemented as is. Not removing/revising the SID fields will not impact the data in reporting.
Q: The pixel I was sent is not image wrapped. How do I format it so it can be image-wrapped?
A: If you are needing an image-wrapped tag, please reach out to your Cuebiq representative who is happy to request an img wrapped tag be generated from our Ops team.
Q: Can I implement the Cuebiq pixel inside another tag?
A: Please avoid wrapping the Cuebiq pixel within another tag. Doing so will not allow the Cuebiq pixel to fire correctly.
Q: What are some SID strategies I can use for my report?
Here are some examples of different SID values:
- Campaign 1
Goal: Optimize the campaign focusing on the creatives that perform best. The best way to do this would be to implement a creative macro in the pixel's creativename and/or creativetype parameter, as below (these values can also be hardcoded if no macro is available):
- Creative Pixel:
- Campaign 2
Goal: Optimize the campaign focusing on the tactic that performs best. The best way to do this would be to use a fixed test string as a SID parameter for each tactic, as below:
- Tactic 1 pixel:
- Tactic 2 pixel:
- Campaign 3
Goal: Optimize a campaign that is targeting three audiences and using two creatives. The best way to do this would be to use a fixed string for audience, in the SID parameter, and add the creative macro to the creativename and/or creativetype parameter. See below:
- Audience 1 pixel:
- Audience 2 pixel:
- Audience 3 pixel:
- Campaign 4
Goal: Optimize a campaign by DMA but also by publisher ID. Our V2 pixel will automatically send back the DMA that the impression was served in, so there is no need to use a SID slot for a DMA. You can place a publisher ID macro in the Publisher_ID.
- Example pixel:
Cuebiq Pixel Best Practices
When revising a Cuebiq pixel with values or implementing the pixel in the respective platform, there are some best practices we recommend you take into consideration:
Revising the Pixel
- Avoid blank spaces or special characters in the pixel. Pixels should only include letters, numbers and/or underscores or hyphens "-" "_".
- Please do not add additional parameters to the pixel. The parameters are predefined and changing/adding new parameters will not pass the data back correctly.
Implementing the Pixel
- The Cuebiq pixel does not fire correctly when wrapped in another tag, please avoid wrapping the Cuebiq pixel in another tag.
- It's imperative that the macros implemented in the pixel be those of the platform the pixel is implemented in. We strongly advise not to implement foreign macros to the environment the pixel is implemented in (ex. having DSP macros with the pixel implemented in the AdServer).
- It's advised for multi-partner campaigns where there are multiple partners serving media, for the Cuebiq tags to be applied at the AdServer level (ex: DCM). This will allow for consistent values captured through the tags. If tags are implemented at the DSP level there is less control over ensuring consistent values are passed back into the Cuebiq platform. Agencies also generally have more control over the media and values in the Cuebiq platform with owning the pixel implementation AdServer level.
- Should a partner only be able to implement at the site served level, this option will work, although it's advised that the SID values be carefully considered to ensure consistent values across partners.