What are event pixels?
Event pixels are used to capture any user-based interaction. Examples include clicks, downloads, and form data. These interactions can be used to understand how people respond to prompts on a page, content, advertising messages, or as a means for additional first party data capture.
Can click events be used in real-time segments?
Yes. Real-time segments are evaluated in-browser, so almost all attributes (including events) can be included as a building block.
Can event pixels be used within an iFrame?
What is the lookback window for an event pixel demographic report?
Demographic reports for event pixels are based on a 7 day lookback window.
What is the difference between uniques and total requests?
Uniques represent the number of users exposed to the pixel, while total requests represents the total number of times the pixel fired.
- Passing page variables as event attributes.
- Deploying the pixel in a form, specifically on onSubmit functions, where data is captured on user action after the page has loaded.
- Collecting additional attributes without writing custom macros
If the page does not have the relevant Control Tag deployed, the image pixel version should be used. Image pixel use cases include:
- Deploying an image pixel on a customer’s web page to retarget that traffic via a campaign.
- Deploying an image pixel on conversion pages that are on another company’s web site that does not have the Krux Control Tag deployed.
- Capturing email newsletter opens and interactions.
For more information on Event Pixel functionality and use cases, please refer to the Event Pixel and Funnel User Guide.