How analytics work
This article covers the basic principles of the technology used to track opens and clicks in JungleMail for Office 365.
How opens and clicks are tracked
When you send a newsletter with JungleMail for Office 365, a tiny transparent image – usually just one pixel in size – is inserted at the bottom of the email HTML body. This image is also known as a tracking pixel or a pixel tag, and is unique for each email. When a user opens the newsletter and opts to download images, the pixel is also downloaded, requiring the user’s email client to send a request with specific parameter to the JungleMail server, where the pixel is stored. Once the request is received, JungleMail Analytics service can bound this specific parameter with a recipient and mark that email was opened. If an email client downloads images, and the recipient uses a preview pane, an email viewed in the preview is counted as opened.
If you are sending newsletters to recipients outside your organization, it’s up to recipients to download external images. However, when it comes to internal newsletters, network administrators have a lot more control over user's email client behavior and can set a policy to download all images from JungleMail automatically.
To increase tracking accuracy
By default, Outlook blocks external images - including tracking pixels - within emails from being downloaded from the Internet. However, you can manually add JungleMail for Office 365's "From" address to the Safe Senders List and then enable automatic downloads from this list. Click here for instructions.
System administrators can also implement this change company-wide as a Group Policy setting. It's a great way to ensure that emails are tracked consistently and that analytics reports are accurate. Note that even though junk email settings are correctly deployed to client workstations, they may not be initially used by Outlook because of missing values in the Windows registry. To fix this issue and to configure Outlook properly, follow the steps outlined in this Microsoft Support article.