> ## Documentation Index
> Fetch the complete documentation index at: https://docs.invoca.com/llms.txt
> Use this file to discover all available pages before exploring further.

# LinkedIn Ads: Integration Guide

> Share call and call conversions with LinkedIn Ads to power your paid social marketing efforts.

## Step 1: Get your LinkedIn Ads Access Token and Conversion ID

**Access Token:** In LinkedIn Campaign Manager, go to your ad account, then **Data > Signals Manager**. Under Sources, click **Direct API**, then **Generate Access Token**.

**Conversion setup:** For each Invoca call or Signal you want to track, create a conversion under **Measurement > Conversion tracking**. Click **Create a conversion**, select **Conversions API**, give it a friendly name, select **Direct API** as the source, apply it to the relevant campaigns, and save.

**Conversion ID:** Click into each conversion you created and check the URL — the second numeric identifier after `/conversions/` is the Conversion ID. For example, in `https://www.linkedin.com/campaignmanager/accounts/1111111111/conversions/22222222`, the Conversion ID is `22222222`.

## Step 2: Set up the integration in Invoca

1. In the sidebar, click **Integrations**, then **Manage Integrations**.
2. Click the **LinkedIn Ads** tile. If it shows "Learn More" instead, contact your Invoca CSM or account manager to enable it.
3. Enter a friendly name for your LinkedIn Ads account, and enter the Access Token from Step 1.

### Create an Action

1. Enter a friendly name (include "Call" or the Signal name to distinguish Actions).
2. Optionally filter by Profile or Campaign.
3. Under **Triggered By**, choose **All Calls** or **Signal**.
4. Enter the LinkedIn Conversion ID matching your Triggered By selection.
5. Enter a **Default Value** as a fallback revenue amount — enter 0 if you don't want one.
6. Enter a 3-letter **Currency Code**, or leave blank to default to USD.
7. Click **Save**. Repeat for each transaction type, using **+ New Action**.

## Step 3: Configure your Invoca Tag(s) to capture the LinkedIn User ID

1. Click the gear icon, select **Invoca Tags**, and locate the Tag on your website.
2. Open the Revision History tab and create a new draft, or continue an existing one.
3. Find the **LinkedIn First Party Unique User ID (li\_fat\_id)** parameter in the Marketing Data section.
4. Set its Data Source Type to **Cookie**, enable it, and enter `li_fat_id` as the Data Source Name — this relies on the LinkedIn Insight Tag on your site capturing this value in a first-party cookie.
5. Test your changes, then click **Save & Go Live**. If you have multiple Invoca Tags, publish the update to each.

## Validate that events are reaching LinkedIn Ads

1. In Invoca, click **Integrations**, then **Manage Integrations**.
2. Click the **LinkedIn Ads** tile, then the name of the Action you created.
3. Review the Delivery Details chart, showing successes (green) and errors (red) by day for the last 30 days. Click Delivery History for individual requests and responses.
4. In LinkedIn Campaign Manager, check the Conversion Status under **Measurement > Conversion tracking** — it should say "Active."

## FAQs

**What is li\_fat\_id and how is it captured?** LinkedIn's first-party tracking user ID, stored in a first-party cookie by the LinkedIn Insight Tag. The Invoca Tag simply reads this value for use in the API call.

**What data is sent to LinkedIn Ads?** The LinkedIn Access Token, Conversion ID, currency, conversion value, conversion timestamp, li\_fat\_id, and the Signal Partner Unique ID (or the call Transaction ID if blank) as the unique event ID.

**How can I see the data Invoca sends to LinkedIn Ads?** Open an Action's Delivery History tab and expand a row to see the full JSON payload sent for that call or Signal.

**How does Invoca send data to LinkedIn Ads?** Invoca uses the LinkedIn Conversions API (CAPI), sending a server-to-server POST request to `https://api.linkedin.com/rest/conversionEvents`.

## Where to go next

* [Connect Apps & No-Code Integrations](/s/article/connect-apps-and-no-code-integrations)
* [Slack: Setup & Overview](/s/article/slack-setup-overview)