Skip to content

OmnisendOpen-tracking pixel, click tracking and unsubscribe

E-commerce · vendor's site ↗ · code omnisend

Compare

Latvian sending platform specialized in e-commerce, positioned as a more affordable alternative to the platforms in its segment. It combines email, SMS and notifications in the same scenarios.

Postmetry reference sheet

What the vendor says, checked by us

Documentation maturity 7 / 20 capabilities 35 %

7 sources · last reviewed on 08/16/2026. Still not checked: Open pixel, Exclusion by campaign, Exclusion by contact, Consent — absence means no pixel, Tracking anonymization, Traceable choice, List-Unsubscribe, RFC 8058 — one click, Sending domain, Tracking domain, Logging, Consent history, Granularity of settings.

Postmetry corpus

What brands actually send

Observation base 2 brands · 3 months 52

52 messages received from 08/08/2026 to 10/29/2026. Below the threshold of 30 messages and 8 brands: no rate is published.

Postmetry reference sheet

What this ESP allows

Catalog shared by both pages. Each note carries its source, its date, and its confidence level.

On the right, what our emails say about it: matching, contradicted, never observed despite the volume, too few emails to conclude — or out of reach, when the capability can't be read from an email.

Tracking 7 not verified

Open pixel Not verified Documentation muette Non vérifié Too few emails seen on 51 of 51 emails from 2 brands, 3 months
Click tracking Yes 1 note · 16/08/2026 Too few emails seen on 51 of 51 emails from 2 brands, 3 months
By default

By default, Omnisend tracks email clicks using a shared domain

Caveat Systematic rewriting ("Omnisend automatically modifies that link"), shared domain by default. No click-tracking switch documented, at any level — the only alternative described is the branded domain, which changes the domain, not the tracking. Nothing on transactional emails.

Use Your Link Domain for Email Links (Click Tracking) · Help centre · last reviewed on 08/16/2026 · confidence medium

Exclusion by campaign Not verified Documentation muette Non vérifié Out of reach
Exclusion by contact Not verified Documentation muette Non vérifié Out of reach
Consent — absence means no pixel Not verified Documentation muette Non vérifié Out of reach
Native consent collection Non vérifié Pas encore documenté Non vérifié Out of reach
Tracking anonymization Not verified Documentation muette Non vérifié Out of reach
Traceable choice Not verified Documentation muette Non vérifié Out of reach

Unsubscribe 2 not verified

List-Unsubscribe Not verified Documentation muette Non vérifié Too few emails seen on 51 of 51 emails from 2 brands, 3 months
RFC 8058 — one click Not verified Documentation muette Non vérifié Too few emails seen on 51 of 51 emails from 2 brands, 3 months
Preferences page Yes 1 note · 16/08/2026
By default

The Preference Center lets subscribers choose which email types they want

Caveat Available on all plans; customisable fields; a link that can be inserted in promotional emails only. Hosted by the vendor — "the page cannot be hosted on your domain", style cannot be customised. Preference/unsubscribe clicks are not counted in the click rate.

Set Up Subscriber Preference Center · Help centre · last reviewed on 08/16/2026 · confidence medium

Transactional exceptions Yes 1 note · 16/08/2026
By default

Unsubscribe links can be removed from transactional emails, such as order, shipping

Caveat The link can be removed from transactional emails; it is not removed automatically. Whether open/click tracking is maintained on these streams is not documented: to be observed.

Customize Your Unsubscribe Page Text and Link Position · Help centre · last reviewed on 08/16/2026 · confidence medium

Authentication 2 not verified

DKIM Yes 1 note · 16/08/2026 Too few emails seen on 52 of 52 emails from 2 brands, 3 months
By default

to view the SPF, DKIM, and DMARC records you need to add

Caveat The exact records (and therefore the DKIM selector) are visible only in the account, on the Domain setup page — our recognition of the sending platform will remain an observation from the corpus. A Mailgun history is mentioned (a domain already authenticated via Mailgun = a conflict to resolve through a CNAME): a useful infrastructure clue.

Set Up Your Email Domain in Omnisend · Help centre · last reviewed on 08/16/2026 · confidence medium

SPF Yes 1 note · 16/08/2026 Too few emails seen on 52 of 52 emails from 2 brands, 3 months
By default

When verifying your sender domain, Omnisend checks your SPF record

Caveat The exact include: is not published on the page (provided in the account). A notable rule: at least one valid record among SPF/DKIM/DMARC is enough to verify the domain for sending — full authentication is therefore not required.

Set Up SPF, DKIM, and DMARC for Email Authentication · Help centre · last reviewed on 08/16/2026 · confidence medium

DMARC Yes 1 note · 16/08/2026 Too few emails seen on 52 of 52 emails from 2 brands, 3 months
By default

Ensure a valid DMARC record with at least a "none" policy

Caveat A minimum policy of p=none is required by the Gmail/Yahoo requirements flow; the choice beyond that (quarantine/reject) is left to the brand. Inheritance of the root domain's DMARC by subdomains is documented on the authentication page.

Walkthrough: Meet New Email Sending Rules · Help centre · last reviewed on 08/16/2026 · confidence medium

Sending domain Not verified Pas encore documenté Non vérifié Too few emails seen on 52 of 52 emails from 2 brands, 3 months
Tracking domain Not verified Pas encore documenté Non vérifié Too few emails out of 51 emails from 2 brands, 3 months

Infrastructure & governance 3 not verified

Logging Not verified Documentation muette Non vérifié Out of reach
API Yes 1 note · 16/08/2026 Out of reach
By default

UTM tags can only be updated while the campaign is in draft status

Caveat Documented public API (versions v3 to v2026, scopes campaigns.read/write), covering campaigns and contacts. No endpoint seen that controls tracking per contact; tracking settings are exposed at campaign level (UTM). The full contacts reference remains to be reviewed.

How to configure UTM tags for campaigns · API documentation · last reviewed on 08/16/2026 · confidence high

Consent history Not verified Documentation muette Non vérifié Out of reach
Granularity of settings Not verified Documentation muette Non vérifié Out of reach

Postmetry corpus

Observed in our corpus

Recorded by our analyzers on messages received on addresses we control. Nothing from the reference sheet here, no access to the tool.

52 messages, 2 brands, below the threshold of 30 messages and 8 brands: no rate is published. A percentage on so few emails, or so few brands, describes what one brand configured, not what the sending platform does.

Period observed

08/2026 → 29/10/2026

3 months, 2 distinct brands.

Identification signals

What we recognized the sending platform by, message by message.

  • omni1 58 %
  • omni2 42 %

Limits of this analysis

It doesn't say what a brand has actually configured. A sending platform that allows turning off the pixel says nothing about which brands have done so — that's what a brand's report answers.

It doesn't rank. No score, no recommendation: capabilities don't carry the same weight depending on the use, and that weight isn't ours to set.

A “not checked” cell is not a “no”. It says nobody has gone to look yet, and nothing else.

The corpus does not establish a capability. A rate of observed pixels says what brands send, not what the tool can do.

Sources

7 sources
See the 1 other sources ▾

Frequently asked questions

Does Omnisend rewrite links for click tracking?

Yes: Omnisend rewrites the links in its emails to count clicks.

Do your emails go through Omnisend?

The sending platform is read from the headers, not from a claim. The report names it, and says where to fix the findings with that vendor.

Analyze one of my emails