# Cint — Vendor Intelligence Profile
> Source: Vedex (https://vedex.ai) | Generated: 2026-10-05T08:33:27.317Z

## Overview

- **Description**: Cint audience segments are built from fully consented and continuously verified data from millions of global consumers who enter our research platform each year to answer surveys.
License Cint Verified Audiences to enrich, validate, and activate your customer data, or build custom research audiences for tailored survey-based insights.
Enrich your first party with additional or new demographic data on your consumers
Build a proprietary audience using modelling to combine your data with Cint Verified Audiences
Validate your customer or first-party data with Cint Verified Audiences
Available Demographic Data
Cint matches against
Hashed Emails (HEM - SHA256, SHA1 or MD5)
,
Mobile Ad IDs (MAID)
and
IP addresses
to provide all the following attributes from
all available countries
in our platform per matched identifier with
a 365-day lookback
period for HEMs and MAIDs and a
2-day lookback
period for IP Addresses:
Age
Gender
Household Income
Education
Employment
Industry
Parental Status
Relationship Status
Lookback Periods:
for HEMs and MAIDs: 365-day lookback period.
for IP addresses: Configurable lookback period between 1 and 30 days (default is 2 days).
Note:
Max 3 attribute sets per identifier will be provided.
The attributes data connected to HEMs and MAIDs are updated every two weeks, and the attributes data connected to IP addresses are updated daily.
How to Use: Manual SQL vs Streamlit App
Cint Verified Audiences can be used in two ways, depending on your preference. Choose the method that best fits your workflow:
Use manual SQL for automation, scripting, or integration.
Use the Streamlit app for an interactive, guided experience.
Manual SQL Usage
You can interact directly with the application by calling the matching procedures in your Snowflake worksheet.
Setup Reference:
Before running any match, you must set up a reference to your table or view containing the identifiers (HEMs, MAIDs, or IP addresses). A reference is a pointer to a table or view in your Snowflake account that contains the identifiers you want to match (e.g., hashed emails, device IDs, or IP addresses). This step is required so the app knows which of your tables to use for matching.
Ensure your table/view contains the required column(s) for the identifier type:
For HEMs: columns named 'HEMSHA256', 'HEMSHA1', or 'HEMMD5'
For MAIDs: column named 'MAID'
For IP addresses: column named 'IPADDRESS'
Use the following SQL command to set the reference (replace '<database.schema.table>' with your actual table/view path):
For Hashed Emails:
CALL core.update_reference(
       'hems',
       'ADD',
       SYSTEM$REFERENCE(
           'table', 
           '<database.schema.table>',
           'PERSISTENT',
           'references',
           'select'
       )
   );
For Device IDs:
CALL core.update_reference(
       'maids',
       'ADD',
       SYSTEM$REFERENCE(
           'table', 
           '<database.schema.table>',
           'PERSISTENT',
           'references',
           'select'
       )
   );
For IP Addresses:
CALL core.update_reference(
       'ip_addresses',
       'ADD',
       SYSTEM$REFERENCE(
           'table', 
           '<database.schema.table>',
           'PERSISTENT',
           'references',
           'select'
       )
   );
You can check if the reference is set by calling:
SELECT SYSTEM$GET_REFERENCE('hems');
   SELECT SYSTEM$GET_REFERENCE('maids');
   SELECT SYSTEM$GET_REFERENCE('ip_addresses');
If you need to change the reference to a different table/view, simply repeat the above steps with the new table/view.
Important Notes:
Each reference must point to a table/view with the correct column name and type for the identifier.
At least 50 distinct identifiers are required in the referenced column for matching to work.
You can update or reset the reference at any time.
Get Match Count:
To get the count of matching identifiers, use:
CALL core.get_match_count('<IDENTIFIER_TYPE>'[, <IP_ADDRESS_AGE_IN_DAYS>]);
Where '<IDENTIFIER_TYPE>' is one of:
'HEMSHA256'
'HEMSHA1'
'HEMMD5'
'MAID'
'IPADDRESS'
For IPADDRESS, you can optionally specify the lookback period (in days) as the second argument (between 1 and 30, default is 2).
Example:
CALL core.get_match_count('HEMSHA256');
CALL core.get_match_count('MAID');
CALL core.get_match_count('IPADDRESS', 7); -- 7-day lookback for IP addresses
CALL core.get_match_count('IPADDRESS');    -- default 2-day lookback
Get Match Data:
You can retrieve the matched audience data:
CALL core.get_match('<IDENTIFIER_TYPE>'[, <IP_ADDRESS_AGE_IN_DAYS>]);
For IPADDRESS, you can optionally specify the lookback period (in days) as the second argument (between 1 and 30, default is 2).
Example:
CALL core.get_match('HEMSHA256');
CALL core.get_match('MAID');
CALL core.get_match('IPADDRESS', 7); -- 7-day lookback for IP addresses
CALL core.get_match('IPADDRESS');    -- default 2-day lookback
Using the Streamlit App
A user-friendly Streamlit app is included for interactive usage.
Steps:
Open the Streamlit app from the
- **Domain**: cint.com
- **Contact Email**: ds@cint.com
- **Company Website**: https://cint.com

## Categories & Sectors

- **Categories**: Demographics

## Marketplace Presence

- **Source Platforms**: snowflake_marketplace
- **Platform Count**: 1

## Intelligence Scores

- **Vendor Score**: 18.5
- **Market Presence**: 12.3
- **Integration**: 20
- **Business Maturity**: 3.2

## Links

- Vedex Profile: https://vedex.ai/vendor/cint-bb731f
- Due Diligence: https://vedex.ai/due-diligence/cint-bb731f