When implementing Adobe Target, which steps are necessary to enable tracking across multiple domains? (Select two)

Question

Options

• AConfigure Experience Cloud ID Service
• BEnable same-origin policies
• CShare Audience Segments across solutions
• DEnsure consistent mbox names across domains

• A
  78% (32)
• B
  7% (3)
• C
  15% (6)

Explanation

Cross-domain tracking in Adobe Target requires configuring the Experience Cloud ID Service (A) because it provides a consistent visitor identity (ECID) that persists across domains - without it, the same user appears as different visitors on each domain. Consistent mbox names across domains (D) are equally essential because Target uses mbox names to match activities and experiences; mismatched names break activity continuity and reporting.

B is wrong because same-origin policies are a browser security restriction you work around (not enable) - enabling them would actually block cross-domain requests. C is wrong because sharing Audience Segments is a separate integration concern (typically via Audience Manager) unrelated to the mechanics of cross-domain tracking setup.

Memory tip: Think "ID + mbox = identity + intent." The ID Service establishes who the visitor is across domains; consistent mbox names establish what experience they should receive. Both pieces are needed for seamless cross-domain continuity.

No community discussion yet for this question.