Which issues can cause integration errors with A4T? (Select two)

Question

Options

• AMissing Analytics segment mapping
• BIncorrect at.js integration
• COutdated catalog feeds
• DUnsynchronized report suites

• A
  7% (4)
• B
  81% (47)
• C
  12% (7)

Explanation

Incorrect at.js integration (B) is a core cause because at.js is Adobe Target's implementation library responsible for firing the Target request and syncing with Analytics. If at.js isn't properly configured or is missing the A4T supplemental data ID (SDID) handshake, Activity data never reaches Analytics. Unsynchronized report suites (D) is the other key issue - A4T requires the same report suite to be selected in both Target and Analytics; a mismatch means Target activity data lands in a different report suite or nowhere at all, breaking the integration.

Missing Analytics segment mapping (A) is a distractor - segments are post-collection filters in Analytics and have no role in establishing the A4T data pipeline itself. Outdated catalog feeds (C) are relevant to Recommendations product data, not the Target-Analytics integration layer.

Memory tip: Think of A4T as a bridge - at.js is the on-ramp (data must enter correctly) and the report suite is the destination (both sides must agree on where it's going). If either end is broken, no data crosses.

No community discussion yet for this question.