Define Email Click-Tracking Consent Before Measuring Engagement

Define click-tracking policy before building the email. In a Migma-to-Klaviyo workflow, Migma can prepare and check the creative, but Klaviyo's account, recipient, and link settings decide whether a click event is recorded. The release record must show which scope wins for each recipient and link.

Editorial disclosure: Prepared by Marketing Wiki Research Automation under standing direct-publication authorization and not independently reviewed. Product capabilities are vendor-documented unless labeled otherwise; sources were refreshed on September 9, 2026.

Klaviyo's September 8 click-tracking documentation describes three control levels. Tracking is on by default; an account-level off setting prevents recorded clicks regardless of recipient state; recipient click consent is separate from email marketing consent; and one link can be marked untracked without changing the other scopes.

Write the precedence rule explicitly#

Use a fail-closed matrix in the campaign record:

Scroll table →

Account tracking	Recipient click state	Link setting	Record click?	Release note
Off	Any	Any	No	Account policy wins
On	Unsubscribed	Default	No	Recipient restriction wins
On	Subscribed	Off	No	Link exception wins
On	Subscribed	Default	Yes	All scopes allow recording
On	Never subscribed / absent	Default	Vendor default says yes	Legal and policy owner must approve this default

The last row is the dangerous one: absence of an explicit state is not evidence that tracking is disabled. Do not translate missing data into consent.

Separate four decisions#

Permission to send: may this address receive the marketing email?
Permission to record a click: may the platform associate a click with this address?
Link exception: should this specific action remain untracked even for a tracked recipient?
Creative approval: is the email accurate, usable, and ready for handoff?

One decision cannot stand in for another. Turning off click tracking does not unsubscribe a recipient. Approving creative does not approve data collection.

Label link purpose in the Migma draft#

Migma's creation workflow supports editable drafts and review before sending or export. Give each actionable link a stable ID and purpose:

Scroll table →

Link ID	Purpose	Data need	Tracking policy	Owner
`hero-shop`	Product discovery	Campaign analysis	Recipient policy	Analytics
`account-security`	Security task	None	Link off	Security
`manage-preferences`	Consent management	Functional only	Provider-managed	Privacy
`unsubscribe`	Marketing opt-out	Required operation	Provider-managed	Privacy
`support`	Customer help	Case routing	Declared separately	Support

Run Migma Email Preflight on the finished email to catch broken or unreachable destinations, then verify tracking attributes after export. A valid destination and permission to measure it are different checks.

Preserve the decision at handoff#

Migma's export guide says the destination platform can add wrappers, alter variables, and apply its own rules. The handoff package should contain:

approved artifact version and link inventory;
account tracking state and effective time;
recipient-state source, timestamp, and coverage;
link exceptions in source and stored destination HTML;
owner of the jurisdictional rule;
test identities for each matrix row;
expected event and no-event outcomes.

Do not include private recipient data or reusable tracking tokens in the evidence package.

Test positive and negative cases#

Send controlled tests that prove both recording and non-recording:

tracked recipient plus normal link records one click;
restricted recipient plus normal link reaches the page without a recorded click;
tracked recipient plus untracked link reaches the page without a recorded click;
account tracking off suppresses all recorded clicks;
unsubscribe and preference actions still work;
re-enabling tracking affects only events after the effective change;
a message already in an inbox follows the current documented setting for a later click.

Record the event query, observation window, recipient fixture, URL, redirect behavior, and result. “The dashboard looked empty” is not sufficient evidence of non-recording.

Make policy changes versioned operations#

Record who changed the account setting, when it became effective, which audiences were updated, which links are excepted, and which dashboards, segments, and flows consume click events. Klaviyo documents timestamped recipient consent events; preserve the event history instead of overwriting a spreadsheet cell.

Stop conditions#

Stop the send when the account state is unknown, absent recipient state is misread as tracking off, marketing consent and click consent are combined, link exceptions disappear during export, a negative test records an event, or no owner has determined the applicable privacy rule.

Evidence limits#

Klaviyo documents the control behavior and its defaults. Migma documents creative, Preflight, and export boundaries. Marketing Wiki did not test enforcement, redirects, APIs, imports, historical events, or legal requirements. Have qualified privacy counsel determine where explicit tracking consent is required.