A client would like to run two activities on their homepage and does not want these activities to overlap. Which feature should be used to separate visitors into two distinct audiences?

Question

Options

• ATraffic Allocation
• BProfile Script
• CData Providers
• DAudience Targeting

• A
  7% (2)
• B
  79% (22)
• C
  4% (1)
• D
  11% (3)

Explanation

Profile Script is correct because it runs server-side on every mbox request and can permanently assign a visitor to a "bucket" (e.g., user.bucket = 1 or user.bucket = 2) stored in their visitor profile. This persistent attribute can then be referenced by audience rules in each activity to guarantee mutually exclusive participation - once a visitor is assigned, they always see only one activity.

• Traffic Allocation (A) controls the percentage split of visitors within a single activity between experiences; it has no mechanism to separate visitors across two different activities.
• Data Providers (C) pull in third-party data at page load for targeting decisions, but they don't create a sticky, persistent assignment that prevents a visitor from qualifying for both activities.
• Audience Targeting (D) is the consumer of the profile attribute - you use it to apply the separation - but without the profile script writing the persistent bucket value, audiences alone cannot guarantee visitors won't qualify for both activities simultaneously.

Memory tip: Think of a Profile Script as a permanent stamp on a visitor's record. Audience Targeting reads the stamp, but only the Profile Script can write it durably enough to keep two activities from "double-stamping" the same person.

No community discussion yet for this question.