This article explains how to add custom tracking pixels to your experiences. Tracking pixels are useful for understanding user behavior, measuring conversions, and retargeting specific audiences. While the Vendor Pixel Tool allows you to add several different pixels on your own, you can submit a custom request if you need a vendor not available in the tool.
How It Works
All experiences are single-page applications that function within a browser without requiring a page reload between screens. Because all screens share the same URL, the main HTML for a tracking pixel loads only once when the experience initially loads. Specific events can be set to trigger throughout the experience. Events can fire when a screen loads (On Load) or when a response is submitted (On Response).
Adding custom tracking pixels
To request the implementation of a custom tracking pixel by our team, follow these steps:
Reach out to the Support team. You can contact them via the in-platform chat or email to submit your request.
Provide the initialization script and event descriptions. Share the necessary HTML code snippet and clearly describe the specific events in the experience that should trigger the pixel to fire. Examples of events include when a user clicks a button, marks a checkbox, or loads a page.
(Optional) Review recommended basic events. If you are unsure which events to track, the team can recommend basic events such as:
jebbit_engage: Trigger when a user clicks the first button.
jebbit_lead: Trigger when a user submits their lead information.
jebbit_outcome: Trigger when a user reaches the outcome screen.
jebbit_complete: Trigger when a user reaches the last screen.
jebbit_redirect: Trigger when a user clicks the last button that redirects them back to your site.
Specify your experience embedding method. Inform the team if you plan to embed your experience onsite or not. This detail helps determine the recommended implementation method to avoid cross-domain tracking issues.
Allow time for implementation. After submitting your request, allow up to seven business days for the team to review and implement the pixels. Submitting your request well in advance is recommended.
Frequently Asked Questions
What is the purpose of adding pixels to an experience?
Pixels are useful for tracking user behavior, conversions and re-targeting specific audiences.
I've embedded a Jebbit experience that has pixels on my website, but I'm not seeing the pixels fire.
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 brand account and then update your iframe snippet so that the Jebbit experience and your parent site share the same domain.