Journey Data Is a Snapshot. Contact Data Is a Moving Target.
A Decision Split routes a contact differently from what the current source table seems to show.
Trust & provenancePRODUCTION
Evidence tierPRODUCTIONOfficial sources1Other sources0Last verifiedNot recorded
Evidence tier describes my hands-on relationship with the content. Official sources describe platform contracts/documentation. Production observations should not automatically be treated as official limits.
Journey Data represents values captured for the contact at entry, while Contact Data is resolved through the current Contact Model. Choosing the wrong source creates “but the field is X now” debugging sessions.
What to check
- Is the rule intentionally based on entry-time context or current state?
- Is the attribute path pointing to Journey Data or Contact Data?
- Do one-to-many relationships make the Contact Data path ambiguous?
Make it cheaper next time
- Write split requirements using explicit “at entry” vs “current” language.
- Test a contact whose data changes after entry.
journey datacontact datadecision splitcontact model