DocumentationExperience PlatformDatastreams Guide

Prerequisites and planning checklist

Last update: June 18, 2026

CREATED FOR:

  • Developer

Complete the following steps before you configure Dynamic Datastream Configuration rules. These are the most common sources of misconfigured rules and unexpected routing behavior.

Datastream setup datastream-setup

Your datastream must exist and have all required services enabled before you add rules. See Configure a datastream and Add services to a datastream for setup instructions.

Depending on which services you plan to use:

  • Adobe Analytics: Configure at least one report suite. You can add more report suites under Advanced Options as report suite overrides.

  • Adobe Target: Configure at least one property token. You can add more property tokens under Advanced Options as property token overrides.

  • Adobe Audience Manager: No additional configuration required. See Audience Manager settings.

  • Event Forwarding: Configure a property. See Event Forwarding settings.

  • Adobe Experience Platform:

    • Configure a primary event dataset. This dataset receives all events that match no rule (the default fallback).
    • Configure any additional secondary event datasets your rules will route events to. If these datasets do not yet exist, complete the Schema and dataset preparation step before configuring rules.
    • Enable the Adobe Experience Platform Edge services you need, including Decision Management, Edge Segmentation, Personalization Destinations, or Adobe Journey Optimizer. See Experience Platform settings.

Schema and dataset preparation schema-dataset

Prepare your schemas and datasets before configuring rules. Datasets must exist before you can reference them in routing configurations.

  • Set the XDM schema for Dynamic Datastream Configuration conditions in the Mapping Schema section of the datastream (see Create a datastream).
  • Verify that your XDM schema includes all fields you plan to use as rule conditions, for example eventType, custom data layer fields, or geographic fields.
  • If you plan to use bot filtering rules, add the Bot Detection Information field group to your XDM schema and enable bot detection on the datastream. Allow up to 15 minutes for bot detection rules to propagate before testing.
  • Create all target datasets before configuring rules, using the correct schema and naming convention. After you validate your rules, you can enable profile, configure data retention, and enable Customer Journey Analytics connections.

For details on configuring dataset retention windows, see the Experience Event Dataset Retention guide.

TIP
Create datasets without profile enablement first. Validate that events route to the correct datasets using Adobe Experience Platform Assurance, then enable profile and data retention settings. This prevents unnecessary events from being ingested in the Real-Time Customer Profile in the first place.

Event inventory event-inventory

Catalog every event type your implementation sends and classify each one before you write a single rule.

  1. List all event types. Common examples include web.webpagedetails.pageViews, commerce.purchases, commerce.productViews, commerce.productListAdds, decisioning.propositionFetch, and personalization.request.

  2. Classify each event using the event value taxonomy:

    • Expendable: no analytical or actionable value (bot traffic, system events)
    • Analytical: needed for analytics reporting only, not for profile enrichment or segmentation
    • Actionable: needed for profile enrichment, segmentation, and activation; also available for analytics reporting

  3. Identify audience-dependent events. Review your audience definitions and note which event types those audiences reference. Routing those events away from a profile-enabled dataset prevents the Real-Time Customer Profile from ingesting them, which causes audiences to stop evaluating correctly.

  4. Identify reliable condition fields. Choose fields that are consistently populated and have a small, predictable set of values. eventType is the recommended primary condition field for most rules. Other useful fields include botDetection.score, web.webPageDetails.URL, and custom data layer fields mapped through Data Prep for Data Collection.

Remove conflicting client-side overrides remove-overrides

Datastream configuration overrides take precedence over Dynamic Datastream Configuration rules. Any event that carries a client-side override bypasses your rules silently, with no error or warning.

Before enabling rules:

  • Verify that your Web SDK or Mobile SDK implementation does not send edgeConfigOverrides in sendEvent or configure calls for events that your rules should handle.
  • For each event type you move to Dynamic Datastream Configuration rules, remove the corresponding edgeConfigOverrides from your SDK code before you enable the rule.

Next steps

After completing this checklist, you are ready to design your rules:

recommendation-more-help
experience-platform-help-datastreams