Email pixel
An invisible 1×1 image that counts how many times an email is opened. It never redirects. Each time the email app loads the image, one deep_link_open event goes to Mixpanel.
Set it up
- New link → Opens on: Email open pixel.
- Give it a title, for example Weekly report email.
- Under Dynamic params, list what you want recorded:
email. - (Optional) Image URL: a public
httpsimage to show in the email instead of an invisible dot. - Open the link, use Customize link to fill in the values, and Copy email snippet.
The URL
The pixel is served by the API, not the link domain:
https://prod-api.aquagen.co.in/api/user/deepLink/pixel/ABCD1234
Add details the same way as any link, with base64 data (default) or plain query params:
…/pixel/ABCD1234?utm=email,weekly&data=eyJlbWFpbCI6ImphbmVAZXhhbXBsZS5jb20ifQ
…/pixel/ABCD1234?utm=email,weekly&email=jane@example.com
If both are present, the plain param wins. Only names listed under Dynamic params are recorded.
In the email
Without an image URL (invisible):
<img
src="…/pixel/ABCD1234?utm=email,weekly&data=…"
width="1"
height="1"
alt=""
style="display:none"
/>
With an image URL (visible), leave out the size and hiding:
<img src="…/pixel/ABCD1234?utm=email,weekly&data=…" alt="AquaGen" />
Build one URL per recipient so each open is tied to a person.
What is recorded
| Property | Value |
|---|---|
id, title | From the link |
utm | From the URL, or the link's defaults |
| your params | Only the ones listed under Dynamic params |
| Mixpanel user | The email param if present, otherwise email_pixel |
The visitor's IP address is not sent.
When it is not counted
| Link state | Counted? | Image |
|---|---|---|
| Live | Yes | Your image, or the transparent pixel |
| Off | No | Your image still shows, so sent emails don't break |
| Deleted or unknown | No | Nothing |
Limits to expect
- Counts are approximate. Apple Mail loads images for every email, even unopened ones. Gmail loads them through its own proxy. Outlook and others block images until the reader allows them. Read it as a trend.
- PDFs rarely load the image, so only the email body counts.
- Repeat loads (reopening, previews) can create several events. Count distinct users, not events, for unique opens.
- Anyone with the URL can load it, so a count can be forged.