End-to-end Dynamic Datastream Configuration example
This page shows how to combine multiple Dynamic Datastream Configuration use cases into a single, production-ready configuration. The example uses the Analytical first pattern and applies to a common e-commerce scenario.
Scenario scenario
An e-commerce retailer uses Web SDK with Adobe Target for personalization, Adobe Analytics, Customer Journey Analytics, and Adobe Real-Time CDP. The retailer currently maintains three separate datastreams: one for Adobe Analytics and Adobe Target, one for Customer Journey Analytics, and one for Adobe Journey Optimizer. The goal is to consolidate into a single datastream and:
- Filter bot traffic before it reaches any service (use case 4)
- Suppress
decisioning.propositionFetchsystem events from Adobe Experience Platform (use case 3) - Route purchases and product interactions to the Real-Time Customer Profile for segmentation and Adobe Journey Optimizer journeys (use case 1 and use case 2)
- Keep page views in the data lake for Customer Journey Analytics only
Since most events are page views (Analytical), the retailer chooses Analytical first: the primary dataset is non-profile-enabled, and rules promote Actionable events to Profile.
Dataset strategy dataset-strategy
Create these datasets before configuring rules. For data retention configuration guidance, see the Experience Event Dataset Retention guide.
Bot Traffic - QuarantineSystem Events - QuarantinepropositionFetch events for debuggingPurchasesProduct InteractionsBrowsing - General (primary)Browsing - General is the primary dataset on the datastream. All events that match no rule fall back to this dataset.
Experience Platform service rules aep-rules
The following table shows the complete rule set for the Adobe Experience Platform service. The Edge Network evaluates rules in the order listed.
eventType equals decisioning.propositionFetch OR eventType equals personalization.requestSystem Events - QuarantineeventType equals commerce.productViews OR eventType equals commerce.productListAddsProduct InteractionsBrowsing - GeneralWhy this rule order rule-order
-
Bot traffic first (Rule 1). Quarantine bot-detected events before any routing logic runs. A bot event that matches a later rule would waste Profile store capacity.
-
System events second (Rule 2).
decisioning.propositionFetchevents fire on every page load and have no analytical value. Catching them early prevents them from accidentally matching an Actionable rule. -
Purchases third (Rule 3). The Actionable events receive full Adobe Experience Platform treatment: Profile, Edge Segmentation, and Adobe Journey Optimizer for triggered inbound personalization.
-
Product interactions fourth (Rule 4). Profile-enabled for segmentation, but Adobe Journey Optimizer is disabled. This implementation does not fetch inbound personalization from Adobe Journey Optimizer on browse behavior.
-
Default last. Everything else (page views, scroll events, site search) lands in the non-profile primary dataset for Customer Journey Analytics reporting only.
Rule budget analysis rule-budget
This configuration uses 4 explicit rules out of the 5-rule-per-service limit for Adobe Experience Platform. One rule slot remains available for future needs, for example, filtering internal traffic by email domain or routing a new event type.
For the full list of guardrails, see Create Dynamic Datastream Configurations.
If you need more granularity, combine additional event types as OR conditions within an existing rule. For example, Rule 4 already combines commerce.productViews and commerce.productListAdds. You could add commerce.productListOpens or commerce.saveForLaters to the same rule without using an additional rule slot. Each rule supports up to 100 conditions.
Solution-level rules solution-rules
The Experience Platform service rules in the previous section are independent of rules for other services. You can configure up to 5 additional rules for each of Adobe Analytics, Adobe Target, Adobe Audience Manager, and Event Forwarding, independently of the Experience Platform rules.
botDetection.score equals 1eventType starts with commerce.rsid-commercebotDetection.score equals 1Assurance validation assurance-validation
After saving your rules, wait 15 minutes for changes to propagate across the Edge Network. Then validate each event path using Adobe Experience Platform Assurance.
For a full walkthrough of the validation process, see Test and validate Dynamic Datastream Configurations.
Bot Traffic - QuarantineSystem Events - QuarantinePurchasesProduct InteractionsBrowsing - GeneralNext steps
- Follow the steps in Test and validate Dynamic Datastream Configurations to verify each event path before deploying to production.
- Read best practices for Dynamic Datastream Configurations for ongoing operational guidance.
- See the FAQ if you encounter unexpected routing behavior.