Loader Pinterest Audience

Pinterest Audience enables businesses to connect with visually driven, highly engaged users through tailored and creative ad campaigns. By leveraging advanced targeting options, brands can segment audiences and deliver personalized content, inspiring meaningful engagement and driving better campaign outcomes.

Business Value in CDP

Integrating Meiro’s Customer Data Platform (CDP) with Pinterest Audience empowers businesses to refine targeting and engagement strategies. Meiro’s CDP analyzes and segments customer data to create detailed audience profiles based on user behaviors and preferences. These profiles are then seamlessly uploaded to Pinterest for precise ad targeting.

This integration ensures personalized campaigns reach the right users, such as those who have interacted with specific products or shown interest in content relevant to your brand, amplifying engagement and boosting campaign success.

Steps for setting up Pinterest Audience Loader

Follow this step-by-step guide to configure the component:

Set up the loader within Meiro Integration by following the instructions provided in this article.
Set up the loader as a destination in CDP. Read here.
Export your segmented customer profiles. Refer to this ~~article.~~article.

Setting up the loader in MI

To set Pinterest Audience as a destination within Meiro Integration, use the Pinterest Audience loader component.

Component Process:

Reads the configuration file, extracts credentials and audience parameters.
Extracts customer IDs from customers.csv file, and hashes them if needed.
Loads the customer IDs to Pinterest.

Requirements

Before proceeding with the setup, ensure that you have the OAuth2 access token and account ID available. These credentials are essential and must be entered in the configuration settings to authenticate and authorize requests sent via the Pinterest API.

Data In/Data Out

Data In

The loader requires an input file named /data/in/tables/customers.csv. The file must include a column named customer_id.
The file should contain only one column with customer profiles.

Valid Profiles:

Emails:
- Must be in lowercase and can be in plain text or hashed (SHA1, SHA256, MD5).
Mobile Advertising IDs (MAIDs):
- Can be cleartext or hashed using SHA1, SHA256, or MD5.
- Android AAIDs: Must be lowercase and follow the format 8-4-4-4-12 (e.g., 123e4567-e89b-12d3-a456-426614174000).

Example:

customer_id

vincenoir@mail.com

howardmoon@mail.com

Data Out

N/A

Learn more: about folder structure in configuration here.

Parameters

Hash customer ID	Set it to true if the data needs to be hashed; otherwise, set it to false. Supported hashing algorithms are SHA1, SHA256, or MD5.
Ad account ID (required)	A unique identifier for an ad account (maximum 18 characters). This parameter is mandatory.
Audience name	The name of the audience. This is required when creating a new audience.
Audience ID	If left empty, a new audience will be created. If an existing Audience ID is provided, the Audience Operation parameter must also be specified to define how the audience should be updated (e.g., add or replace).
Audience operation	Specifies the action to perform on the audience: `add` - To append new records to the existing audience. `replace` - Replaces data from the input file with data contained in the audience. Example Workflow Input Configuration: { "parameters": { "hash_customer_id": false, "ad_account_id": "12345", "audience_id": "123", "audience_operation": "replace" } } Outcome: The audience with ID 123 will entirely have its customer list replaced with the new customer data from customers.csv.

Hashing Customer Data for Secure Uploads

Hashing ensures that sensitive data, like plain-text emails, is securely transformed into an encrypted format before sharing. Pinterest supports three hashing methods: SHA1, SHA256, and MD5.
If your data is already hashed using one of these methods, the loader will use it as-is. If the data in customers.csv is not hashed, the loader will automatically hash it using SHA256, the recommended algorithm for security and compatibility.
For example, an email like vincenoir@mail.com would be securely transformed into a hashed version, such as b85f5c5c506dd6b86d0de4693476bb1720d162f1b194d06fa8f1a9e6ef4cd97c. This ensures that customer data remains protected during the upload process.
To avoid errors, ensure the same hashing method is used consistently across all platforms.

Remember:
If audience_id is provided, the specified audience_operation (e.g., add or replace) will be applied to the audience associated with this ID.
If audience_id is not provided, the audience_name parameter must be used to create a new audience.

For detailed information about the Pinterest API, refer to the official Pinterest API Documentation.