> ## 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.

# Paid ads audiences

> Build consented, suppressed, and reviewed audiences for Google Ads, Meta, and LinkedIn from first-party data.

Use Deepline Ads Audiences to turn a consented first-party list into a reviewed
audience for Google Ads, Meta, or LinkedIn. This is for paid-ad matching, not
outbound messaging.

## Before you spend

Confirm all four points before enrichment or upload:

1. You may use the source list and any enriched identifiers for paid ads.
2. The requested platform and geography are in scope.
3. You know the target ad account name and ID.
4. You have a suppression list for current customers, employees, active
   opportunities, closed-lost accounts, and recent converters.

<Warning>
  Do not guess an ad account ID. Discover and confirm the account before a
  paid enrichment run or an upload.
</Warning>

## The audience lifecycle

<Steps>
  <Step title="Start from approved first-party data">
    Begin with a reviewed CSV, Customer DB query, or CRM segment. Keep the
    source, suppression, and output as separate datasets.
  </Step>

  <Step title="Build a baseline before enrichment">
    Create a first-party baseline from the identifiers you already have. This
    lets you measure whether enrichment improves the audience.
  </Step>

  <Step title="Enrich the remaining eligible rows">
    Run personal-identifier enrichment only for rows that still need a usable
    paid-ads identifier. Ask for the current Deepline-credit price and approve
    the spend before each paid layer.
  </Step>

  <Step title="Validate and upload one reviewed audience per platform">
    Remove invalid or duplicate identifiers, apply suppression, then create and
    upload the audience. Read status back before you call it complete.
  </Step>
</Steps>

## Run a first audience plan

Ask your Deepline agent for a plan before it creates anything:

```text theme={null}
/deepline-ads-audiences Build a cost-effective paid-ads audience from accounts.csv for Meta and Google. First show the target ad accounts, the suppression plan, source-row count, expected identifier layers, and Deepline-credit price. Do not enrich or upload until I approve.
```

<Check>
  A good plan names the source and suppression datasets, platform account names
  and IDs, the baseline, each paid layer, and the explicit approval point.
</Check>

## What to measure

Report these separately for each platform and each audience:

* Source rows and suppressed rows.
* Valid upload rows and invalid rows.
* Baseline and enriched audience names and IDs.
* Upload status and provider request IDs.
* Match rate when the platform exposes one; an accepted upload is not the same
  as a matched audience.
* Deepline spend, not provider-side spend.

## Platform guides

<CardGroup cols={3}>
  <Card title="Google Ads" icon="google" href="/docs/providers/google-ads-audiences/guide">
    Create and sync Customer Match audiences.
  </Card>

  <Card title="Meta" icon="meta" href="/docs/providers/meta-audiences/guide">
    Create and sync Custom Audiences.
  </Card>

  <Card title="LinkedIn" icon="linkedin" href="/docs/providers/linkedin-ads-audiences/guide">
    Create and sync Matched Audiences.
  </Card>
</CardGroup>

<Card title="Choose where audience data lives" icon="database" href="/docs/data-lifecycle">
  Start with a CSV, use Customer DB for durable processing, and write only approved outcomes to the CRM.
</Card>