What features are supported by the Form-Based Experience Composer? (Select two.)

Question

Options

• ADynamic URL parameters
• BCode-based template editing
• CCreating multi-page experiences
• DTesting server-side logic

• A
  92% (59)
• B
  5% (3)
• D
  3% (2)

Explanation

Dynamic URL parameters (A) and creating multi-page experiences (C) are correct because the Form-Based Experience Composer in Adobe Target is designed for non-visual, structured targeting scenarios. It natively supports dynamic URL parameters for precise audience targeting and allows you to build multi-page activities by adding multiple locations across pages in a single experience.

B (Code-based template editing) is incorrect - the form-based composer uses a structured form interface, not direct code editing. Code-based modifications belong to the Code Editor within the Visual Experience Composer or the Code-Based Experience channel.

D (Testing server-side logic) is incorrect - the Form-Based Experience Composer is a client-side delivery mechanism. Server-side testing uses Adobe Target's server-side APIs or SDKs, which operate outside the composer entirely.

Memory tip: Think of the Form-Based Composer as a form you fill out - it lets you say "on these URLs (dynamic parameters), across these pages (multi-page), show this content." Anything requiring code editing or backend logic lives outside the form.

No community discussion yet for this question.