How to add a Gmail tracking pixel
Gmail can insert a MailPixel URL through Insert photo → Web Address (URL). We tested the full workflow with a real email. The pixel worked, but Gmail produced two proxy requests after Send and before the received message was opened. Use the activity as a clue, not a read receipt.
A manual Gmail tracking pixel is possible for an occasional test. It is a fragile workflow and its first request may be Gmail's infrastructure. For repeated sending, use the Gmail extension so you do not have to paste a remote image URL into every draft.
Add the pixel to a Gmail draft
Use the public pixel URL. Never paste the private activity link into a message.
- Create a pixel
Use the generator, give the test a non-sensitive label, then choose Copy pixel URL. Keep the activity page open in its separate tab.
- Open a Gmail draft
Write the subject and message first. In the compose toolbar, choose Insert photo.
- Choose Web Address (URL)
Paste the URL beginning with
https://mailpixel.org/p/. Wait until Gmail accepts the image, then choose Insert. - Send a controlled test
Send to an address you control before using the method in a real conversation. Do not open the public pixel URL in a browser; that creates another request.
What happened in the real Gmail tracking pixel test
The result shows why a Gmail tracking pixel is not the same as a confirmed human open.
MailPixel classified the activity as possible mail proxy requests. A proxy can fetch an image on behalf of Gmail, and caching can prevent a later view from producing a clean one-to-one event.
Do not report “the recipient opened it” from this result. Report that the hosted image was requested, then use timing and replies as additional context.
Choose the right Gmail tracking pixel workflow
The manual method and the extension solve different frequency problems.
| Workflow | Best for | Main limitation |
|---|---|---|
| Insert photo by URL | A one-off controlled test | Repeated manual steps; proxy requests can appear before a human open. |
| MailPixel Chrome extension | Regular Gmail sending | Requires installing the extension and reviewing its permissions. |
| Copy HTML | An email API or template editor with HTML source | Normal Gmail compose does not provide a supported raw-HTML editor. |
Avoid a common mistake: pasting the copied <img> tag into Gmail's visible message body displays code or plain text. If you are using normal Gmail compose, use the image URL workflow above or the extension.
Test and interpret it safely
A short checklist prevents false conclusions and accidental self-requests.
- Use a label that contains no recipient name, email address, or message content.
- Copy the public pixel URL, not the private activity link.
- Record the request count before Send and before opening the test inbox.
- Treat automated loading, forwarding, blocked images, and caching as alternative explanations.
Interface and behavior checked in Gmail on September 20, 2026. Gmail can change its compose interface and image handling. MailPixel is independent and is not affiliated with Google.