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 you can then review total campaign 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 to 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 centre.

  • Frequency: Upload your file at least once a month and send conversion data within 30 days of each conversion occurrence to Pinterest
  • File size: Your file must be under 5 GB in size and contain fewer than 10 million rows
  • Delivery time: LiveRamp processes and delivers conversion events to Pinterest within 1-3 days. Your conversion data will be ready 48 hours after that.
  • Separate files for each account: Do not combine conversions from child accounts into a single file. Upload conversions separately for each child account.
    •
    CSV file specifications
    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 using 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 maximise user matching against LiveRamp’s database.
    madid Mobile ad IDs
    • Google ad ID
    		 AECE52E7-03EE-455A-B3C4-E57283966239 Any or all combinations of listed identifiers are accepted. We recommend that you provide as many as possible to maximise 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 maximise 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 maximise 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 maximise 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 maximise user matching against LiveRamp’s database.
    CITY See LiveRamp's article 'Formatting Name and Postal Addresses' for more info Manchester Any or all combinations of listed identifiers are accepted. We recommend that you provide as many as possible to maximise 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 maximise user matching against LiveRamp’s database.
    POSTCODE See LiveRamp's article 'Formatting Name and Postal Addresses' for more info M11 4DW Any or all combinations of listed identifiers are accepted. We recommend that you provide as many as possible to maximise user matching against LiveRamp’s database.
    POSTCODE4 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 maximise user matching against LiveRamp’s database.
    PHONE1

    Can be plaintext or hashed, with SHA1 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:

     

    • +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 maximise 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 as "known" and not "anonymous".

    		   Any or all combinations of listed identifiers are accepted. We recommend that you provide as many as possible to maximise 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 maximise 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 accept these formats:
    • dd/MM/yyyy hh:mm:ss aa
    • dd/MM/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
    • dd/MM/yyyy
    • Unix timestamp
    Transaction data should be uploaded within 14 days of the conversion.
     

    14/08/2012

    or

    14/08/2012 5:01:54 PM

    or

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

    		 Yes
    event_type

    Any of our standard conversion event types:

    • Signup
    • Checkout
    • Custom
    • ViewCategory
    • Search
    • AddToCart
    • WatchVideo
    • Lead

    If it's not included, we'll default to Checkout. 

    		 Checkout No
    source_type

    Add the event source type:

    • offline
    • app_android
    • app_ios
    • web

    If it's 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 can 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, such as SKUs and UPCs.

    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

     

    1. If a delivery fails, click into its row in Upload History in Ads Manager to review a drop-down list 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 of the original CSV files uploaded to LiveRamp and we delete files from LiveRamp after 48 hours in accordance with 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 next?

    Once you have your offline conversions data connected to Pinterest, find out more about Offline conversion events reporting.
    Still need help? Contact us
    Was this article helpful?

    How can we make this article better?