Adding Custom Tracking Pixels to your Jebbit Experiences

A tracking tag, or tracking pixel, is an HTML code snippet which is loaded when a user visits a website or opens an email. Our Vendor Pixel Tool allows you to add several different pixels to your Jebbit experiences on your own. But if you don't see the pixel vendor that you need, don't worry! You can submit a custom request to have our team add the pixels for you.

1. Reach out to the Support team via the in-platform chat, or via ‘support@jebbit.com’ to submit a request for custom pixel implementation

2. Provide our team with the initialization script as well as a description of the events that you need the tracking pixel to fire on. For example, when a user clicks a button, marks a checkbox, loads a page, etc.

3. If you are unsure of which events to track in your experience, then we can recommend some basic ones for you. Here are some events that may be helpful to track:

   1. jebbit_engage - set this event to trigger whenever a user clicks on the first button in the experience

   2. jebbit_lead - set this event to trigger whenever a user submits their lead info

   3. jebbit_outcome - set this to fire when a user reaches the outcome screen

   4. jebbit_complete - set this to fire when a user makes it to the last screen

   5. jebbit_redirect - set this to fire when a user clicks on the last button that redirects them back to your site

4. Let our team know if you plan to embed your Jebbit experience onsite or not. Knowing this will influence our recommended implementation method to ensure that your team does not run into cross domain tracking issues.

5. After you submit your request, allow up to seven business days for our team to review your request and implement the pixels on your behalf. It's always best to request a pixel implementation well in advance!

Q: How does the pixel load within a Jebbit experience?

A: All Jebbit experiences are single-page applications, which means they work inside a browser and do not require a reload between screens. Because all of the screens in your Jebbit experience share the same url, the main HTML that you provide us with is only loaded once when the Jebbit experience first loads. Throughout the experience, specific events can be set to trigger On Load (when the screen loads) or On Response (when a response is submitted).

Q: What is the purpose of adding pixels to an experience?

A: Pixels are useful for tracking user behavior, conversions and re-targeting specific audiences.

Q: I've embedded a Jebbit experience that has pixels on my website, but I'm not seeing the pixels fire.

A: It's possible that you are running into cross-domain tracking issues. This can happen if the domain that the Jebbit experience is hosted on does not match the domain to your parent site. Our team can work with your team to add the events via postMessage which will allow your team to add an event listener to your site to pick up the events that fire from the iframe. Or, you can set up a custom domain in your Jebbit account and then update your iframe snippet so that the Jebbit experience and your parent site share the same domain.

• Meta (Facebook) Self-Serve Pixel UI

• Pixel UI for Neustar

Keywords: pixels, tags, tracking, custom request, cross domain tracking, postMessage, custom domain