> For the complete documentation index, see [llms.txt](https://docs.adpage.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.adpage.io/data-and-insights/marketing-integrations/linkedin-ads.md).

# LinkedIn Ads

Connect LinkedIn Ads to pull campaign cost and conversions into your reports and the Marketing Mix Model.

Connect LinkedIn Campaign Manager so AdPage can read your campaign cost and conversions. The connection is **read-only**: AdPage asks for `r_ads` and `r_ads_reporting`, both read-only, plus your basic profile to identify the connection.

### Before you start

You need a LinkedIn account with at least **Viewer** access to the ad accounts you want, granted in Campaign Manager. Viewer is enough.

LinkedIn ties access to a personal profile more tightly than the other platforms — there is no equivalent of a shared service account. Use someone who will still be at the company in a year, and expect to reconnect if they leave.

### Connect LinkedIn Ads

{% stepper %}
{% step %}

#### Open the tile

Go to **Integrations**, select the container, and open the **LinkedIn Ads** tile.
{% endstep %}

{% step %}

#### Approve access at LinkedIn

Select connect. LinkedIn shows what AdPage is requesting — read access to your advertising accounts and reporting. Approve.
{% endstep %}

{% step %}

#### Choose your ad accounts

AdPage lists the ad accounts the approved profile can reach. Tick the ones for this container and save.
{% endstep %}
{% endstepper %}

### What you get

LinkedIn cost and conversions in **Channel KPIs** and **Campaigns & Attribution**, and spend in the **Marketing Mix Model**.

LinkedIn is usually a B2B channel with a long sales cycle, which makes the model more useful than the platform report: a lead created this week may become revenue two quarters out, and last-click will never connect the two.

### Reading the numbers

**Volumes are small and noisy.** LinkedIn costs far more per click than the other platforms, so a week can turn on a handful of conversions. Read longer periods than you would for Meta or Google.

**Conversions include view-through by default.** LinkedIn's default window counts post-view conversions. AdPage measures last-click.

**Lead-gen form submissions are not orders.** If you use LinkedIn Lead Gen Forms, the platform's conversion count is form fills. Revenue attached to those leads lives in your CRM, which is outside this integration.

### Troubleshooting

**No ad accounts appear.** The profile has no role on any ad account. Check in Campaign Manager under account **Settings → User permissions**.

**"Insufficient permissions" during approval.** The LinkedIn profile cannot grant advertising access — typically a personal profile with no Campaign Manager role at all.

**The tile says the connection expired.** LinkedIn access is comparatively short-lived and ends when the member changes their password or leaves the company. Reconnect from the tile.

**Conversions are zero but cost is right.** No LinkedIn Insight Tag conversions are recorded, or the campaign objective does not produce them. A LinkedIn-side configuration question.

Still stuck? Contact <support@adpage.io> with the container and the ad account ID.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.adpage.io/data-and-insights/marketing-integrations/linkedin-ads.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.