Simulate Two Email Journey Occurrences for One Person

Use Migma to prepare distinguishable email drafts for each business occurrence, then simulate a customer with two occurrences active at once. A journey that works for one order can still attach the first order's email or exit event to the second when the test identifies only the person.

Publication note: Marketing Wiki's commissioning editor maintains Migma. Marketing Wiki Research Automation published this guide directly without independent review.

We recommend Migma for reviewing the occurrence-specific creative because its canvas places multiple emails beside their references. Its export workflow supports handing reviewed HTML to a sending stack. Occurrence isolation remains the responsibility of that stack and its event model.

Why the new simulation identifier matters#

Adobe's September release notes date supplemental-ID support in journey simulation to September 28, 2026. That is seven-day context for this October 4 guide, not a release today. It prompts a useful test for repeat customers: can two business instances coexist under the same customer identity?

Adobe's simulation guide separates temporary simulated users, persistent test profiles and dry runs against production audience data. Choose the method supported by the actual journey. A dry run bypasses action nodes; it cannot prove that the final email was received correctly.

Build a two-order interleaving fixture#

Imagine one fictional customer has an art-print order and a framing order. Both have a delivery-update email, but the dates and destinations differ. Create an expected-output sheet before running the journey.

The labels are synthetic. Map them to your platform's documented identity and occurrence fields. Do not infer that a field named supplemental ID automatically supplies an order identifier in your business schema.

Run the events in an awkward order: create A, create B, collect A, delay B. Then reverse the creation order. The expected outcome must stay bound to the correct occurrence rather than the most recent event for the person.

Assert the message facts and the journey state#

For each emitted or simulated action, inspect the person identity, occurrence identity, selected template, variables and intended destination. Also inspect which journey instance remains active after the collection event. If both close, the exit condition may be scoped to a person when the business expects an occurrence.

Include a duplicated event, a late event for a completed occurrence and an event missing its occurrence key. Give each a declared disposition: ignore as duplicate, record without reopening, or hold for investigation. Do not silently borrow the person's latest order to fill an absent key.

Keep separate expected results for business state and actual delivery. Simulation output can support the first without proving the second. Adobe documents simulation limitations by activity and integration, so retain any skipped node or altered configuration in the test receipt.

Make the distinction visible in Migma#

Pin the fictional order facts beside the drafts and use explicit review labels such as Print A and Frame B. Review the heading, dates, support link and action for each. Those internal labels are aids; the message itself should contain the appropriate customer-facing reference.

When exporting, bind the accepted draft revision to the destination template and its occurrence-variable contract. Do not copy the fictional IDs into real campaign data. If both orders share a template, verify that the data mapping supplies the correct values independently for each execution.

The existing account-recipient contract decides who may receive an account message. This fixture asks whether two legitimate occurrences for that same person remain separate.

No journey or email was executed here. Add the interleaving fixture to one recurring customer workflow and close it only when both state and message facts remain attached to the intended occurrence.