FAQ: Data Licensing, Samples & Delivery

Answers to common GSDSI buyer questions: what we sell, how to request samples, delivery formats, pilots, privacy diligence, federal programs, and links to topic buying guides.

GSDSI licensing FAQ

This page answers company-wide buyer questions: samples, delivery formats, pilots, pricing model, privacy diligence, federal programs, and where to find topic-specific procurement guides.

Buying guides

Request a scoped sample via contact or read pilot process and pricing.

FAQ

What does GSDSI sell?
GSDSI licenses privacy-safe commercial data feeds: identity graphs (MAID→HEM, household, CTV IDs), location intelligence (POI polygons and global mobility panels), CTV/ACR exposure, clickstream intent, CPG purchase signals, property and B2B files, and vertical lead products. Buyers evaluate through product pages, buying-guide hubs, and catalog.gsdsi.com before scoping a matched sample.
Who is GSDSI a fit for?
Enterprise data buyers in advertising and AdTech, financial services and alternative data, retail and CPG, real estate, healthcare analytics (non-PHI), travel, media, and federal/defense teams that need documented provenance, sample-before-contract pilots, and flexible warehouse or activation delivery.
How do I request a data sample?
Use /contact or the Request Sample CTAs on product and pricing pages. The solutions team scopes volume, geography, and format (CSV, JSON, Parquet via S3 or SFTP), then typically delivers a sized evaluation file within 2 to 3 business days after the scoping call.
What delivery formats and channels does GSDSI support?
File formats include CSV, JSON, Parquet, SQL, TXT, and XLS. Delivery paths include Snowflake secure share, BigQuery, AWS S3, Google Cloud Storage, Azure Blob, REST API, SFTP, AWS Data Exchange, and clean-room workspaces. Federal programs can terminate in AWS GovCloud or Azure Government.
How long does a typical pilot take?
Most buyers run a matched-sample pilot (2 to 5 business days to deliver the file) followed by a 2 to 4 week evaluation window against their own seed or measurement stack. Production licensing follows a signed order or SOW; feeds usually land in the buyer environment within 1 to 2 weeks of signature. See /pilot-process for the standard checklist.
How is GSDSI data priced?
Pricing is custom-scoped by volume, geography, refresh cadence, use case, and delivery method. Quotes may be structured as insertion orders, subscriptions, or data-share terms. Every engagement starts with discovery; there is no self-serve cart. Details are on /pricing.
What is the difference between Products and Solutions pages?
Products pages describe individual feeds (schema, coverage, refresh, delivery). Solutions pages describe how multiple feeds combine for a workflow: audience targeting, CTV measurement, fraud, site selection, alternative data for finance, and similar motions. Start with the product spec, then read the solution playbook for joins and methodology.
Where can I browse the full SKU catalog?
The live Monda Data Storefront at catalog.gsdsi.com lists 50+ SKUs with search and filters. The site footer links to it as Data Catalog. Each gsdsi.com /products/* page documents a single feed in depth for procurement memos.
Where should privacy and legal teams start diligence?
Begin with /sourcing-methodology for provenance and QA, /trust for security and subprocessors, /privacy-center for consumer rights, and the /privacy-compliance buying guide for post-FTC procurement questions. Executable terms live in the signed license and any data processing addendum.
Does GSDSI support federal and intelligence buyers?
Yes. The Federal Intelligence practice and /federal-procurement hub document CAI-aligned sourcing, VOSB/SDVOSB status, GovCloud delivery, and downloadable capability statements. Contact federal@gsdsi.com or use the federal contact form for scoped evaluations.
How does GSDSI handle CCPA, CPRA, and GDPR rights requests?
Consumer rights workflows are documented at /privacy-center and /do-not-sell. Production licenses define retention, deletion SLAs, and downstream sharing. Buyers should align their activation and measurement use cases with the stated permitted uses before scaling.
Can GSDSI data be used in clean rooms?
Yes. GSDSI supports Snowflake secure shares, InfoSum, LiveRamp Safe Haven, and buyer-controlled warehouse joins where contract terms allow. See /clean-room-measurement and /integrations for connector status and governance expectations.
How should I evaluate identity-graph match rates?
Run a matched sample on your own hashed seed, segmented by geography and channel. Ask for confidence tiers, last_seen decay fields, and refresh cadence. Deck averages are not sufficient. Use the /identity-resolution buying guide and /identity-graph product overview.
How do POI data and mobility panels differ?
POI data answers “where is the place?” with polygon footprints and brand hierarchy. Mobility panels answer “who visited, when?” with device-level visitation aggregated to privacy-safe cohorts. Many location use cases require both. See /location-intelligence and /poi-data.
What should CTV and measurement teams validate?
Panel stability, unique CTV ID volume, content-recognition methodology, dedupe rules, attribution windows, and joins to identity or outcomes. The /ctv-acr buying guide and CTV Smart TV ACR product page list the diligence checklist.
How do finance buyers evaluate alternative data?
Validate ticker mapping, historical depth, revision policy, survivorship, latency, and leakage controls before production. Start with /alternative-data, tickerized data and clickstream product pages, and the alternative data for finance solution.
Where is the integrations list?
/integrations documents DSP, CDP, clean-room, warehouse, and identity partner routes with Production, Beta, and On Request status. Net-new connectors are scoped with solutions engineering during procurement.
What support is included during evaluation?
Samples include data-dictionary walkthroughs and schema notes. Pilots may add solutions engineering for cohort design, match-rate readouts, and delivery manifests. Production licenses include agreed refresh SLAs and customer success contacts per contract.
What contract vehicles are available?
Commercial buyers typically sign direct MSAs or insertion orders. Federal buyers may reference SAM.gov registration, capability statements, and agency-specific vehicles described on /federal-procurement/contract-vehicles.
How often is data refreshed?
Cadence is feed-specific: POI and many identity products refresh daily; other panels may be weekly or monthly. Always confirm refresh SLA, change-delta delivery, and backfill policy in the order form.
Where can I review subprocessors?
The live table is at /trust/sub-processors, updated when materially new processors join production workflows. Enterprise customers receive notice per contract terms.
Where are the topic-specific buying guides?
GSDSI publishes procurement hubs at /identity-resolution, /location-intelligence, /ctv-acr, /privacy-compliance, and /alternative-data. Each hub links product routes, resources, and evaluation checklists for that category.