# Ad leads to contacts

How leads from Meta, TikTok, LinkedIn and Google lead forms become HighLevel contacts, tagged with the network, campaign and form.

Every lead from the lead forms on the profile's connected ad accounts becomes a contact in the connected HighLevel sub-account, seconds after the network delivers it. Your workflows, pipelines and follow-ups start from there.

## Turn it on or off

Ad lead sync is on by default for every connected sub-account. Turn it off with `syncAdLeads`:

```bash
curl -X PATCH "https://zernio.com/api/v1/accounts/ACCOUNT_ID/gohighlevel-settings" \
  -H "Authorization: Bearer $ZERNIO_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "syncAdLeads": false }'
```

## What each contact gets

| Lead answer | HighLevel contact field |
|-------------|---------------------------|
| Email (or work email) | Email |
| Phone number (or work phone) | Phone |
| First name, last name, full name | First name, last name, name |
| Company name | Company name |
| Street address, city, state or province, zip or post code | Address, city, state, postal code |
| Country (two-letter code) | Country |
| Any other answer | A text custom field named `Lead: <question>`, created the first time the question is seen |

Each contact is tagged:

| Tag | Example |
|-----|---------|
| `zernio ad lead` | On every contact from an ad lead |
| `<network> lead` | `meta lead`, `tiktok lead`, `linkedin lead`, `google lead` |
| `campaign: <name>` | `campaign: spring promo` (the campaign id until the campaign has synced) |
| `form: <name>` | `form: quote form` |

The contact's source reads `Zernio · Meta lead form` (or the lead's network).

## How it behaves

- A lead is matched to an existing contact by email, then by phone, using the sub-account's duplicate rules. A match is updated: only the fields it lacks are filled (its name is never changed), its own tags stay and Zernio's are added.
- A lead with neither email nor phone is not sent, since there is nothing to match on.
- A lead is sent once per sub-account. One that fails because HighLevel is down is retried 15 minutes later, then up to 8 hours apart, for about a day; a rate-limited sub-account waits out its limit first. A lead HighLevel refuses outright (for example an invalid phone) is not retried.
- Calls to HighLevel share the sub-account's rate limit with the rest of the integration and back off when HighLevel answers 429.
- A contact created from an ad lead does not count a second `Lead` conversion: its `Lead` already came from the ad network.
- Leads from every network Zernio reads lead forms from are sent: Meta, TikTok, LinkedIn and Google. See [Meta lead forms](/platforms/meta-ads/lead-forms) for how lead forms reach Zernio.
- Only leads that arrive while the sync is on are sent: connecting a sub-account or turning `syncAdLeads` on does not import earlier leads, and leads submitted more than a week before Zernio stores them (a backfill) are not sent.

## Related

- [Settings](/platforms/gohighlevel/settings)
- [What syncs](/platforms/gohighlevel/sync)