Meta Pixel + Conversions API Setup with GoHighLevel

Facebook Ads Tracking & Attribution Setup

(Duda + GoHighLevel + Meta Pixel + CAPI + Cookiebot)

Project Overview

We are running Facebook Ads and need a complete tracking and attribution setup that:

Sends accurate Lead conversion data back to Meta so campaigns can optimise properly

Allows us to clearly see inside GoHighLevel which leads came from Facebook and whether they converted

This is not an analytics-only project.

The objective is optimisation accuracy + clear attribution visibility inside GoHighLevel.

Current Setup

Website platform: Duda

Landing pages hosted on Duda

Forms: GoHighLevel forms embedded via HTML

CRM: GoHighLevel

Cookie consent: Cookiebot + Termly

Traffic source: Facebook Ads only

Traffic goes directly to landing pages

Core Objectives

We need:

Clean, deduplicated Facebook conversion tracking (Pixel + CAPI)

Confirmed Lead events firing only on real submissions

Clear attribution inside GoHighLevel showing:

Lead source = Facebook

Campaign / ad attribution where possible (UTMs or fbclid)

Visibility of whether they converted

We want to clearly see in GHL:

“User came from Facebook campaign X and completed form Y.”

Scope of Work
1. Meta Pixel Installation (Browser)

Install Meta Pixel correctly across the Duda website.

Pixel must track:

PageView

Lead event (confirmed submission only)

Relevant click events (if implemented)

2. Conversions API (Server-Side Tracking)

Set up Meta CAPI, ideally via GoHighLevel.

If both Pixel and CAPI are active:

Proper deduplication must be implemented

No double counting

Matching event IDs used

CAPI should act as fallback where browser tracking is blocked.

3. Confirmed Lead Conversion Logic (Critical)

The Lead event must fire only after a genuine submission.

Preferred setup:

Form submission → Redirect to dedicated thank you page → Thank you page triggers Lead event

No firing on partial submissions.

4. Facebook Attribution Inside GoHighLevel (Very Important)

We need:

UTM parameters captured and stored in GHL contact records

fbclid captured if possible

Source clearly visible as Facebook

Campaign level visibility where possible

This may require:

Hidden fields inside GHL forms

UTM persistence across pages

Proper mapping inside GoHighLevel

We want to clearly see in GHL:

• Traffic source
• Campaign
• Whether that user converted

5. Cookie Consent Compliance

We use Cookiebot + Termly.

Tracking must:

Categorise Pixel under Marketing cookies

Trigger correctly after consent

Remain compliant

Not break conversion tracking

If browser tracking is limited, CAPI must maintain conversion reliability.

Validation & Testing

We must verify using Meta Events Manager:

PageView fires correctly

Lead fires only on thank you page

No double counting

We must confirm whether Lead is received via:

Browser

Server

Or both

We must also confirm inside GoHighLevel:

A test Facebook lead shows correct source attribution

UTMs are visible

Conversion status is visible

Screenshots or walkthrough proof required.

Success Criteria

This project is complete when:

Facebook Ads Manager consistently receives clean Lead events

No double counting

Events fire only on genuine submissions

GoHighLevel clearly shows:

Lead came from Facebook

Campaign attribution (where possible)

Conversion status

The end goal is both:

Better Facebook optimisation
AND
Clear attribution visibility inside GoHighLevel

Deliverables

Meta Pixel correctly installed across Duda

Lead event firing correctly for all GHL forms

Conversions API configured and deduplicated

UTM and fbclid capture inside GoHighLevel

Attribution visibility inside GHL confirmed

Short written summary explaining:

What was implemented

How deduplication works

How attribution is captured in GHL

Any limitations caused by cookie consent

Any recommended improvements

Required Experience

Advanced Meta Pixel & CAPI implementation

Experience with GoHighLevel tracking & attribution

Experience with Duda

Understanding of UTM capture and persistence

Experience working with Cookiebot / consent-based environments

Please only apply if you have implemented deduplicated Pixel + CAPI setups with CRM attribution before.