Real-Time CDP · Journey Optimizer · CJA
Four moments with Laura
What you can do with a customer in Real-Time CDP, AJO and CJA depends on what her profile knows. Which identities are in the graph, and what consent she has given. Pick a moment and see what unlocks and what stays closed.
Example assumptions
Example customer, identifiers, dates and values.
Real-Time Customer Profile
What the profile knows about Laura
Identities in the graph and profile attributes. Anything marked new arrives at this moment.
Real-Time CDP · AJO · CJA
What you can do with her
Thirteen actions by product across four moments. The highlighted column is the chosen moment; under each action, its reason.
The recommendation
Each moment is unlocked by an identity and a consent. Design when to ask for them
This is not a marketing funnel. It is an identity capture plan: which namespace enters the graph at each point of the journey, and with which consent.
- 01
Server-side FPID
A first-party cookie set by your server, not by JavaScript, which the Web SDK sends to seed the ECID. Laura stays the same visitor in Safari after 7 days.
- 02
Ask for the email early, with explicit consent
Newsletter, wishlist or back-in-stock alert. Do not leave consents.marketing.email.val empty: change the default behaviour or use consent policies.
- 03
Login, club and app that send identities
At login and checkout, the Web SDK and Mobile SDK send Email and CRMID in the identityMap. Then loyaltyId linked to the CRMID, and push permission requested when it makes sense, not on first launch.
- 04
Pseudonymous profile expiry
Profiles with only an ECID that never return are deleted after the number of days you configure. Once deleted, they stop counting towards your licence.