Skip to main content

The LinkedIn Conversions API Program for Offline Conversions

The LinkedIn Conversions API Program for Offline Conversions allows clients to send offline conversion data to the LinkedIn platform (including both the LinkedIn feed and LinkedIn Audience Network inventory). This allows customers to understand how LinkedIn campaigns drive offline conversions and provides an additional piece of data to help optimize ad spend or customer experience.

Note

The LinkedIn Conversions API Program for Offline Conversions was formerly known as "the LinkedIn Offline Conversions Attribution Program".

With the LinkedIn Conversions API Program, you can measure how your LinkedIn ads lead to real-world outcomes, such as in-store interactions, phone calls, product demos, purchases, bookings, and more. To help you understand the effectiveness of your ad campaigns, LinkedIn matches your uploaded offline events with metrics from people who saw or clicked on your ads on LinkedIn.

Use this to:

  • Track offline conversion activity and see how much of it can be attributed to your ads on LinkedIn.

  • Measure the offline return on your ad spend.

  • Optimize your LinkedIn ads targeting based on offline conversion signals.

  • Refine audience strategy across LinkedIn properties based on above results.

Overview of Steps Involved

The following steps need to be performed to enable the attribution analysis on LinkedIn:

  1. Send LiveRamp a sample conversion data file, and provide your LinkedIn Campaign Manager Account ID to your LiveRamp technical representative.

  2. Grant LiveRamp the ability to deliver data to your LinkedIn Campaign Manager Account by creating a LinkedIn Conversions API destination account and by performing OAuth authorization in LiveRamp Connect.

  3. LiveRamp creates an offline data segment, which is used to stream offline conversion events to LinkedIn, and sends you the offline data segment name (LinkedIn DMP ID).

  4. You activate your campaign(s) on LinkedIn.

  5. You perform activities in LinkedIn Campaign Manager to set up your offline conversions (create the conversions rule, select the campaigns, and select the offline data source).

  6. You send the list of conversion categories to LiveRamp.

  7. You upload conversion data.

  8. LiveRamp matches the data using our mapping of LinkedIn users.

  9. LiveRamp passes your conversion data file through LinkedIn’s Conversions API.

  10. You view the results within LinkedIn's Campaign Manager (results available within 24 hours).

See the appropriate sections below for more information on performing these steps.

Create a LinkedIn Conversions API Destination Account

To distribute offline conversions data, a LinkedIn user who has Account Manager-level access to your LinkedIn Campaign Manager Account will need to activate a LinkedIn Conversions API - Offline destination account in Connect.

C_LinkedIn_Attribution_Program-LinkedIn_DA_tile.png

LinkedIn Conversions API destination account tile

During destination account activation, you will need to perform OAuth authorization for that destination account, either by selecting an existing OAuth connection or by creating a new connection. This grants LiveRamp access to your LinkedIn-sponsored account in order to deliver data to your LinkedIn Campaign Manager account.

Follow the general instructions in "Activate a New Destination Account”, performing these additional steps:

C_LinkedIn_Attribution_Program-LinkedIn_DA_configuration.png

LinkedIn Conversions API destination account configuration

  1. Remove the end date to leave the end date open ended.

  2. Enter your 9-digit LinkedIn account ID in the Account ID field. This ID can be found in the URL when logging into Campaign Manager (after "/accounts/"). Contact your LinkedIn account representative if you’re unsure of which value to use here.

  3. In the Destination Account Name field, pick a unique and memorable name for this account. We'll suggest one for you but you can use any name you wish as long as it is less than 50 characters in length.

  4. To use one of your existing LinkedIn OAuth connections, select it from the OAuth Connection drop-down list and click Validate OAuth Connection.

  5. To create a new OAuth connection and validate that connection:

    1. From the OAuth Connection drop-down list, select + New LinkedIn OAuth Connection.

    2. From the new window that opens with LinkedIn's sign in or login screen, enter your credentials and then click Sign in.

      C-Authorize_DA_with_OAuth-LinkedIn-login-screen.jpg
  6. Click Validate OAuth Connection.

Perform Activities in LinkedIn Campaign Manager

Once LiveRamp has provided you with the offline data segment information, follow LinkedIn’s instructions to perform the following activities:

  • Create an offline conversion rule

  • Associate the appropriate campaigns with the conversion rule

  • Associate the appropriate offline data segment (provided by LiveRamp)

For each conversion category that you want to track, you’ll need to create an offline conversion rule in LinkedIn Campaign Manager.

Note

The recommendation is to use the maximum lookback window, which is 90 days.

Provide Conversion Categories to LiveRamp

Once you’ve performed the activities in LinkedIn Campaign Manager, provide your LiveRamp Implementation Manager with a list of the conversion category(s) that were specified in the offline conversion rule(s).

Note that the values you provide in the “transaction_category” field in the files you upload are used to map to the conversion categories. If there is a mismatch between values in the “transaction_category” field and the conversion categories names (such as when you’re repurposing conversion data files from another LiveRamp attribution program), you will need to provide LiveRamp with a mapping of transaction_category values to conversion categories names. For a list of LinkedIn-supported conversion categories, click here.

Mapping Example:

Transaction_category Value

LinkedIn Conversion Categories

In Store

Purchase

New Customer

Other

Existing Customer

Other

Note

Make sure to provide a corresponding conversion category for all values within the “transaction_category” field. Otherwise these transaction records will not be distributed to LinkedIn for attribution.

Formatting your Conversion File Data

Before sending your conversion data to LiveRamp, make sure to strictly follow the guidelines listed below:

Note

Caution

If an uploaded file does not meet these requirements, you will need to reformat the file until it is formatted correctly.

  • Headers must be included in the exact order as listed below and must match exactly.

  • If hashing email addresses, convert all characters to lowercase and remove all whitespace before hashing. For example, the plaintext email address "MyName@liveramp.com " must be changed to "myname@liveramp.com" before hashing.

  • This program uses our Measurement Enablement workflow. Make sure to follow our recommended file limits for Measurement Enablement workflow files (such as a maximum of 500,000,000 rows per file and a maximum uncompressed file size of 50 GB).

  • Your conversion data file must use one of our allowed delimiters (commas, tabs, or pipes), and be one of our allowed file types (.csv, .tsv, .psv, or .txt).

  • Include all of the required columns listed below.

  • Fields must not have leading or trailing white space.

  • Unless values are required for a field, fields can be left blank if there is no data for the given row (do not include “N/A” or “null”).

  • The file must be rectangular. That is every row must have the same number of delimiters and columns of data.

Tip

To download an Excel file template that contains all possible columns and formatting instructions, click here.

After transferring your data into the file template, be sure to delete the row with the formatting instructions and save the file in one of our allowed file types (.csv, .tsv, .psv, or .txt) before uploading.

Once the file has been formatted correctly, upload the file to LiveRamp. See the “Upload the File” section below for more information.

Note

Once you set up the file format for an existing conversions program feed, try to keep the file format (such as the column headers or the column order) the same for all subsequent files. If you change the file format for an existing feed, create a support case before uploading the new file to ensure your existing feeds are not impacted. For more information, see "Changing the Format of an Existing File".

List of All File Columns

See the table below for a list of columns and formatting instructions:

Field Name

Column Required?

Values Required?

Notes

first_name

Yes

Yes (if Name and Postal is used as an identifier)

last_name

Yes

Yes (if Name and Postal is used as an identifier)

address_1

Yes

Yes (if Name and Postal is used as an identifier)

address_2

Yes

No

  • Include values in this column if you have additional street address info for a given row.

city

Yes

Yes (if Name and Postal is used as an identifier)

state

Yes

Yes (if Name and Postal is used as an identifier)

  • Must be a two-character, capitalized abbreviation ("CA", not "California" or "Ca").

zip

Yes

Yes (if Name and Postal is used as an identifier)

  • ZIP codes can be in 5-digit format or 9-digit format (ZIP+4).

email_1

Yes

Yes (if email is used as an identifier)

  • Can be plaintext or one of our allowed hash types (SHA-256, MD5, or SHA-1).

  • If you have multiple emails for a consumer, send your best one in the “email_1” column.

email_2

Yes

No

  • Can be plaintext or one of our allowed hash types (SHA-256, MD5, or SHA-1).

email_3

Yes

No

  • Can be plaintext or one of our allowed hash types (SHA-256, MD5, or SHA-1).

email_4

Yes

No

  • Can be plaintext or one of our allowed hash types (SHA-256, MD5, or SHA-1).

transaction_category

Yes

Yes

  • The field for tracking transactions by conversion categories (see this list of conversion categories that LinkedIn accepts).

transaction_timestamp

Yes

Yes

  • Corresponds to the date/time of transaction in UTC - (example “2017-02-07T13:25:00Z-0800" should be the time the conversion happened in UTC).

  • Standard formats:

    • yyyy-MM-dd

    • yyyy-MM-dd'T'HH:mm:ss'Z'-0000 (for example, 2021-06-04T10:01:00Z-0000)

  • Additional formats:

    • MM/dd/yyyy h:mm:ss aa

    • MM,dd,yyyy h:mm:ss

    • MM/dd/yyyy HH:mm:ss

    • yyyy-MM-dd HH:mm:ss

    • yyyy-MM-dd'T'HH:mm:ss

    • yyyy-MM-dd HH:mm:ssZ

transaction_amount

Yes

Yes

  • Do not include any (currency) symbols.

  • Format required: XXX.XX

phone_1

Yes

Yes (if phone is used as an identifier)

  • Do not include any hyphens or parentheses.

  • Must be plaintext (no hashed phone numbers allowed).

  • If you have multiple phone numbers for a consumer, send your best one in the “phone_1” column.

phone_2

Yes

No

  • Do not include any hyphens or parentheses.

  • Must be plaintext (no hashed phone numbers allowed).

order_id

No

No

  • A unique ID (such as a transaction ID) that corresponds to the order that the particular item belongs to (this is often referred to as an “ordinal”). If the value is not unique, a partner may deduplicate some of these events when ingesting your conversion data.

  • To measure item-level events, the value will need to be a unique value for each item within a basket. LiveRamp recommends using the concatenated value of the order ID + product SKU. For example, if the order ID is “123” and SKU is “456”, the “order_id” value would be “123456”.

  • Do not include special characters, currency symbols, or commas.

Header Row Example

The headers shown below are all required.

email_1|transaction_category|transaction_timestamp|transaction_amount

Conversion Data Examples

alex@gmail.com|In Store|2014-03-31|99.99

julian@gmail.com|Offline|2014-03-30|55.55

Send Conversion Data to LiveRamp

To set up the integration, send us a sample conversion data file. This file should contain at least 25 rows and each row should have values for the required fields (you can use placeholder data). Include all the possible values you plan on using in the “transaction_category” field and include only those values in subsequent files.

Once your campaign has started, send conversion data to LiveRamp at your preferred cadence. Files can be delivered at any cadence (daily, weekly, monthly, etc.), but do not send more than one file per day. LiveRamp’s preference is daily or weekly.

Conversion Data Guidelines

Each conversion data record must include at least one PII identifier (name and postal address, email, or phone) and the required conversion data:

  • Transaction category

  • Transaction timestamp

  • Transaction amount

Make sure to also follow these additional guidelines:

  • Avoid sending duplicate transactions (transactions already sent to LiveRamp). If you send weekly or monthly files, only send transactions that occurred since the previous file was sent.

  • Do not include transactions that exceed the lookback window.

    Note

    The lookback window will be based on the conversion rule you create in LinkedIn Campaign Manager. LinkedIn only allows a maximum lookback window of 90 days for an offline conversion rule. As a result, make sure the transactions in your file are not older than 90 days from the current day.

  • Do not include conversions with a conversion date in the future.

Upload the File

Upload conversion data files using LiveRamp’s SFTP server or your SFTP server.

You can also have us pull files from an AWS S3 bucket or GCS bucket. See “Getting Your Data Into LiveRamp” for more information.

Caution

Files for this program cannot be uploaded via Connect. We recommend either uploading via our SFTP server or having us pull files from an S3 bucket.

After uploading, email your LiveRamp technical account specialist to confirm that you have uploaded conversion data.

Once the file is uploaded, information on file processing status can be viewed in Connect (see "Check File Processing Status" below for more information).

Once the file has finished processing, the data will be viewable within LinkedIn Campaign Manager.

C_LinkedIn_Attribution_Program-LinkedIn_Campaign_Manager.jpeg

Check File Processing Status

You can check the status of the files you've uploaded on the Files page in Connect. See "Check the Status of an Uploaded File" for complete instructions.

Note

  • Once you've uploaded a file, it can take up to 20 minutes before the file appears associated with the appropriate audience(s) on the Files page. If the file does not appear after at least 20 minutes, create a support case.

  • Files for this program use our Measurement Enablement workflow, and so the column headings that display on the Files page will look different from the ones that display for files that use our Activation workflow.

FAQs

How do lookback windows work?

LinkedIn can attribute conversions that happen up to 180 days in the past:

  • 90-Day Lookback Window: You can set a max lookback window of 90 days. For example, you can say, if this person saw an ad within 90 days of converting, count the conversion.

  • Converted 90-days ago: LinkedIn can track conversion events that happened up to 90 days in the past. For example, you upload your data that includes an offline purchase that occurred 89 days ago.

How long does it take to see results?

It can take up to 24 hours before you’ll see your conversion data within LinkedIn Campaign Manager.

Can we add additional conversion categories?

Yes, you can. Create a support case and specify the conversion categories you would like to add. If not, these transactions will not be delivered to LinkedIn.