Upload conversions with LiveRamp

Upload offline conversions to LiveRamp, who will match conversions to Pinterest IDs and send them to Pinterest. Pinterest then matches relevant campaigns to these conversions, and you can then pull relevant reporting for these uploaded conversions in Ads Manager

Before you get started

  • Make sure you have an active campaign.
  • Confirm participation with LiveRamp and pass specific Pinterest Advertiser IDs to LiveRamp.
  • If a parent Pinterest advertiser account contains multiple child accounts, pass unique Pinterest advertiser IDs for each child account to LiveRamp. 

Get your data into LiveRamp

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 LiveRamp's help center.

  • Frequency: Upload at a regular interval, at least once a month. Send conversion data within 30 days of each conversion occurrence to Pinterest on a monthly or more frequent cadence.
  • File size: Files must be under 5GB in size and contain less than 10M rows.
  • Delivery time: LiveRamp processes and delivers conversion events to Pinterest within 1-3 days. Your conversions data will be ready 48 hours after that.
  • Separate files for each account: Don't combine conversions from child accounts into a single file. Upload conversions separately for each child account.

 

CSV file specifications

Customer data fields

Column name Description Example Required? 

email

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, MD5 hashing, use lowercase characters and remove extra spaces before, after, or between email address.

example [at] 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
  • Google Ad ID 
  • Apple IDFA
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 help 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 help 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 help 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 help 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 help 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 help 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 help 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 help 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 help article "Formatting Phone Numbers" for more information.

Phone numbers can be used to match with or without any additional PII, 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:

 

  • +1XXXXXXXXXX
  • +1 (XXX) XXX-XXXX
  • (XXX) XXX-XXXX
  • XXX-XXX-XXXX
  • XXX XXX XXXX
  • XXXXXXXXXX  (this format must be used if hashing)
     
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 help article "Formatting Custom IDs" for more information. Note: If a custom ID is tied to PII, 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 help 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 help article "Formatting IdentityLinks" for more information. See “IdentityLink (IDL)” for examples. Inclusion of IDL is optional and cannot be combined with any other Customer Data Fields or PII (personally identifiable information). 
Event Data Fields
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 will accept these formats:
  • MM/dd/yyyy hh:mm:ss aa
  • MM/dd/yyyy HH:mm:ss
  • yyyy-MM-dd HH:mm:ss
  • yyyy-MM-ddTHH:mm:ss
  • yyyy-MM-dd HH:mm:ss+zzzz
  • yyyy-MM-ddTHH:mm:ss+zzzz
  • yyyy-MM-dd
  • MM/dd/yyyy
  • Unix timestamp

Transaction data should be uploaded within 14 days of the conversion
 

08/14/2012

or

08/14/2012 5:01:54 PM

or

2019-08-14T12:32:42+0700

Yes
event_type

Default to Checkout

Checkout Yes
source_type 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 - preferred for checkout events
quantity Number items of purchased 15

No

product_id The item number field may contain an alphanumeric value with no special characters, currency symbols or commas; this field allows you to split a transaction into multiple events by using unique product ids, i.e. SKUs, UPCs etc., for each item that is associated with the same transaction-id

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 Sub-category of 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

 

Troubleshoot delivery failure
  1. If a delivery fails, click into its row in Conversion Upload History to review a dropdown displaying information on reasons for failure.
  2. Click into View Data Errors to examine the invalid data values in the delivery file. 
  3. Pinterest has no visibility into the original csv files from 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.

What's the next step?

Learn about offline conversion events reporting

Still need help?
Contact us