Integrations
HighLevel setup guide
Install once on your agency. Every sub-account gets its own DataCops client account and website record, and the stages your clients already work, form fills, bookings, showed appointments, won deals and paid invoices, are delivered to Meta, Google and TikTok with the ad click attached. Two steps per client, no code beyond one script tag.
What it does
Your clients close business inside their CRM, not on the website. The ad platforms never hear about it, so they keep bidding on form fills instead of real patients, clients and buyers. DataCops takes the stages that already happen in HighLevel and delivers them to the ad accounts as conversions, with the ad click and verified customer details attached.The app itself is free in the HighLevel marketplace. DataCops is billed to you, the agency, on one account across every client. See pricing.
What happens when you install
You install DataCops from the marketplace on your agency and choose the sub-accounts. From there everything below is automatic.
- You land in DataCops already signed in. The install creates your agency account and takes you to your Clients board. There is no separate signup and no login wall.
- Every sub-account becomes a client account. Created on the sub-account's own email, with the standard invite, so your client can log in and see only their own data.
- Every client gets a website record. If HighLevel already knows their website address, it is filled in for you. If not, you set it in DataCops later.
- A new sub-account added later appears on its own. Rename a sub-account or add its website in HighLevel and DataCops follows. A website address you set yourself is never overwritten.
Nothing is built inside HighLevel. Your client's website stays wherever it already lives, and DataCops only needs to know its address.
The two steps you do per client
Everything else is checked for you. These two need a human, once per client.
Paste the tracking script
Open the client's site in DataCops, press Finish setup, and copy the one script tag into the head of the website they actually run. DataCops then checks for it on its own and marks the site verified when it sees it, or when the first visit arrives. See installing the script.
Connect the ad accounts
In that site's CAPI Flow, connect Meta, Google Ads or TikTok. Until an ad account is connected, DataCops still records every CRM stage and tells you plainly that there is nowhere to send it yet.
What DataCops sends
Each stage below becomes a real conversion in your client's ad accounts, matched on the ad click where one exists and on securely hashed email and phone where it does not. Any stage can be switched off per client.| When this happens in HighLevel | DataCops sends | Detail |
|---|---|---|
| Form or survey submitted | Lead | A new contact and a returning contact both count. The submission carries the visitor ip, the browser and any ad click it arrived with. |
| Appointment booked | Schedule | A new or confirmed appointment. Booking through a HighLevel calendar is enough. |
| Appointment marked showed | Showed | The person actually turned up, which is the moment worth optimising for. |
| Opportunity moved to won | Purchase | Sent with the opportunity value and your currency. |
| Invoice paid or order placed | Purchase | Sent with the real amount. A refund reverses it. |
DataCops also writes the result back onto the HighLevel contact, so your client can see inside their own CRM which ad click a person came from and that the conversion was delivered.
The same submission is never counted twice. If the website script already sent that lead, HighLevel's copy of it is dropped, and a repeated webhook for the same booking, deal or invoice can only send once.
What sends nothing
A stage only becomes a conversion when it means something happened. These are recorded so you can see them, and deliberately never sent:
- A cancelled appointment, or one marked no show.
- An opportunity that is open, abandoned or lost.
- A contact created by hand or by a list import, with no submission behind it.
- A contact edit that is just a tag, a note or a field change.
- A contact with no email and no phone, because there is nothing an ad platform could match.
Where to watch it
Each client site has a HighLevel page in DataCops, next to CAPI Flow, with three tabs.
- Overview. Which sub-account the site is tied to, whether the connection is healthy, how many webhooks arrived in the last 30 days, how many were sent, skipped or failed, and the funnel from lead to booked, showed, won and paid.
- Event log. One readable row per event: what happened, what DataCops made of it, and the outcome at each platform, with the reason when something was held back.
- Settings. The five stage switches and the currency.
If webhooks stop arriving for a day, the page says so. Every row behind a conversion is also in the delivery log, so you can prove what was sent and when.
Health and wellness clients
Clinics are a large share of HighLevel agencies, and Meta restricts what you may send about them. DataCops has a health mode that keeps the conversion flowing while stripping the identity fields that must not be sent and using coded event names instead of plain ones. See Meta health and wellness restrictions.
Consent and data
- Where consent is required, nothing is collected or sent until the visitor accepts. See the consent manager.
- Customer details are normalised and hashed once before an ad platform sees them. Ad platforms never receive raw email or phone.
- Each client account sees only its own data. You, the agency, can open every client you manage.
- Deletion requests are handled for you. See DSAR automation.
What this does not do
- It does not build audiences in Meta, Google or TikTok. It sends conversions.
- It does not build or edit anything inside HighLevel, and it does not touch your client's own pixel setup.
- It does not replace the script on the website. Website sessions and CRM stages work together, and the script is what ties a stage back to the ad click.
Uninstall
Uninstall from HighLevel and DataCops stops sending for those sub-accounts straight away and drops its access. Your accounts, sites and history are kept, so reinstalling picks up where you left off without creating anything twice.