Understand Web Pixel Source with a Use Case
For example, a FinTech company can use web pixel files to track user interactions on their website, emails, and advertisements. The company can gather valuable data on user behaviour, such as clicks, form submissions and page visits by embedding pixel codes within these digital assets. This data can 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. Note that the Pixel URL hits the Zeotap APIs with the event-related information and is recorded based on the provisionedwrite_key.
Understand the Differences Between Web Image Pixel, App Image Pixel and iFrame
The following table explains the difference between web image pixel, app image pixel and iFrame:| ACTION | WEB IMAGE PIXEL | APP IMAGE PIXEL | IFRAME |
|---|---|---|---|
| How does Cookie sync work? | The Web Image Pixel can perform only one cookie sync at a time. Thus, if you have five preferred partners, then all such cookie syncs require the pixel to be fired five times. For example, if there are five different events of a customer, then every event triggers cookie sync with a preferred partner. | The iFrame tag responds with multiple image tags, each of which is cookie sync with the platforms of your choice. | |
| How does user identification happen? | The Web Image Pixel relies on the Zeotap third-party cookie primarily for user identification. Additionally, you may send your own identifiers. | The App Image Pixel relies on the MAID that you send in the pixel. Therefore, Maid is mandatory in the App image pixel in addition to any other identifiers that you may send in the pixel. |
Note:For more information about how to create a Pixel or iFrame Source, refer here.