← Back to the simulators {"noEvent":"With no event there is no window or frequency.","buysNoBuy":"A rule on purchases cannot require no purchase afterwards.","ruleKicker":"The rule","and":"AND","empty":"Add at least one condition.","twoOrMore":"2 or more","ofProduct":"of a product whose category is in the products dataset","in":"in","win24h":"the last 24 hours","win7d":"the last 7 days","win30d":"the last 30 days","noBuyAfter":"with no <code>commerce.purchases</code> afterwards","gold":"Gold","inGold":"in the audience \"Gold members\"","inBuyers":"in the audience \"Buyers of the month\"","withProducts":"with data from the products dataset","best":"Evaluated this way","possible":"Also possible","unsupported":"Not supported","edgeLat":"Up to 350 ms.","edgeLatProfile":"Once a day on Edge.","streamLat":"Up to 5 minutes.","batchLat":"Once a day.","edgeUse":"Personalisation on the same page or the next one (Target, AJO web).","streamUse":"AJO journeys triggered by audience entry, and streaming destinations.","batchUse":"Journeys that read the audience, scheduled campaigns and batch destinations.","edgeLim":"Limit: 150 active audiences per sandbox.","streamLim":"Limit: 500 active audiences per sandbox.","batchLim":"Within the 4,000 active audiences.","whyMp":"The audience does not use the merge policy active on Edge.","whyMultiEdge":"It uses data from another entity (multi-entity).","whyMultiStream":"Multi-entity queries are not evaluated in streaming.","whyWindow":"The event looks back more than 24 hours.","whySequence":"It combines several events in sequence.","whyCount":"It counts the event several times.","whyCountLong":"It counts frequencies over a window longer than 24 hours.","whySegStream":"It mixes an event with another audience.","whySegEdge":"It mixes an event with an audience that is not profile only.","fixMpTitle":"Assign it the merge policy active on Edge","fixMpBody":"Both edge and streaming require it, and there is only one per sandbox. Without it, the audience is batch even if the rule is simple.","fixWindowTitle":"Shorten the window to 24 hours, or split out the history","fixWindowBody":"If what matters is reacting, use the last 24 hours. If you need the week, move the history into a computed attribute and combine it with today's event. That attribute refreshes periodically, not instantly.","fixCountTitle":"Turn the frequency into a computed attribute","fixCountBody":"A COUNT of purchases as a computed attribute, with a lookback of up to 4 weeks. The audience now uses a profile attribute, which does support streaming. But it is not real time: with that lookback it refreshes once a week, or daily with fast refresh.","fixMultiTitle":"Put the category on the event itself","fixMultiBody":"Send the category in the products of the commerce event instead of looking it up in the products dataset. Without multi-entity, the rule can be streaming.","fixSegProfTitle":"For streaming, put the condition in the same rule","fixSegTitle":"Put the condition in the same rule","fixSegBody":"Instead of \"is in audience X\", use its profile conditions directly.","fixSegProfBody":"On edge it is supported, because the referenced audience is profile only.","fixSegEventsBody":"An audience with events referenced from another one with an event takes it out of edge and streaming.","profileOnlyTitle":"Profile only: on Edge, once a day","profileOnlyBody":"An audience that only uses profile attributes is evaluated on Edge daily. In streaming it changes when the attribute arrives via streaming. To personalise on the website instantly, add a session event.","cityTitle":"The attribute arrives by batch","cityBody":"Adobe recommends moving conditions on data ingested by batch into a separate audience and referencing it. Here the city only changes when the CRM batch comes in, however streaming the audience is.","cartTitle":"For the abandoned cart email, an event-triggered journey is better","cartBody":"The audience qualifies when the item is added to the cart, before there has been time to buy. For the email, the usual approach is an event-triggered AJO journey with a wait and a purchase condition. This audience fits better for excluding from campaigns or for personalisation.","journeyTitle":"If an AJO journey uses it","journeyBody":"With edge segmentation, the qualification usually takes 15 to 30 minutes to reach the Hub before the journey sees it. Leave some margin in the journey.","batchOkTitle":"Batch is enough","batchOkBody":"A newsletter or a scheduled campaign does not need real time. Data ingested via streaming can take up to 3 hours to be available for batch.","nothingTitle":"Nothing to rewrite","nothingBody":"It is evaluated with the fastest method its rule supports."}
Experience Platform · Segmentation Service
Edge, streaming or batch
"Why isn't my audience real time?" AEP does not decide by the name but by the rule: which events it uses, over what window, how many times, with which other audiences and with which merge policy. Build an audience and see how it is evaluated and what takes it out of real time.
Illustrative scenario ↑ Back to the controls
Example assumptions
Example audiences, events and attributes.
The rule
How the audience is evaluated
The fastest method the rule supports is used. Each method has its own latency and audience limit.
Rewriting it
What takes it out of real time and how to rewrite it
Recalculated with every change to the rule.
The recommendation
Start with the use case: decide how long it can wait and build the audience for that method
Not every audience needs to be real time. Those that are have a limit: 150 active on edge and 500 in streaming per sandbox, within 4,000 active in total.
- 01
Edge for the visit
Only what is personalised on the same page or the next one. One session event, with or without profile attributes.
- 02
Streaming to react
Abandoned cart, purchase, tier change. Windows under 24 hours, with history turned into computed attributes.
- 03
Batch for everything else
Frequencies, long histories, data from other entities. It resolves once a day. That is enough for newsletters, scheduled campaigns and batch destinations.
- 04
Split out what arrives by batch
Conditions on attributes that arrive by batch go in a separate audience referenced from the real-time one. And all of them on the merge policy active on Edge.