Preserve the Meaning of a Starting Consent Record

Affiliation: Marketing Wiki's commissioning editor maintains Migma.

Marketing Wiki Research Automation published this guide directly without independent review.

When preparing a Migma campaign from migrated audience records, preserve whether a consent-history entry represents a customer action or a starting snapshot. The day a system begins recording history is not automatically the day the customer subscribed.

Migma's sending rules require permission-based marketing and preserved subscription status during moves. We recommend keeping Migma creative work tied to an audience decision whose provenance remains explainable. This article supplies an operational mapping method; it does not determine a legal basis or certify any individual contact's permission.

A starting record answers a narrower question#

Customer.io's consent-record documentation distinguishes history from current subscription preferences and sender opt-outs. For older accounts, it describes starting records based on existing choices when consent records are turned on. Such a record shows that a choice exists, but not how the person originally made it.

The associated October 1 release is historical context, outside this run's seven-day window. This is not a newly announced consent rule or a claim that enabling a feature recreates missing evidence.

That distinction matters when a marketer asks for “people who subscribed recently.” If an import transforms a starting-record timestamp into an original opt-in timestamp, long-standing preferences can appear to be fresh customer actions. A welcome message or recent-subscriber analysis can then answer the wrong question.

Map provenance before importing dates#

Use this original mapping card. The names are editorial fields, not a promised Customer.io or Migma schema.

Current preference: subscribed to approved topic
Record kind: starting snapshot / observed customer action / unknown
History-recorded-at: system observation time
Original-choice-at: known source timestamp or unknown
Collection evidence: source record reference or unknown
Scope: channel, topic and brand meaning
Transfer rule: preserve current exclusions and provenance
Review owner: audience operations

Keep unknown as unknown. Do not copy history-recorded-at into original-choice-at simply because the destination requires a date. Escalate the mapping requirement or use a supported representation that retains the uncertainty.

Customer.io names migration collection points for subscription preferences and sender opt-outs. Preserve their meaning in your evidence record. A new label such as “web form” would invent a collection path if the original record contains only a migrated preference.

Classify three synthetic histories#

In the first case, an older subscriber has a current topic preference and a starting record created when history recording begins. Their original collection method is unavailable. Preserve the current state and mark historical method and original date unknown. Do not count them as a new signup merely because the starting record is recent.

In the second case, a person changes a preference through a documented collection point after recording begins. Retain the observed action and available scope fields. Do not infer additional channels or brands from a single topic choice.

In the third case, current subscription status differs from the latest visible history. Customer.io notes that history and status can differ, including when an automation updates subscription status. Route the inconsistency to the responsible operator. Neither an attractive timeline nor a single cached field should silently decide eligibility for a Migma campaign.

These cases are proposed review fixtures. Marketing Wiki did not import contacts, enable consent recording or test enforcement in either product.

Brief Migma with audience meaning#

Give the creative team the approved audience definition, message purpose and relevant restrictions. A brief can say “existing subscribers receiving a service improvement update” without claiming “you joined yesterday” from a migrated date. Review personalized age-of-relationship claims as carefully as segment membership.

If the message is a welcome email, ask the audience owner which observed event qualifies someone for it. Keep that event rule separate from the ability to render a welcoming design in Migma. Good creative cannot correct a mistaken historical trigger.

Preserve evidence references in the controlled audience system rather than placing raw contact histories in general creative notes. The validation-versus-permission matrix covers a different boundary: technical mailbox status cannot supply permission. Start this history review by finding one mapped timestamp and proving exactly what event it represents.