A client has set up a Redirect Offer within Adobe Target with Adobe Analytics as the reporting source. Data for the redirect landing page is not showing in the report. The Adobe Target Architect has…

Question

Options

• AVerify that the correct adobe_mc_ref URL parameter is present on the redirect page.
• BInclude additional code in the redirect offer to encode the URL parameters.
• CVerify that the correct adobe_mc_sdid URL parameter is present on the redirect page.
• DVerify that the correct adobe_mc_id URL parameter is present.

• A
  5% (1)
• B
  5% (1)
• C
  76% (16)
• D
  14% (3)

Explanation

When using A4T (Analytics for Target) with a Redirect Offer, Adobe Target appends the adobe_mc_sdid (Supplemental Data ID) parameter to the redirect URL so Analytics can stitch the hit on the original page with the hit on the landing page - without it, Analytics has no way to connect the two page views, causing landing page data to go missing in reports. Option A (adobe_mc_ref) is wrong because that parameter carries the referrer URL, not the stitching ID needed for A4T data reconciliation. Option B is wrong because URL encoding is handled automatically by the libraries and is not a documented troubleshooting step for this scenario. Option D (adobe_mc_id) is wrong because the Marketing Cloud ID (ECID) handles visitor identification, not cross-page hit stitching - and it would already be covered by the correctly-implemented ID Service library.

Memory tip: Think of SDID as the "staple" - it staples the redirect source page hit to the landing page hit inside Analytics. No staple = no data.

No community discussion yet for this question.