InMarket bake-off: CTV measurement vs ACR feeds

TL;DR

• Choose GSDSI when you need CTV/ACR exposure logs and mobility outcomes as licensed feeds for your measurement stack.
• Choose InMarket when you want a packaged media and location measurement offering with managed reporting.
• In a pilot, validate panel stability, content-recognition methodology, and outcome joins, not just reach charts.

What to align before the bake-off

CTV and store-visit measurement fails when exposure logs and outcome panels use incompatible dedupe or geography cuts. Agree on the join plan and privacy envelope before you compare vendors.

Decision frame

Choose GSDSI when

• Your measurement team owns lift models in a warehouse or clean room.
• You need ACR-grade exposure plus identity graph joins under one contract.
• You require flat-file or Snowflake delivery with schema stability commitments.

CTV / ACR buying guide · CTV Smart TV ACR

Choose InMarket when

• You want managed measurement products spanning media and location.
• Your org prioritizes speed to packaged reporting over feed-level control.

Pilot checklist

• Monthly unique CTV or device IDs with churn disclosure.
• Attribution windows and frequency caps documented.
• Store-visit or outcome joins tested on your retail set.
• Governance: exclusions, retention, and subprocessors listed in the order.

FAQ

How is InMarket different from licensing ACR feeds?

InMarket is often evaluated as a managed media and location measurement product. GSDSI is evaluated when buyers need exposure-grade files and identity keys for custom lift models.

What CTV diligence questions matter?

Panel stability, content-recognition methodology, dedupe rules, and outcome joins. See /ctv-acr for the full checklist.

Can we run a clean-room bake-off?

Yes, when contracts allow. Document aggregation floors and permitted joins before comparing exposure-to-outcome results across vendors.