> For the complete documentation index, see [llms.txt](https://docs.mediarithmics.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mediarithmics.io/connectors/destinations/linkedin.md).

# LinkedIn

Send offline data from mediarithmics to LinkedIn Matched Audiences.

The LinkedIn connector sends offline data from mediarithmics to [LinkedIn Matched Audiences](https://www.linkedin.com/help/lms/answer/a795242/matched-audiences-definitions?lang=en-US).

<table data-search="false"><thead><tr><th width="220">Connection</th><th></th></tr></thead><tbody><tr><td><strong>Type</strong></td><td>Server-side</td></tr><tr><td><strong>Category</strong></td><td><a href="/connectors/partner-types/social-and-retail-media.md">Social &#x26; retail media</a></td></tr><tr><td><strong>Identifiers sent</strong></td><td>Email identifiers, Mobile IDs (AAID only), Profile data</td></tr><tr><td><strong>Authentication</strong></td><td>Self-service sign-in, per mediarithmics user</td></tr></tbody></table>

## Description

### What is LinkedIn Matched Audiences?

Matched Audiences is LinkedIn's audience-matching product: you upload your own data, LinkedIn matches it against its members, and the resulting audience becomes targetable in your campaigns.

### What you can do with this connector

* Create a LinkedIn Matched Audience from a mediarithmics segment.
* Enrich a LinkedIn audience that already exists rather than creating a new one.
* Improve match rate by sending profile attributes alongside the email.

### Which identifiers are sent

* **Email identifiers**
* **Mobile IDs** - AAID only
* **Profile data** - first name (plain text), last name (plain text), title, company, country

All identifiers must be **SHA-256 encrypted**. Identifiers not already stored encrypted are encrypted before being sent.

{% hint style="info" %}
The more identifiers you send, the higher the chance of matching profiles.
{% endhint %}

## Connector setup

### Prerequisites

* A LinkedIn ad account you have access to.
* To send **profile data**, an internal configuration set up by your account manager.

### Authentication

Sign-in is **self-service**, from the platform, and grants mediarithmics access to your LinkedIn data.

{% hint style="warning" %}
**The connection belongs to your mediarithmics user.** Only you can create and manage LinkedIn feeds through it. Another mediarithmics user wanting to create a LinkedIn feed must have access to the relevant LinkedIn ad account and configure their own connector.
{% endhint %}

### Setup steps

{% stepper %}
{% step %}
**Go to any segment and create a feed.**
{% endstep %}

{% step %}
**Select the LinkedIn connector.**
{% endstep %}

{% step %}
**Click Sign in and follow the steps.**

You are prompted to allow mediarithmics to access your data.
{% endstep %}

{% step %}
**You are redirected to the mediarithmics platform, connected. Close the tab.**
{% endstep %}

{% step %}
**To send profile data, contact your account manager.**

They set up the internal configuration.
{% endstep %}

{% step %}
**Fill in the feed configuration.**

<table data-search="false"><thead><tr><th width="300">Field</th><th></th></tr></thead><tbody><tr><td><strong>Name</strong></td><td>Identifies the feed inside mediarithmics.</td></tr><tr><td><strong>LinkedIn Sponsored Account</strong></td><td>The account to sync the audience with. Only accounts you have access to are listed.</td></tr><tr><td><strong>Data</strong></td><td>Which data to send to LinkedIn.</td></tr><tr><td><strong>LinkedIn Segment Name</strong> <em>(optional)</em></td><td>A specific name for the LinkedIn audience. Defaults to the mediarithmics segment name.</td></tr><tr><td><strong>LinkedIn Audience</strong> <em>(optional)</em></td><td>An existing LinkedIn audience to enrich. Only audiences from the selected Sponsored Account are listed.</td></tr></tbody></table>
{% endstep %}
{% endstepper %}

Creating and activating the feed on a segment is covered in the **Audience & Activation** section, under *Activate your audiences › Send your first-party data to a destination*.

## Good to know

Two thresholds apply, and both are LinkedIn's:

* Your segment must hold **at least 300 users** for a matched audience to be created.
* The LinkedIn audience must have **at least 300 matches** with LinkedIn members before it can be used in a campaign.

{% hint style="info" %}
For a user to match, they must have **at least one valid ID**, **or** a valid **first name and last name**.
{% endhint %}

## FAQ

#### How do I check the LinkedIn audience details and match rate?

{% stepper %}
{% step %}
On the segment, go to the feeds section.
{% endstep %}

{% step %}
Open **Stats** in the options of the LinkedIn feed.
{% endstep %}

{% step %}
Go to the **Troubleshooting** tab and scroll to *Audience description on the destination platform*.

Match rate, status and number of users are there.
{% endstep %}
{% endstepper %}

#### How do I get the best match rate?

Send more identifiers - every additional one raises the chance of a match. LinkedIn's own [Matched Audiences best practices](https://www.linkedin.com/help/lms/answer/a424450?lang=en-US) are worth reading.

#### A colleague cannot see my LinkedIn feed. Why?

The connection is tied to the mediarithmics user who signed in. Your colleague needs access to the LinkedIn ad account and must configure their own connector.

## Partner documentation

LinkedIn Marketing Solutions documents its own platform at <https://www.linkedin.com/help/lms>. Use it for anything that happens on the partner side of this connector: account setup, the fields the partner expects, and its own limits.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.mediarithmics.io/connectors/destinations/linkedin.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.