A retail company wants to track which store is the user's preferred store, which is only available in the site's data layer. Which method should be recommended to bring the preferred store into…

Question

Options

• ATarget request (mbox) profile attributes
• BData Providers
• CScript profile parameters
• DPeople Core Services Customer Attributes

• A
  77% (23)
• B
  7% (2)
• C
  13% (4)
• D
  3% (1)

Explanation

Target request (mbox) profile attributes are the right choice because they let you read a value directly from the client-side data layer and pass it as a profile. parameter within the same mbox request - one action, real-time, no extra steps. Data Providers (B) are designed to fetch data asynchronously from external third-party APIs before the Target call fires; they add unnecessary overhead when the data is already present in the data layer. Script profile parameters (C) run server-side within Target itself and cannot access the client-side data layer - they derive values from existing mbox or profile data, not from the page. Customer Attributes (D) require a separate offline batch upload of CRM data via the People Core Service and are meant for persistent known-visitor attributes, not real-time session data.

Memory tip: Think of mbox profile attributes as "stuffing the envelope" - you grab whatever is on the page (data layer included) and seal it all into one request. If the data lives on the page, the mbox carries it.

No community discussion yet for this question.