Configure tag management and edge network routing

This task produces a working, published tag container that captures user interactions on a web or mobile property and routes the resulting event stream to one or more downstream data stores through a centrally managed edge configuration. The key decisions are: which SDK or library loads the container, how the edge routing configuration maps to destination sandboxes and services, and which data-element/rule combinations govern what gets collected on each page type.

Core components. Three artifacts must be created and linked before data can flow: (1) a Tag Property that scopes the container to a domain or app; (2) a Datastream (edge routing config) that declares which services receive events and which sandbox or org-level settings apply; (3) a published library containing the SDK extension, data elements, and rules. The SDK extension bridges the container to the edge endpoint. Data elements give rules a stable variable vocabulary. Rules define when, what, and how to send — typically "on page view" or "on custom event" triggers paired with a "send event" action carrying an XDM payload.

Key decisions. First-party vs. third-party edge domain (CNAME vs. default edge.adobedc.net) affects cookie lifetime and ad-blocker resistance. Datastream service toggles (Edge Segmentation, Offer Decisioning, Personalization Destinations) must be enabled before the downstream feature can receive data — they cannot be back-filled retroactively on a per-event basis. Library publishing stages (Development → Staging → Production) provide a release gate that prevents untested rules from reaching production traffic.

Parallel viability (moderate). Any tag management system (Tealium, Segment.io, Google Tag Manager) can load an equivalent first-party SDK and route events to any edge or streaming endpoint. The structural pattern — property → routing config → library publish — is consistent across vendors, though naming and UI layout differ. Phase 3 will document Tealium EventStream and Segment.io Source configurations as parallel implementations.