Skip to main content
Adrià García
Menu
← Back to the simulators

Web SDK · datastreams · event forwarding

Browser or server

A store's product page loads Adobe, the Meta pixel, Google Ads, GA4, TikTok and a heatmap. Each one has its own library and its own request. Choose which Adobe library the page uses and where each tag lives.

Scenario

Adobe: Analytics, Target and AEP

Adobe does not support Web SDK for Target with AppMeasurement for Analytics on the same page. You can migrate page by page.

Meta: purchases for ads
Google Ads: purchase conversion
GA4: still used by ecommerce
TikTok: campaign purchases

Assumes the blocker stops third-party libraries but not the Web SDK call.

See the full result ↓
Illustrative scenario ↑ Back to the controls
Example assumptions

Example store, requests and percentages. Web SDK, datastream and event forwarding behaviour comes from the public Adobe documentation.

Product page

How each visit travels

Dashed lines: vendor library in the browser. Solid lines: from the Edge Network.

Consequences

What this set-up gains and loses

Recalculated with every change. The heatmap always stays in the browser.

Architecture

Where it fits in the platform

One request brings back the Journey Optimizer proposition and the ECID. The Edge Network sends the event to Experience Platform, where CJA reads it, and forwards it to Meta. With consent set to out, the event never leaves the browser.

Sequence diagram of one Web SDK request, with seven participants: the page, a product page; the Web SDK, alloy.js; the Edge Network with its datastream; Journey Optimizer, deciding at the Edge Network; Experience Platform, with a dataset and Profile; Customer Journey Analytics with its connection; and event forwarding to the Meta Conversions API. Out: the page passes consent in from the CMP to the Web SDK with setConsent, then calls sendEvent with commerce.productViews. The Web SDK sends a POST to the interact endpoint with the XDM event. Decision: the Edge Network requests propositions from Journey Optimizer, which returns a banner. The Edge Network responds to the Web SDK with the propositions and the ECID, which the Web SDK reuses, and the Web SDK renders the banner without a second call. Only the Journey Optimizer proposition travels in that response, and it needs an Active-On-Edge merge policy. Fan-out: the Edge Network sends the XDM event to the dataset and Profile, the Customer Journey Analytics connection reads that dataset, and the Edge Network applies the product view rule to forward it to CAPI. Measurement: after rendering, the Web SDK sends the display notification. With consent set to out, the event never leaves the browser, and with no event at the Edge Network there is nothing to forward.

The recommendation

One Adobe library, distribution in the Edge Network and only what needs it in the browser

It is not about moving everything to the server. Whatever only sends data leaves from the Edge Network. Whatever renders, records or needs its own cookies stays on the page.

  1. 01

    Migrate to Web SDK

    It replaces AppMeasurement and at.js with one call to the Edge Network. The datastream sends it on to Analytics, Target and Experience Platform. Each page is migrated in full.

  2. 02

    Conversions through event forwarding

    An event forwarding property with the Meta, Google Ads, TikTok, Pinterest or Snap extensions. It comes with Real-Time CDP Connections, Prime or Ultimate.

  3. 03

    In the browser, what needs it

    Personalisation renders on the page and the heatmap records the session. The Meta pixel can run alongside the Conversions API if both send the same event_id.

  4. 04

    Consent, once

    It is set in the Web SDK. If the customer declines, the event never reaches the Edge Network and there is nothing to forward. Anything left in Tags needs its own conditions.