What are valid use cases for Profile Scripts in Adobe Target? (Select two)

Question

Options

• AStoring user attributes for personalization
• BTracking purchase history of users
• CEnabling server-side integrations
• DDefining audiences based on behavior

• A
  72% (36)
• B
  8% (4)
• C
  20% (10)

Explanation

Profile Scripts in Adobe Target are JavaScript snippets that run on the server side to capture and store persistent visitor attributes - making A (Storing user attributes) a core use case, as they save data like visit counts, preferred categories, or behavioral signals directly to the visitor profile. D (Defining audiences based on behavior) is equally valid because profile script values can be used as audience criteria, letting you segment users dynamically (e.g., "users who visited pricing page 3+ times").

B is incorrect because purchase history tracking belongs to order confirmation mboxes or Analytics integrations, not Profile Scripts - they aren't designed for transactional record-keeping. C is incorrect because server-side integrations are handled through the Target Delivery API or SDKs, not Profile Scripts.

Memory tip: Think of Profile Scripts as a visitor's "sticky notepad" - they write notes about behavior (A) and those notes define who the visitor is for targeting (D). Anything involving transactions (B) or external system calls (C) lives elsewhere.

No community discussion yet for this question.