Offline Pixels: Sending Unique IDs + Limitations
Using DY’s offline pixels is a great way to track events and information occurring on a site or page that does not have DY implemented. These pixels are sent to the DY Admin as events and can be used to create audiences, be used as goals, etc.
A pixel looks like this:
<img height='1' width='1' border='0' src='//px.dynamicyield.com/dpx?sec=[SITE ID]&name=[EVENT NAME]&props={"[FIRST PROPERTY NAME]": "PROPERTY_VALUE", value: "[MONETARY VALUE]"}&uid=[DYID]&cuid=[CUID]&cuidType=[CUID TYPE]'/>
Pixel value breakdown:
- px.dynamicyield.com: If you're using DY with the EU data center (i.e. if the URL of the Dynamic Yield console is adm.dynamicyield.eu), change the domain to px-eu.dynamicyield.com.
- sec: the section ID of the client you would like to send the events to
- name: how the event will be named in the Admin
- props (optional): used to record event properties and will come through as such in the Admin
- dyid (optional): used to identify the user’s DYID if available offsite. If unavailable, DY will look at the ‘DYID’ 3rd party cookie. Note: With recent ITP protocol changes, this cookie may not be available for all browsers
- cuid (optional): used to identify a user’s unique ID if DYID is unavailable to be passed
- cuidType (optional): the type of cuid being passed (ie: hashed email)
However, there are some limitations to how the pixels work. Below are key considerations to keep in mind when deploying an offline pixel to ensure data is reported correctly.
- Offline pixels work primarily on mainstream browsers. Mainstream browsers include:
- Chrome
- Firefox
- Safari
- Internet Explorer
- Attributing off-site events to your campaigns in experience reports:
- You must leverage user stickiness and an attribution window of 1 day or 7 days in the campaign - cannot be session-based.
- Experiences that leverage "start attribution after an event is sent" will not be able to use offline pixels.
- For dynamic allocation experiments, the offline pixel event won't appear in the audience breakdown.
Please sign in to leave a comment.
Comments
0 comments