An Adobe Target Business Practitioner is tasked with implementing an Exit Intent Pop-Up on a specific website page using Adobe Target. The objective is to measure user interactions effectively by…

Question

Options

• ASet up two separate conversion goals in Adobe Target, one for "clicked element" and another for
• BImplement a custom JavaScript function through Adobe Target to manually track clicks and views
• CUtilize Adobe Target's out-of-the-box metrics without customization for a combined conversion
• DCreate a Calculated Metric based on "clicked element & viewed page" in Adobe Analytics and then

• A
  4% (1)
• B
  4% (1)
• C
  16% (4)
• D
  76% (19)

Explanation

Option D is correct because when Adobe Analytics serves as the reporting source for Adobe Target (the A4T integration), you gain access to Adobe Analytics' Calculated Metrics feature, which allows you to combine "clicked element" AND "viewed page" into a single composite metric - that combined metric is then imported into Adobe Target as one unified conversion goal, satisfying the requirement to measure both interactions together.

Why the distractors fail:

• A creates two separate goals, which tracks each event independently rather than as a single combined conversion - this splits the measurement, not unifies it.
• B (custom JavaScript) is unnecessary complexity; the A4T integration already provides the mechanism natively, and custom tracking scripts introduce maintenance overhead and error risk.
• C fails because Adobe Target's native out-of-the-box metrics cannot natively chain a click and a subsequent page view into a single conversion goal without leveraging Analytics.

Memory tip: When you see "Adobe Analytics as reporting source" in a question, think "Analytics owns the metric math." Any combined or conditional conversion logic should be built as a Calculated Metric in Analytics first, then surfaced in Target - not the other way around.

No community discussion yet for this question.