Upload offline conversions to LiveRamp. LiveRamp will then match conversions to Pinterest IDs and report them back to us. We then match relevant campaigns to these conversions, so that you can then review total campaign conversions in Ads Manager
After you provide LiveRamp with your Pinterest advertiser IDs, LiveRamp will pass conversion data back to Pinterest. For help getting your data into LiveRamp, see
Column name | Description | Example | Required? |
---|---|---|---|
|
Up to 4 email addresses (can have up to 4 columns with the header name email or email_1, email_2, email_3, email_4) If SHA256, SHA1 or MD5 hashing, use lowercase characters and remove extra spaces before, after, or between email address. |
example@email.com |
Any or all combinations of listed identifiers are accepted. We recommend that you provide as many as possible to maximize user matching against LiveRamp’s database. |
madid | Mobile ad IDs
|
AECE52E7-03EE-455A-B3C4-E57283966239 |
Any or all combinations of listed identifiers are accepted. We recommend that you provide as many as possible to maximize user matching against LiveRamp’s database. |
FIRSTNAME |
See LiveRamp's article "Formatting Name and Postal Addresses" for more info | John | Any or all combinations of listed identifiers are accepted. We recommend that you provide as many as possible to maximize user matching against LiveRamp’s database. |
LASTNAME | See LiveRamp's article "Formatting Name and Postal Addresses" for more info | Smith | Any or all combinations of listed identifiers are accepted. We recommend that you provide as many as possible to maximize user matching against LiveRamp’s database. |
ADDRESS1 | See LiveRamp's article "Formatting Name and Postal Addresses" for more info | 400 Church St | Any or all combinations of listed identifiers are accepted. We recommend that you provide as many as possible to maximize user matching against LiveRamp’s database. |
ADDRESS2 | See LiveRamp's article "Formatting Name and Postal Addresses" for more info | Apt 123 | Any or all combinations of listed identifiers are accepted. We recommend that you provide as many as possible to maximize user matching against LiveRamp’s database. |
CITY | See LiveRamp's article "Formatting Name and Postal Addresses" for more info | San Francisco | Any or all combinations of listed identifiers are accepted. We recommend that you provide as many as possible to maximize user matching against LiveRamp’s database. |
STATE | See LiveRamp's article "Formatting Name and Postal Addresses" for more info | CA | Any or all combinations of listed identifiers are accepted. We recommend that you provide as many as possible to maximize user matching against LiveRamp’s database. |
ZIP | See LiveRamp's article "Formatting Name and Postal Addresses" for more info | 94112 | Any or all combinations of listed identifiers are accepted. We recommend that you provide as many as possible to maximize user matching against LiveRamp’s database. |
ZIP4 | See LiveRamp's article "Formatting Name and Postal Addresses" for more info | 1234 | Any or all combinations of listed identifiers are accepted. We recommend that you provide as many as possible to maximize user matching against LiveRamp’s database. |
PHONE1 |
Can be plaintext or hashed, with SHA-1 hashes accepted. See LiveRamp's article "Formatting Phone Numbers" for more info. Phone numbers can be used to match with or without any additional PII (personally identifiable information), and can be used to match in conjunction with first and last name (similarly to NAP) for greater accuracy. Note: EU data files cannot contain hashed phone numbers. |
Allowed formats:
|
Any or all combinations of listed identifiers are accepted. We recommend that you provide as many as possible to maximize user matching against LiveRamp’s database. |
CCID |
Custom IDs are assigned to users by a specific platform, such as Google or Facebook. See LiveRamp's article "Formatting Custom IDs" for more info. Note: If a custom ID is tied to PII (personally identifiable information), it is considered "known" and not "anonymous". |
Any or all combinations of listed identifiers are accepted. We recommend that you provide as many as possible to maximize user matching against LiveRamp’s database. | |
cookie | Data that is set by a website when a particular user’s browser visits that site. See LiveRamp's article "Formatting Cookies" for more information. | Any or all combinations of listed identifiers are accepted. We recommend that you provide as many as possible to maximize user matching against LiveRamp’s database. | |
IDL | LiveRamp’s identifier that is tied to devices in the LiveRamp Identity Graph. See LiveRamp's article "Formatting IdentityLinks" for more info. | See LiveRamp’s article “IdentityLink (IDL)” for examples. | Inclusion of IDL is optional and cannot be combined with any other Customer Data Fields or PII (personally identifiable information). |
Column name | Description | Example | Required? |
---|---|---|---|
event_time (Please do not compile data using Excel so as to avoid auto-correct) |
Unix timestamps are recommended. We'll accept these formats:
|
08/14/2012 or 08/14/2012 5:01:54 PM or 2019-08-14T12:32:42+0700 |
Yes |
event_type |
Any of our standard conversion event types:
If not included we'll default to Checkout. |
Checkout | No |
source_type |
Add the event source type:
If not included we'll default to offline. |
offline | Yes |
value | Cost of product on the row. | 500.00 | Yes for checkout |
order_id | A contiguous identifier for the offline transaction, 64 character limit. | X-151481 | Optional but preferred for Checkout events |
quantity | Number of items purchased. | 15 |
No |
product_id | The item number field may contain an alphanumeric value with no special characters, currency symbols or commas. This field lets you split a transaction into multiple events by using unique product IDs, for each item that is associated with the same transaction-ID like SKUs, UPCs, etc. |
108 or F28 |
No |
currency | Currency paid. |
USD CAD |
No |
property | Website property that the item is purchased from. | brandsite.com | No |
product_name | Short name of the product. | Gabrielle chair | No |
promo_code | Promotion that was used for the purchase. | Winter 10 | No |
product_category | Top level category of product. | furniture | No |
product_sub_category | Subcategory of the product. | chair | No |
product_variant | Any product variation identifiers of the product. |
red or leather |
No |
product_brand | Brand name of the product. | Gabrielle | No |
is_new_customer |
New customer (Y) Existing customer (N) |
Y | No |
- If a delivery fails, click into its row in Upload History in Ads Manager to review a dropdown list displaying information on reasons for failure.
- Click into View Data Errors to examine the invalid data values in the delivery file.
- Pinterest has no visibility into the original CSV files uploaded to LiveRamp and we delete files from LiveRamp after 48 hours per data retention policies. To troubleshoot issues, you should work with LiveRamp and/or refer to the invalid data values in the original uploaded file.
Once you have your offline conversions data connected to Pinterest, learn about