When creating a Recommendations activity using the Form-Based Experience Composer, what step is different from other activity types?

Question

Options

• AChoosing audience refinements
• BSpecifying the content type
• CSelecting a location
• DNaming the activity

• A
  87% (39)
• B
  2% (1)
• C
  4% (2)
• D
  7% (3)

Explanation

Choosing audience refinements (A) is unique to Recommendations activities because this step lets you filter which items are eligible to be recommended - for example, restricting recommendations to products in a specific category. Other activity types (A/B, XT, MVT) don't surface this step because they don't serve algorithmic recommendations that need item-level filtering.

Why the distractors are wrong:

• B (Content type): All Form-Based activities require you to define what content goes in a location - this isn't Recommendations-specific.
• C (Selecting a location): Choosing an mbox/location is a standard step shared across every Form-Based activity type.
• D (Naming the activity): Every activity type requires a name; nothing unique here.

Memory tip: Link the two R's - Recommendations gets Refinements. It's the only activity type where you're curating a pool of items, so it's the only one that needs an extra filtering step.

No community discussion yet for this question.