Datasys
Platform
Capabilities
Enterprise
Data Licensing & Delivery
License the data your business needs.
Bring Datasys identity, consumer, business, signal, and predictive data into your enterprise. Choose the products, coverage, usage rights, and delivery approach that fit your business—or put the intelligence to work in Datasys360.
Enterprise data licensing
Pricing built around your requirements.
Your data requirements determine the right license. A regional dataset for a one-time analysis has a different scope from a national identity product refreshed across enterprise systems.
Datasys builds pricing around the products, coverage, usage rights, volume, and delivery you need.
We work with your team to define the data, refresh schedule, evaluation, and support before preparing a pricing quote.
- Business objective
- Product family
- Coverage and scale
- Selected fields
- Permitted use
- Delivery and refresh
Flexible ways to work with Datasys
Choose how you use Datasys.
Operate in Datasys360
Explore audiences, understand markets, activate data, and measure results inside Datasys360.
License Datasys data
Bring selected identifiers, attributes, signals, scores, or audiences into your own systems through an agreed delivery method.
Enrich customer records
Add relevant Datasys attributes and intelligence to your existing customer records, with coverage and output defined for your use case.
Use both together
Use Datasys360 alongside licensed data or enriched records in your analytics, applications, and AI environments, with the appropriate use rights.
Built around your use case
Define the right data product.
Business objective
Start with what you want the data to help you do: understand customers, plan markets, build models, develop audiences, or measure results.
Your intended use guides the products, fields, rights, and evaluation approach.
Product and population
Choose the data family, audience, geography, and level of detail your business needs.
Datasys helps define whether person, household, business, vehicle, or geographic data best fits the question.
Data specification
Define the fields, identifiers, signals, scores, and volume your teams need, along with the expected coverage.
A clear data dictionary explains each field and distinguishes recorded information from linked or modeled insights.
Usage rights
Specify who can use the data, in which systems and markets, for what purpose, and for how long.
The agreement sets the boundaries for model development, derived outputs, sharing, redistribution, and restricted uses.
Evaluation and acceptance
Agree on how to assess fit before delivery. Criteria may include coverage, field availability, freshness, model performance, or technical compatibility.
Datasys defines an appropriate evaluation for the product and use case, including samples or technical validation where available.
Delivery that fits your systems
Delivery paths
| Delivery path | Best suited for | What must be confirmed |
|---|---|---|
| Datasys360 | Audience intelligence, activation, and measurement inside the platform | Platform capabilities, users, workflows, and data access |
| Enriched records | Adding selected Datasys fields to your existing records | Identifiers, fields, coverage, output format, and refresh |
| Managed file | One-time or recurring datasets for your existing processes | Fields, format, secure transfer, refresh, and versioning |
| Data-product API | Programmatic access to supported data products | Product availability, authentication, volume, and support |
| Configured integration | Connecting supported Datasys data flows to your environment | Systems, access controls, data flows, and implementation |
| Combined approach | Datasys360 alongside licensed datasets or enriched records | Platform access, licensed outputs, usage rights, and delivery |
Datasys360
- Best suited for
- Audience intelligence, activation, and measurement inside the platform
- What must be confirmed
- Platform capabilities, users, workflows, and data access
Enriched records
- Best suited for
- Adding selected Datasys fields to your existing records
- What must be confirmed
- Identifiers, fields, coverage, output format, and refresh
Managed file
- Best suited for
- One-time or recurring datasets for your existing processes
- What must be confirmed
- Fields, format, secure transfer, refresh, and versioning
Data-product API
- Best suited for
- Programmatic access to supported data products
- What must be confirmed
- Product availability, authentication, volume, and support
Configured integration
- Best suited for
- Connecting supported Datasys data flows to your environment
- What must be confirmed
- Systems, access controls, data flows, and implementation
Combined approach
- Best suited for
- Datasys360 alongside licensed datasets or enriched records
- What must be confirmed
- Platform access, licensed outputs, usage rights, and delivery
Delivery options vary by product. We’ll confirm the supported approach, technical requirements, and refresh schedule with your team.
ENTERPRISE CONNECTIVITY. CONTROLLED ACCESS.
Configure access around your enterprise’s requirements, with managed API enablement, API keys, and IP restrictions where needed. Datasys works with your team to establish how systems connect and which environments can exchange data.
Bring intelligence into more of your business while keeping control over how it is accessed and used.
Getting started
A clear path to delivery.
01
Scope
Tell us your business objective, the data you need, and where you plan to use it. Together, we define what a useful result looks like.
02
Evaluate the fit
We review product availability, coverage, and delivery requirements. Where appropriate, a sample, file assessment, or technical validation helps your team evaluate fit against the agreed criteria.
03
Agree on the scope
Define the product, fields, coverage, delivery, and refresh schedule. The agreement sets usage rights, privacy and security requirements, support, and each team’s responsibilities.
04
Deliver and operate
Set up delivery, validate the data, and establish the agreed refresh and support process. Review changes as your requirements evolve.
Rights and responsibilities
Clear terms from the start.
What we define
- Available products, field definitions, and use restrictions
- How customer data is handled and used
- Suppression and privacy-choice requirements
- Delivery, refresh, support, and retention terms
- Coverage, freshness, evaluation criteria, and product limitations
What you share
- Your business objective, required data, and destination
- The teams, partners, and systems that will use the data
- Your retention, deletion, security, modeling, and sharing requirements
- Relevant legal requirements and internal policies
- How you will evaluate success
What the agreement covers
The agreement defines permitted uses, product coverage, sharing and redistribution rights, support, change handling, and offboarding. AI training and inference rights must be agreed explicitly, including how the data and resulting outputs may be used.
Data licensing questions
Licensing FAQ
Answers about pricing, evaluation, and delivery.
Pricing depends on the data products, fields, coverage, volume, usage rights, and delivery you need. Refresh frequency, implementation, evaluation, and support can also affect the scope. We define those requirements with you and provide a pricing quote.
API access is available for supported products and workflows. Other products may be delivered as files, enriched records, or through Datasys360. We’ll confirm the available delivery options and technical requirements for the data you need.
We’ll work with you to define an appropriate evaluation. Depending on the product and intended use, that may include a representative sample, file or coverage assessment, model evaluation, or technical validation. We agree on the evaluation criteria and any limitations before you begin.
Get the data your business needs.
Tell us what you want to achieve, the data you need, and where you plan to use it. We’ll help define the right products, licensing scope, and delivery approach.