Which Target request type is best for reducing latency and improving speed?

Question

Options

• AGlobal Request
• BHybrid Request
• CBatch Request
• DOrder Confirmation Request

• A
  14% (8)
• B
  77% (44)
• C
  7% (4)
• D
  2% (1)

Explanation

Hybrid Request is correct because it combines on-device decisioning (executed locally, with near-zero latency) and server-side decisioning in a single hybrid execution model. This means eligible activities resolve instantly on the client without a network round-trip, dramatically reducing response times compared to purely server-side approaches.

Why the distractors are wrong:

• A. Global Request fires a single call at page load to retrieve all Target activities, but it still relies on a server round-trip, making it slower than Hybrid for latency-sensitive scenarios.
• C. Batch Request groups multiple mbox calls into one network request to reduce the number of calls, but the goal is efficiency, not raw speed - the round-trip still occurs.
• D. Order Confirmation Request is a specialized request for capturing purchase/conversion data; it plays no role in content delivery speed.

Memory tip: Think "Hybrid = local + server." The local part is what kills latency - just like a hybrid car uses the electric motor (instant torque, no warm-up) for quick starts. If speed is the priority, go Hybrid.

No community discussion yet for this question.