What are the benefits of using Global Requests in Adobe Target? (Select two)

Question

Options

• AEfficient data collection for all pages
• BEnhanced real-time segmentation
• CReduced request payload size
• DConsistent user experience across sessions

• A
  71% (20)
• B
  11% (3)
• C
  18% (5)

Explanation

Global Requests in Adobe Target fire a single mbox call that loads on every page of a site, making them ideal for sitewide data collection (A) - every page visit is tracked without requiring individual mbox configurations per page. They also ensure consistent user experience across sessions (D) because the same activity and experience logic is applied uniformly regardless of which page a visitor enters on, preventing jarring variation between pages or visits.

Why B and C are wrong:

• B (Enhanced real-time segmentation) - segmentation capabilities are tied to your audience rules and visitor profiles, not to whether you use a global vs. local request. The request type doesn't enhance segmentation itself.
• C (Reduced request payload size) - a Global Request actually consolidates calls but doesn't inherently shrink the payload; in fact, loading all activity data sitewide can increase payload compared to a targeted local request on a single page.

Memory tip: Think of Global Requests as a "net cast over the whole site" - they collect data everywhere (A) and deliver the same experience everywhere (D). Both benefits are about scope and consistency, not about performance optimization or segmentation logic.

No community discussion yet for this question.