Skip to main content
The LinkedIn Connector delivers audience data to LinkedIn Campaign Manager as Matched Audiences, either lists of people or lists of companies, for targeting in LinkedIn ad campaigns.

Overview

The connector delivers two kinds of LinkedIn audience. A people audience matches on email addresses and Android advertising IDs. A company audience matches on company names, domains, and LinkedIn company pages, for account-based targeting. For either kind you can create a new audience in one of your ad accounts or deliver into one that already exists. An opt-out removes people or companies from every audience of its kind that your connections deliver to.

Guides

Setting Up the LinkedIn Connector

Install the connector, connect a profile, and reconnect it before the grant expires

Connecting an Opt-Out Dataset

Remove opted-out people and companies from LinkedIn audiences

Requirements

Account access

  • A LinkedIn Campaign Manager ad account that isn’t a test account and hasn’t been closed
  • A LinkedIn account with a role other than Viewer on that ad account. Connecting a profile asks LinkedIn for the r_ads and rw_dmp_segments permissions

Supported identifiers for people audiences

Your data must include at least one of these identifier types, mapped to the corresponding Rosetta Stone attribute: The connector removes whitespace from a raw email and lowercases it before hashing it. Dots and + tags stay as they are.
Hashed emails must use SHA256. A hashed_email value of another type, such as SHA-1 or MD5, is skipped during delivery. See Hashing PII for Upload for formatting requirements.
The connector doesn’t match people on name, phone number, or Apple IDFA. A row that carries none of the identifiers above delivers nothing.

Supported identifiers for company audiences

Your data must include at least one of these identifier types. Each one can identify a company by itself: A mapped postal_address narrows the match with its city, region, postal code, and country. An address can’t identify a company by itself, so a row with only an address delivers nothing. Company identifiers reach LinkedIn as plain text, not hashed. The connector trims each value, and sends only the first value of each identifier type in a row and the row’s first address.

Managing profiles

Each profile carries its own LinkedIn grant. The Profiles tab lists every profile with its Status, and a profile’s page shows the rest:
  • Status: Connected, Expiring, Expired, or Not Connected. Only Connected and Expiring profiles deliver audiences, list them on the Audiences tab, and make opt-outs available. Setting Up the LinkedIn Connector explains each status and how to reconnect.
  • Profile status: whether the profile is Enabled or Disabled.
  • LinkedIn grant expires: the date the grant expires. It reads LinkedIn grant expired once the date has passed.
  • Ad accounts: the ad accounts the grant reaches, with Refresh to read them from LinkedIn again. Shown while the profile is Connected or Expiring.
  • Delete profile: removes the profile.

Delivering audiences

When you connect a dataset to the LinkedIn Connector, you pick a Profile and, when the dataset fits more than one, a Connection type. A dataset mapped to people identifiers is offered the people types, and one mapped to company identifiers is offered the company types. To connect a dataset of opted-out people or companies instead, see Opt-outs.

New People Audience

Existing People Audience

New Company Audience

Existing Company Audience

The Audience list offers audiences of the matching kind that were built through LinkedIn’s API, such as the ones Narrative creates. An audience uploaded to Campaign Manager as a CSV file isn’t offered, because LinkedIn accepts only CSV uploads into it.

Write modes

The dataset write mode decides what happens to an audience’s existing members when a new delivery arrives. Company audiences and existing people audiences always append. Use Overwrite with an overwrite dataset, where each delivery is the complete, current audience. Each delivery carries one new dataset snapshot. On an overwrite dataset, every snapshot is the full dataset, so an Overwrite connection keeps the audience matching the dataset. On an append dataset, every snapshot holds only the newly added rows, so an Overwrite connection shrinks the audience to the latest batch at each delivery.
Creating a new audience fails when the ad account already holds LinkedIn’s maximum of 1,000 audiences built through its API. The connection’s error says so.

Audience status in LinkedIn

A successful delivery in Narrative means the identifiers reached LinkedIn. LinkedIn then matches them to its members or companies, and the Audiences tab on the connector page shows how far each audience has got. Pick a Profile, an Ad account, and an Audience type (People or Companies). Only Connected and Expiring profiles are offered. The tab lists the audiences in that ad account that were built through LinkedIn’s API, so an audience uploaded as a CSV file doesn’t appear. LinkedIn can report other statuses, which the tab shows in LinkedIn’s own words. Click Refresh statuses to read every status from LinkedIn again.

API connection settings

A connection’s quick_settings pick the interface and set how the connection delivers. The fields depend on the interface. The interface’s JSON Schema is authoritative; retrieve it with List app interfaces.

New people audience (user_audience_new)

The connector creates the audience in LinkedIn when you create the connection.

Existing people audience (user_audience_existing)

New company audience (company_audience_new)

The connector creates the audience in LinkedIn when you create the connection. Company audiences take no write mode or member TTL, because every delivery appends.

Existing company audience (company_audience_existing)

People and company opt-outs (user_opt_out, company_opt_out)

A connection created over the API without dataset_write_mode uses append. The connection form in Narrative pre-fills the source dataset’s write mode instead.

Existing and new rows

A connection delivers every snapshot written to the dataset after the connection is created. The historical_data_enabled quick setting decides whether the connection also delivers data that was already in the dataset when you created it:
  • With historical_data_enabled set to true, the connection first delivers data already in the dataset, then keeps delivering new snapshots as they land.
  • With historical_data_enabled set to false, the connection delivers only snapshots written after it was created.
How far back the first delivery reaches depends on the connector, and each connector’s guide states it. For LinkedIn, historical_data_enabled delivers the dataset’s data from the 30 days before the connection was created. After that, each new snapshot is delivered as it lands.

Audience membership duration

Membership duration is how long a delivered identifier remains active in the destination audience before the destination platform expires it. It is distinct from the dataset’s retention policy (which governs data stored in Narrative) and the interface’s refresh window (which governs how stale the source dataset may get). Narrative enforces the TTL itself. A daily job removes the members the dataset has not delivered within the TTL, so a member can stay up to one day longer than the TTL. Company audiences, existing audiences, and Overwrite connections have no TTL. See Write modes.

Opt-outs

The Opt Out Configuration tab on the connector page connects a dataset of opted-out people or companies to LinkedIn. Set Opt out to People or Companies before you connect the dataset:
  • People: removes the dataset’s people from every LinkedIn people audience your company’s connections deliver to, across all of your LinkedIn profiles. The dataset needs at least one of the people identifiers.
  • Companies: removes the dataset’s companies from every LinkedIn company audience your company’s connections deliver to. The dataset needs at least one of the company identifiers.
The opt-out connection itself names no ad account and no audience. To connect an opt-out dataset, follow Connecting an Opt-Out Dataset.
You need at least one connected profile before Connect opt out dataset becomes available. Each removal is sent with the grant of the profile that owns the audience, so a removal from the audiences of a profile whose grant has expired fails. Keep every profile that delivers audiences connected.

Data Activation Overview

Understand how connectors deliver data

Hashing PII

Prepare identifiers for LinkedIn

Structuring Audiences

Organize datasets for delivery

Schema Incompatibility Errors

Resolve errors when a dataset schema doesn’t match a connector

LinkedIn Connector API

Profiles, ad accounts, audiences, and connection settings forms on the connector host