Skip to main content

Distribute Data To LinkedIn

See the sections below for distributing first-party data or Data Marketplace data to LinkedIn.

LinkedIn requires that an authorization using OAuth be performed by a user with the appropriate permission level before any distributions can be made to LinkedIn. For more information, see the "Performing OAuth Authorization for LinkedIn" section below.

Note

OAuth credentials at LinkedIn expire 1 year after authorization. After 1 year (or if you notice your distributions are not going through), perform OAuth authorization at LinkedIn again.

Overview of the LinkedIn Integration

See the table below for an overview of LiveRamp's integration for LinkedIn:

Caution

The information listed below was current at the time of publication and represents our best understanding of the integration based on the information available at the time, including information given to us by the destination platform. Any sections not filled out are areas we did not have information on at the time of publication. Use this as a general guide, but check with the platform to confirm any areas that are critical to your use case.

Note

For detailed information on the distribution options, see the additional sections below.

Category

Area

Info

Notes

Delivery/Matching

Identifiers that can be delivered

  • Cookies: No

  • Mobile device IDs: No

  • RampIDs: No

  • CTV IDs: No

  • CIDs/Platform IDs: No

Lookback window

Time to live

Precision levels allowed

  • Individual: Yes

  • Household: Yes

  • Neighborhood: Yes

For more information, see "Precision Levels".

Allowed input data types

  • Offline (PII): Yes

  • Online: No

Enabled for Record Sync

Yes

For more information, see "Keep Destination Data Fresh with Record Sync".

Accepts raw fields

Yes

For more information, see “Platforms that Do Not Accept Raw Fields”.

Duplicate segment names allowed

Configuration

Account info needed

  • Account ID: The 9 digit LinkedIn account ID

  • Reporting Contact Email

For more information, see the sections below.

Requires OAuth authorization

Yes

Additional data restrictions

For information on LiveRamp’s standard data restrictions, see “LiveRamp Data Restrictions” and “Data Marketplace Segment Review and Approval”.

Requires LiveRamp action to activate destination account

Yes

Data Marketplace

Accepts Data Marketplace data

  • Standard segments: Yes

  • Custom segments: Yes

  • Syndication: No

For more information, see the “Distribute Data Marketplace Data to LinkedIn” section below.

Data Marketplace pricing used

Advertiser Direct

Additional Data Marketplace limitations or guidelines

Additional Information

Can display matched reach in Connect

Yes

For more information, see “Destinations that Do Not Support Matched Reach Stats”.

Limit on number of audiences per seat ID in the platform

Exposure logs available

LiveRamp Conversions API program available

Yes

For more information, see "The LinkedIn Conversions API Program for Offline Conversions".

LinkedIn Integration Options

When activating a LinkedIn destination account, the following integration options are available:

Integration Name

Data Type

Who It's For

Use

Distributing US first-party data to LinkedIn

First-party data

  • Advertisers

LinkedIn (US) First-Party Data

Distributing US first-party data to LinkedIn and utilizing Record Sync

First-party data

  • Advertisers

[Record Sync] LinkedIn (US) First-Party Data

Distributing US Data Marketplace standard segments (third-party data) to LinkedIn

Data Marketplace data

  • Data buyers

  • Data sellers

LinkedIn (US) Data Marketplace

Distribute First-Party Data to LinkedIn

To distribute first-party data to LinkedIn, activate the appropriate “LinkedIn First-Party Data” destination account tile for your country or region by following the instructions in "Activate a New Destination Account."

Note

The non-US integrations are currently in a closed beta. If you’re interested in being considered to participate, contact your LiveRamp representative.

When distributing your first-party data to LinkedIn, two integration options are available:

  • A Record Sync-enabled first-party data integration, which keeps your data fresh at the destination by enabling data refreshes to utilize user deletions (see "Keep Destination Data Fresh with Record Sync" for more information).

    Note

    Record Sync is currently only available to US customers.

  • A first-party data integration that is not enabled for Record Sync.

Once you’ve activated the destination account, follow our instructions in Distribute Data to a Destination.Distribute Data to a Destination

Configure the Required Properties

When activating a LinkedIn First-Party Data destination account, use the following guidelines to configure the required properties:

  • End Date: Not needed, leave open-ended.

  • Account ID: The 9-digit LinkedIn account ID. 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.

  • Destination Account Name: 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.

Enable and Validate an OAuth Connection

Follow the instructions in “Validate OAuth Connection During Destination Account Activation” and "Perform OAuth Authorization for LinkedIn" below to enable and validate an OAuth connection for the LinkedIn destination account.

Distribute Data Marketplace Data to LinkedIn

To distribute Data Marketplace data to LinkedIn, activate the appropriate “LinkedIn Data Marketplace” destination account tile for your country or region by following the instructions in "Activate a New Destination Account."

In addition, keep the following guidelines in mind:

  • Distributing Data Marketplace data to this platform goes through LiveRamp’s Advertiser Direct program, which requires a separate agreement and follows a different process from Data Marketplace distribution to other platforms. For more information, see “Implementing LiveRamp's Advertiser Direct Solution”.

  • The Advertiser Direct program requires that data sellers share their custom segments with the data buyer within Connect. See “Implementing LiveRamp’s Advertiser Direct Solution” for more details.

  • All advertisers (and agencies acting on behalf of advertisers) are required to report their usage of all LiveRamp Data Marketplace data distributed to this platform on a monthly basis. See “Report Usage for Data Marketplace Distributions to Advertiser Direct Destinations” for instructions on how to pull reports.

  • The non-U.S. integrations are currently in a closed beta. If you’re interested in being considered to participate, contact your LiveRamp representative.

Configure the Required Properties

When activating a LinkedIn Data Marketplace destination account, use the following guidelines to configure the required properties:

  • End Date: Not needed, leave open-ended.

  • Account ID: The 9-digit LinkedIn account ID. 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.

  • Destination Account Name: 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.

  • Data Usage Reporting Requirement (type I Agree): Enter “I Agree” in this field to acknowledge that you will report the impressions and amount spent associated with this campaign to LiveRamp on a monthly basis.

  • Payment Model (type I Agree): Enter “I Agree” in this field to acknowledge that the cost of all data used in this campaign will be calculated as a % of campaign spend, using the 'Amount Spent' column provided in monthly usage reporting.

  • Payment Requirement (type I Agree): Enter “I Agree” in this field to acknowledge that you will pay for the use of this data in accordance with the LinkedIn Data Agreement.

  • Reporting Contact Email: Provide an accurate email or emails (comma separated) for the users who will be sending usage reports for the LinkedIn Account ID listed above.

Enable and Validate an OAuth Connection

Follow the instructions in “Validate OAuth Connection During Destination Account Activation” and "Perform OAuth Authorization for LinkedIn" below to enable and validate an OAuth connection for the LinkedIn destination account.

Performing OAuth Authorization for LinkedIn

LinkedIn requires that an authorization using OAuth be performed by a user with the appropriate permission level before any distributions can be made to LinkedIn.

Within Connect, OAuth authorizations are performed by utilizing an OAuth "connection" and validating it with your destination-specific information. A connection can be created by any user with the appropriate permission level at LinkedIn and can be reused for multiple LinkedIn destination accounts. See "Managing OAuth Connections" for information on creating, viewing, and managing OAuth connections.

This validation must be done when the destination account is activated, either by using an existing LinkedIn OAuth connection or by creating a new LinkedIn connection during the activation process. You can also create a LinkedIn OAuth connection outside of the destination account activation process. See the sections below for more information.

Whichever method you use, follow the instructions in "Perform OAuth Authorization for LinkedIn" below once the LinkedIn authorization dialog appears.

Note

OAuth credentials at LinkedIn expire 1 year after authorization. After 1 year (or if you notice your distributions are not going through), perform OAuth authorization at LinkedIn again.

Validate OAuth Connection During Destination Account Activation

While performing the steps in “Activate a New Destination Account” and before attempting to finalize the activation:

Note

The instructions below are valid for any OAuth destination platform. The screenshots show the process for LinkedIn as an example.

  1. Select one of your existing OAuth connections for that destination from the OAuth Connection drop-down list, or select + New OAuth Connection to create a new connection for that destination and follow the authorization process at the destination's website (LinkedIn example shown).

    C-Activate_New_Destination_Account-Select_OAuth_Connection.jpg

    Note

    If creating a new connection, follow the instructions to perform the authorization in the dialog that opens for that destination. See the appropriate section below for authorization information for specific platforms.

  2. Enter the appropriate information in the other OAuth-related fields (LinkedIn example shown - required fields vary by destination).

    C-Activate_New_Destination_Account-OAuth_fields.jpg

  3. Click VALIDATE OAUTH CONNECTION.

    C-Activate_New_Destination_Account-Validate_OAuth_Connection_button.jpg

    Note

    When activating a TikTok destination account, no VALIDATE OAUTH CONNECTION button appears (unlike other OAuth platform’s destination accounts). Skip to the next step.

    After the validation process is completed, a validated check mark appears:

    C-Managing_OAuth_Connections-validate_checkmark.jpg

    Note

    If a system error occurs, an error banner appears:

    C-Managing_OAuth_Connections-validate_system_error_banner.jpg

    Try to validate again. If you continue to get this error, contact your LiveRamp representative.

    Note

    If the seat or account ID is incorrect, an error message appears:

    C-Managing_OAuth_Connections-validate_error_message.jpg

    Check that the ID is correct and try to validate again.

  4. Complete any additional steps to activate the destination account.

Perform OAuth Authorization for LinkedIn

Caution

LiveRamp's OAuth integration with LinkedIn was updated on October 3, 2022. If you are the creator of one or more LinkedIn OAuth connections used by your LinkedIn destination accounts, you might need to take action as a result of this update. See this announcement for more information.

Account type required: The LinkedIn account needs to be a campaign manager account and must correspond to the account ID entered on the destination account.

OAuth expiration: OAuth credentials at LinkedIn expire 1 year after authorization. After 1 year (or if you notice your distributions are not going through), perform OAuth authorization at LinkedIn again.

Required destination account fields:

  • Accountid: The 9 digit LinkedIn account ID. This ID can be found in the URL when logging into Campaign Manager (after "/accounts/"). Contact your LinkedIn account representative if unsure of which value to use here.

Steps to perform OAuth for LinkedIn:

  • Once the LinkedIn login dialog appears, enter your credentials and then click Sign in.

    C-Authorize_DA_with_OAuth-LinkedIn-login-screen.jpg

You’ll be directed back to the destination account screen and should see the blue success banner at the top of the screen.

Troubleshooting Distributions

If you do not see your data segment(s) appear in LinkedIn:

  • Confirm you have authenticated with an Account Manager-level LinkedIn account

  • Confirm all parties are aligned on the data segment names and IDs

  • Confirm all parties are aligned on the type of segment (first-party vs. third-party) and that the segment has been pushed to the correct data endpoint

  • Confirm that the data partner pushed the segment

In this section:

OAuth (Open Authorization) is an open standard for token-based authentication and authorization.

The audience precision level determines whether a record that is onboarded is matched to records in the LiveRamp Identity Graph on an individual level or a household level (for offline-based data) or on a device level or individual level (for online-based data).

A type of LiveRamp destination integration that allows you to propagate user deletions downstream to supported destination platforms.

A field in a given file that has over 250 distinct values, and so cannot be separated out and managed individually in the UI.

The number of records and devices that have been matched at a distribution destination for your distributed fields and segments. Also referred to as "actual reach".

Data that a company has collected themselves, as opposed to second-party data or third-party data.