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

# LinkedIn Ads Audiences

> LinkedIn Matched Audiences connection, action IDs, payload requirements, and replacement-upload safeguards.

Use LinkedIn Ads Audiences to create and replace Matched Audience contact or
company lists. Plan consent, suppression, enrichment, and approval in
[Paid ads audiences](https://deepline.com/docs/ads-audiences.md); this page owns the LinkedIn-specific
contract.

## Connect and select an account

In the Deepline dashboard, open **Integrations → LinkedIn Ads Audiences**,
complete OAuth, refresh accessible accounts, enable the accounts Deepline may
use, and set a default when appropriate. With more than one enabled account,
pass `account_id` explicitly. Deepline accepts a bare sponsored-account ID or
`urn:li:sponsoredAccount:{id}` and normalizes it.

## Live actions and schema

Execute these IDs through the shared
[`POST /api/v2/integrations/{toolId}/execute` contract](https://deepline.com/docs/api-reference#execute-a-tool).
The table lists `payload` fields. Substitute an Action ID from it into
`GET /api/v2/integrations/{toolId}/get` to inspect the live schema.

| Action ID | Required payload | Important optional fields |
| - | - | - |
| `linkedin_ads_audiences_create_audience` | `name` | `account_id`, `audience_kind` (`contacts` or `companies`) |
| `linkedin_ads_audiences_list_audiences` | — | `account_id` |
| `linkedin_ads_audiences_get_audience_status` | `audience_id` | `account_id` |
| `linkedin_ads_audiences_sync_audience_members` | `audience_id`, `rows` | `account_id`, `audience_kind` |
| `linkedin_ads_audiences_delete_audience` | `audience_id` | `account_id` |

Each `rows` entry can carry a supported raw or SHA-256 identifier. Deepline
builds the contact or company CSV and reports invalid rows separately.

## LinkedIn-specific safeguards

* `linkedin_ads_audiences_sync_audience_members` is replacement-only:
  `mode` is always `replace`. Treat each sync as a full refresh, not an append.
* Choose `audience_kind: "contacts"` for person matching and `"companies"` for
  account matching, and keep that choice consistent with the audience you
  created.
* Read `destination_status` after a sync. An accepted upload is not a matched
  audience.
* Deleting an audience is irreversible. Read the audience and account IDs back
  before calling the delete action.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.