Architecture simulators
Architecture decisions that often go wrong in CDP projects. You change the scenario, see what breaks and read the recommendation.
Grouped by the part of the platform where it hurts. Each one runs in your browser and sends nothing.
Start with a question
Campaigns, customers and data usage. Pick a problem and see what changes when you make a different decision.
-
Are we sending too many messages to the same person?
Try a limit of 1 email per day: Monday’s newsletter blocks Laura’s cart reminder.
AJO Open the simulator → -
Does your campaign drive purchases or just opens?
Change the metric to see why the subject line with more opens can sell less.
AJO Open the simulator → -
Why do we count several customers when there is only one?
Connect the website, app and shop. See which messages change when the same customer is recognised.
AEP Open the simulator → -
Can we store less without losing what we need?
Choose which data goes into Profile. Compare licence usage with the use cases that still work.
AEP Open the simulator →
View the platform map
Collection, ingestion, profile, audiences and applications, as data flows through Experience Platform. Each group of simulators covers one part.
Map of Adobe Experience Platform with Journey Optimizer and Customer Journey Analytics, top to bottom in five stages. Capture: the Web and Mobile SDK, on the client or the server, sends XDM events, and systems such as the CRM or the warehouse deliver files. Ingestion: the Edge Network receives the XDM event in its datastream and streams it to Profile, and also to Data Lake datasets. Sources receives files and API calls through its connectors and Data Prep, and in these examples loads them into the Data Lake in batch, although it also supports streaming connectors. Profile and Data Lake: Identity Service links identifiers from several namespaces in a graph and passes it to Profile. Profile joins attributes and events in real time, and is fed by the enabled datasets of the Data Lake, which keeps the history. Audiences and governance: Segmentation receives the profiles and evaluates audiences with three methods. Governance applies labels, policies and consent. Applications: audiences go out to Destinations, in Real-Time CDP, where Governance checks its policies at activation. Journey Optimizer receives profiles and events to act in its journeys in real time. Customer Journey Analytics ingests the Experience Platform datasets selected in a connection and exposes them for analysis through its data views.
All simulators
Guided examples suggest a first change. In free exploration, you choose which settings to try.
Identity and profile
-
How many profiles does one person have?
How many profiles do three people produce, and what does it take to get three?
Open the simulator → -
Four moments with Laura
What can you do with Laura at each moment, given her identities and her consent?
Open the simulator → -
Which value wins
Which value of each attribute does AJO see, depending on the merge policy?
Open the simulator → -
Where do you store the orders?
Which audiences work if the orders live in the profile, in events or in the warehouse?
Open the simulator → -
The load that wiped the names
What is left on Laura's profile after the load, depending on how the record is ingested?
Open the simulator →
Data and governance
-
Can I send this?
What stops a labelled piece of data from going out to a destination or an AJO channel?
Open the simulator → -
Where consent lives
How much of what Laura decided reaches her profile, and who enforces it at activation?
Open the simulator → -
Retain or delete
Which group gets deleted, with which tool, and what breaks when it does?
Open the simulator → -
SQL in AEP
Ad hoc query, batch query, computed attribute or an audience with SQL?
Open the simulator → -
From development to production
What travels in a sandbox tooling package, and what has to be rebuilt by hand?
Open the simulator → -
The schema with no way back
Which changes does an XDM schema accept once it has data?
Open the simulator → -
How much of the licence is used
How does licence usage change over two years depending on the set-up?
Open the simulator → -
Profile or data lake?
Which events need to be in Profile, and which can simply live in the data lake?
Open the simulator →
Collection and timing
-
The journey of an event
Which events go out, when is the ECID created and which services do they reach?
Open the simulator → -
Laura installs the app
What breaks when an SDK call or a dataset is missing?
Open the simulator → -
Is it real time?
When does each channel find out about the abandoned cart, and what delays it?
Open the simulator → -
Edge, streaming or batch
Is this audience evaluated on edge, in streaming or in batch, and which piece takes it out of real time?
Open the simulator → -
The load that half failed
How many purchases and how much money do Profile and the data lake see after reprocessing?
Open the simulator → -
Browser or server
Web SDK, legacy libraries or event forwarding for each tag?
Open the simulator →
Activation
-
Who reaches the destination
Which profiles in the audience reach each destination, and with which identities?
Open the simulator → -
Which offer wins
Which offer does Laura get, and what did each step discard?
Open the simulator → -
Person or account?
Laura is a customer of two brands. How does each one email her with its own sender, respecting what she agreed to with each?
Open the simulator → -
Journey or campaign
Which type of journey or campaign fits each of the shop's use cases?
Open the simulator → -
Are we sending Laura too many messages?
How many messages reach Laura this week, and which ones are left out?
Open the simulator → -
When the CRM does not answer
How many customers get the email with their points when the CRM cannot take the peak?
Open the simulator → -
The ones already inside
Which email do the customers already inside receive, and can someone who signs up again get back in?
Open the simulator →
Analysis
-
Same data, different reports
Did conversion improve, or did the way sessions are counted change?
Open the simulator → -
How many people visited us?
How many people and what conversion rate does CJA report with each stitching method?
Open the simulator → -
Who is one person to CJA?
Who is "one person" to CJA, depending on the field you choose as person ID?
Open the simulator → -
Graph or stitching
Who is the customer for AEP when activating, and who was she for CJA when measuring?
Open the simulator → -
Did the campaign work?
Would you choose the same subject line if you measured purchases instead of opens?
Open the simulator →
The stores, people and figures are examples. Product behaviour comes from the public Adobe documentation.