Events FAQ

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.

How do I stop an event pixel from firing? What does the disable button in the Events screen do?

If you no longer want data to be collected on an event pixel, the event pixel must be removed from the site that it was tagged on. Disabling an event pixel via the UI will only remove it from being available in UI reports. Disabling an event pixel in the UI will not stop the pixel from firing on your site. Event pixels that remain on sites and continue to fire even after being disabled in the UI will continue to count towards your billed data collection events (DCEs) until it either stops firing or is removed from the site completely.

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.


Please note that the JavaScript version of the pixel must be used, and your unique Control Tag must also be firing on the page(s). This is not available for events captured outside of the client's environment (i.e. where the Control Tag is not deployed).

Can event pixels be used within an iFrame?
Yes, the HTML version of the event pixel can be used. The JavaScript version will not function properly, as the Krux Control Tag is in the parent window.

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.

What is the difference between the JavaScript event pixel and the image event pixel?
The JavaScript event from a particular publisher account should only be deployed on pages where that publisher's Control Tag is present. Javascript pixel use cases include:

  • 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.

Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.