Test and operate
Test customer events safely
Validate payloads, schemas, identity, journey qualification, and exits without emailing real customers.
Start with an isolated source
Create a staging connection and use synthetic customers on addresses your team controls. Keep all journeys in draft until event names, property types, identity, consent, and goal exits are verified.
End-to-end checklist
- 01
Send identify
Confirm the durable user ID, email trait, and other intended traits.
- 02
Send the trigger
Use a unique messageId and realistic but non-sensitive properties.
- 03
Inspect the schema
Confirm names and types match the journey conditions.
- 04
Run the draft journey
Use built-in test controls and inspect the enrollment timeline.
- 05
Send the goal event
Verify the customer exits before any later action.
- 06
Repeat a messageId
Confirm duplicate count increases and no second customer event is created.
Promote to production
- ✓Create a separate production connection and credential
- ✓Recreate or review the observed production schema
- ✓Activate one narrowly scoped journey
- ✓Monitor accepted, rejected, failed, enrolled, exited, and suppressed outcomes
- ✓Expand traffic only after expected behavior is visible