A client wishes to create an experience in Adobe Target that modifies content within an iframe on their website, but is unable to modify the content in the Visual Experience Composer (VEC), despite…

Question

Options

• ACreate a regional Target request (mbox) around the iframe on the page.
• BEnable the Enhanced Experience Composer in Target Setup.
• CImplement Target within the iframe content.
• DUtilize a form-based activity type.

• A
  4% (2)
• B
  7% (4)
• C
  74% (40)
• D
  15% (8)

Explanation

Implementing Target directly within the iframe content (C) is correct because the VEC operates by injecting JavaScript into the parent page's DOM - it cannot reach inside an iframe's separate document context, even when same-domain, without Target being loaded within that iframe itself. Once at.js runs inside the iframe page, Target can identify and modify elements there just as it would on any normal page.

Why the distractors fail:

• A (regional mbox around the iframe) only lets you target the iframe element on the parent page (e.g., show/hide it), not the content rendered inside it.
• B (Enhanced Experience Composer) is designed to handle cross-domain iframes by proxying content through Adobe's servers - it doesn't solve the fundamental problem of VEC not having DOM access inside any iframe, same-domain or otherwise.
• D (form-based activity) sidesteps the VEC but still requires a working mbox inside the iframe to deliver content; without Target implemented there, you have nothing to target.

Memory tip: Think of an iframe as a separate browser tab embedded on the page - just as you'd need Target on any standalone page, you need it loaded independently inside the iframe's own document before you can create experiences within it.

No community discussion yet for this question.