Cint Verified Audiences

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

<p><br/></p>

# **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

<p><br/></p>

**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).

<p><br/></p>

**Note:**

1. Max 3 attribute sets per identifier will be provided.
2. The attributes data connected to HEMs and MAIDs are updated every two weeks, and the attributes data connected to IP addresses are updated daily.

<p><br/></p>

# **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.

<p><br/></p>

## Manual SQL Usage

You can interact directly with the application by calling the matching procedures in your Snowflake worksheet.

<p><br/></p>

**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.<br/>

1. 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'

<p><br/></p>

2. Use the following SQL command to set the reference (replace '<database.schema.table>' with your actual table/view path):

<p><br/></p>

For Hashed Emails:

```javascript
CALL core.update_reference(
'hems',
'ADD',
SYSTEM$REFERENCE(
'table',
'<database.schema.table>',
'PERSISTENT',
'references',
'select'
)
);
```

<p><br/></p>

For Device IDs:

```javascript
CALL core.update_reference(
'maids',
'ADD',
SYSTEM$REFERENCE(
'table',
'<database.schema.table>',
'PERSISTENT',
'references',
'select'
)
);
```

<p><br/></p>

For IP Addresses:

```javascript
CALL core.update_reference(
'ip_addresses',
'ADD',
SYSTEM$REFERENCE(
'table',
'<database.schema.table>',
'PERSISTENT',
'references',
'select'
)
);
```

<p><br/></p>

3. You can check if the reference is set by calling:

```javascript
SELECT SYSTEM$GET_REFERENCE('hems');
SELECT SYSTEM$GET_REFERENCE('maids');
SELECT SYSTEM$GET_REFERENCE('ip_addresses');
```

<p><br/></p>

4. If you need to change the reference to a different table/view, simply repeat the above steps with the new table/view.

<p><br/></p>

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.

<p><br/></p>

<p><br/></p>

**Get Match Count:**

To get the count of matching identifiers, use:

```javascript
CALL core.get_match_count('<IDENTIFIER_TYPE>'[, <IP_ADDRESS_AGE_IN_DAYS>]);
```

Where '<IDENTIFIER_TYPE>' is one of:

- 'HEMSHA256'
- 'HEMSHA1'
- 'HEMMD5'
- 'MAID'
- 'IPADDRESS'

<p><br/></p>

For IPADDRESS, you can optionally specify the lookback period (in days) as the second argument (between 1 and 30, default is 2).

<p><br/></p>

Example:

```javascript
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
```

<p><br/></p>

**Get Match Data:**

You can retrieve the matched audience data:

```javascript
CALL core.get_match('<IDENTIFIER_TYPE>'[, <IP_ADDRESS_AGE_IN_DAYS>]);
```

<p><br/></p>

For IPADDRESS, you can optionally specify the lookback period (in days) as the second argument (between 1 and 30, default is 2).

<p><br/></p>

Example:

```javascript
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
```

<p><br/></p>

## Using the Streamlit App

A user-friendly Streamlit app is included for interactive usage.

<p><br/></p>

**Steps:**

1. Open the Streamlit app from the Snowflake Marketplace listing or your Snowflake UI.
2. Select the identifier type tab: Hashed Emails, Device IDs, or IP Addresses.
3. Setup the reference to your table/view using the provided button.
4. For Hashed Emails, select the encoding type (SHA256, SHA1, MD5).
5. Click "Get Count" to see the number of matches (calls core.get_match_count).
6. Click "Get Data" to retrieve the matched audience data (calls core.get_match).

<p><br/></p>

**Notes:**

The Streamlit app provides a guided workflow for reference setup and matching. All matching operations performed in the app use the same backend procedures as manual SQL calls.

<p><br/></p>

<p><br/></p>

# **Privacy features**

Cint Verified Audiences is built on the Snowflake Native App framework and runs entirely in your own Snowflake instance. Licensing Cint Verified Audiences through Snowflake will not expose your identifiers to Cint or any other external users, meaning that your first-party data stays private.

原始信息汇总

Cint Verified Audiences 数据集概述

数据集基本信息

• 提供方: Cint
• 定价: 起始价 $1,000/月 + 使用费
• 试用: 限时3天试用

数据集描述

Cint Verified Audiences 数据集包含来自全球数百万消费者的完全同意和持续验证的数据。这些数据可用于丰富、验证和激活客户数据，或构建定制研究受众以获得量身定制的调查见解。

主要功能

• 数据丰富: 使用额外的或新的人口统计数据丰富您的第一方数据。
• 专有受众构建: 通过建模将您的数据与Cint Verified Audiences结合，构建专有受众。
• 数据验证: 使用Cint Verified Audiences验证您的客户或第一方数据。

可用人口统计数据

Cint 可匹配以下标识符并提供以下属性：

• 匹配标识符:
  • Hashed Emails (HEM - SHA256, SHA1或MD5)
  • Mobile Ad IDs (MAID)
  • IP地址
• 属性:
  • 年龄
  • 性别
  • 家庭收入
  • 教育
  • 就业
  • 行业
  • 父母状态
  • 关系状态
• 覆盖范围: 所有可用国家
• 回溯期: 90天
• 更新频率: 每两周更新一次
• 限制: 每个标识符最多提供3个属性集

隐私特性

• 基于Snowflake Native App框架构建，完全在用户自己的Snowflake实例中运行。
• 通过Snowflake许可不会将您的标识符暴露给Cint或任何其他外部用户。

商业需求

1. 用户数据丰富: 使用Cint Verified Audience数据丰富客户分析数据。
2. 验证客户分析: 匹配全球超过2.5亿用户的直接收集和明确同意的标识符。
3. 构建客户研究细分: 创建自己的受众以进行详细的行为、意见和心理研究。

使用示例

• 付费: 通过匹配提供的标识符提取人口统计数据。
  • 示例过程调用: sql CALL core.get_match(EMAIL, SHA256); CALL core.get_match(EMAIL, SHA1); CALL core.get_match(EMAIL, MD5); CALL core.get_match(DEVICEID, NONE); CALL core.get_match(IPADDRESS, NONE);

安全性

• 安全审查: 已完成Snowflake安全审查。
• 基于角色的访问控制: 数据受Snowflake基于角色的访问控制保护。

其他资源

• 文档: 提供详细文档。
• 云区域可用性: 支持多个AWS区域，包括:
  • 亚太地区（孟买）
  • 亚太地区（大阪）
  • 亚太地区（首尔）
  • 亚太地区（新加坡）
  • 以及其他35个区域。

联系方式

• 销售: [e-mail]
• 支持: [e-mail]