# Funnel tracking and contact attribution

Put the Zernio tag on HighLevel funnels, send their conversions with the ad click behind them, and see each contact's ad source.

HighLevel webhooks say who became a lead or bought, never which ad click brought them. The Zernio tag on your funnels and websites records that click, and Zernio joins it to each conversion.

## Add the tag to your funnels

Open **Zernio Ads & Conversions** in the sub-account's menu. The **Funnel and website tracking** card creates the sub-account's tag on first open and shows the line to paste:

```html
<script async src="https://edge.zernio-edge.com/z.js?s=zs_..."></script>
```

HighLevel does not let apps write code into funnels, so paste the line once per funnel and website. Open the funnel, then **Settings**, then **Head tracking code**, and save.

The card lists every funnel and website in the sub-account and marks those whose tracking code holds the tag.

## Verify the install

Type the address of a live funnel page into the card and press **Verify install**. Zernio loads the page and looks for the tag.

When the tag is there, the page's domain joins the sub-account's tracking site, so its visits are tied to the people who fill its forms. Verify once per custom domain.

The card turns **Live** with the first visit.

## What reaches your ad platforms

Forms, calendar bookings and order forms on the funnel create HighLevel contacts, appointments and orders. Zernio relays them as `Lead`, `Schedule` and `Purchase` (see [What syncs](/platforms/gohighlevel/sync)).

Each one is joined to the same person's visit, found by the email or phone typed into the form. It carries that visit's click and browser ids: `gclid`, `gbraid`, `wbraid`, `fbc`, `fbp` and the rest.

With `reportToAds` on, the conversion reaches each ad platform's server-side API with those ids.

## Ad source on contacts

When a new contact comes from a tracked funnel, Zernio writes where they came from onto these contact custom fields, created in the sub-account the first time:

| Field | Value |
|-------|-------|
| Zernio Source | The ad network (Meta, Google, TikTok, LinkedIn...), else the UTM source or channel |
| Zernio Campaign | `utm_campaign`, else the campaign id in the URL |
| Zernio Ad | `utm_content`, else the ad id in the URL |
| Zernio Click ID | The click id, Meta's as `fbc` |
| Zernio Click ID Type | `gclid`, `gbraid`, `wbraid`, `fbc`, `ttclid`, `li_fat_id`... |
| Zernio UTM Source, Medium, Campaign, Content, Term | The landing page's UTM tags |
| Zernio Landing Page | The page the visit landed on, without its query |
| Zernio Source Date | When that visit started, ISO 8601 |

The source is the person's latest ad click in the 90 days before the lead, else their latest visit from a tagged link or another site. Empty fields are left as they were.

Turn the write off with `writeBackAttribution` in [Settings](/platforms/gohighlevel/settings).

## How it behaves

- Consent comes first. The tag follows the page's consent banner and asks EU visitors to opt in. A visitor who refuses ad storage leaves no click, so their contact gets no ad source.
- A new lead waits up to about 20 seconds for its visit, since the form's email reaches Zernio just after HighLevel creates the contact.
- Only contacts that came in by themselves (a form, a booking, an ad lead form) count as a `Lead`. Contacts your team adds or imports do not.
- The tag records visits and clicks, never conversions: those come from HighLevel's own records, so each counts once.

## Related

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