Skip to main content

What this is

The Web Pixel/Web IFrame/App Pixel source brings event data into Zeotap CDP from your websites, emails, advertisements and mobile apps. Pixel files, also known as tracking pixels or web beacons, are small, invisible elements embedded within web pages to collect information about user behaviour and interactions. They are typically implemented using HTML code, JavaScript or a combination of both, and they collect data without significantly impacting the user experience, as they are generally invisible to the visitor. The source comes in three variants, which you pick when you create it: the Web Pixel API and IFrame data sources under the Website Events category, and the App Pixel API data source under App Events.

How pixel sources work

A pixel fires a request each time the event it is attached to occurs. The request carries the event information and is recorded against the write_key provisioned for the source, so every pixel you create under a source is attributed to that source on ingestion. For example, a FinTech company can use web pixel files to track user interactions on their website, emails and advertisements. By embedding pixel codes within these digital assets, the company gathers data on user behaviour such as clicks, form submissions and page visits. That data can then be used to analyse user engagement, optimise marketing campaigns and personalise financial product offerings, ultimately improving the user experience and increasing customer satisfaction in a non-intrusive manner. Within a source you can create one pixel per event, a single generic pixel that covers many pages, or a masked pixel that carries its properties as a base64-encoded payload. See Implement the Pixel Source for the global properties and the pixel types.

Choose between the Web Image Pixel, App Image Pixel and iFrame

The following table explains the difference between the three variants:
Cookie sync is pre-configured against the write key of every source in your organisation, and the channel cookies are mapped to the Zeotap cookie and to any user identifiers you send. Contact your Customer Success Manager (CSM) for activation or to configure preferred partners. For the full mechanism and the cookies Zeotap CDP sets, see Understanding Cookies. Third-party cookies, and the cookie syncs that depend on them, are being phased out by major browsers — see Third-Party Cookie Deprecation.

FAQ

Choose by where the events happen: the Web Pixel API or IFrame data source for website, email and advertisement traffic, and the App Pixel API data source for mobile app traffic. Between the two website variants, the iFrame tag responds with multiple image tags and can therefore cookie sync with several platforms from one call, while the Web Image Pixel syncs with one partner per call.
Yes. Create one source for each unique origin, so a website and an app are two separate sources. Keeping them separate keeps write keys, catalogues and delivery traffic separated per origin. See Sources.
Open the source from the SOURCES listing page. The source detail view shows the snippet code and the authorisation key, and the IMPLEMENTATION DETAILS tab is where you add global properties and create the individual pixels.

Next steps

Last modified on November 17, 2026