Track Facebook Ads in ActiveCampaign: UTMs, Hidden Fields and Reports
Knowing which Facebook campaigns produce leads, opportunities, customers and revenue changes how you allocate budget. Without that link, a profitable campaign may be underfunded while an unprofitable one keeps consuming spend. The workflow below connects ad clicks to CRM records using UTM parameters, a website snippet, hidden form fields and ActiveCampaign reporting.
How the attribution flow works
A small website snippet examines technical visit data to determine how each visitor arrived, then classifies that origin into marketing channels such as Organic Search, Paid Social and Paid Search. The classification is saved in a browser cookie. When a visitor submits a form, the snippet writes the attribution values into hidden fields, so they are stored in the CRM alongside the contact's name, email and phone. From there you can compare Facebook Ads against Google Ads, SEO and other channels across leads, opportunities, closed deals, close rates, revenue and return on ad spend.
Step 1: Install the snippet and add hidden fields
Install the snippet on your website, either directly through your site settings or via a tool such as Google Tag Manager. Then add five hidden fields to every lead-capture form: Channel, Channel Drilldown 1, Channel Drilldown 2, Channel Drilldown 3 and Channel Drilldown 4. In most form builders you drag in a Hidden field type or convert an existing field to hidden in its settings. Checklist: snippet active on all pages, five hidden fields present on each form, and a test submission confirms values arrive in ActiveCampaign.
Step 2: Tag Facebook Ads with UTM parameters
UTM parameters are extra text appended to the destination URL. A consistent convention makes reporting reliable: utm_medium for the channel type, utm_source for the platform, utm_campaign for the campaign name, utm_term for the ad set and utm_content for the specific ad. For example, a destination page with utm_medium=paidsocial, utm_source=facebook and utm_campaign=brand-campaign lets the CRM distinguish that campaign from every other source. Free UTM builder tools can help assemble these URLs.
Step 3: Capture and store the data until form submission
When a visitor lands from a Facebook ad, the snippet captures the UTM parameters and keeps them in a cookie, so they are not lost while the visitor browses other pages. On form submission those values are written into the hidden fields and saved with the lead. Worked example: a marketer promoting a CRM runs a brand campaign; a visitor clicks, browses, then requests a demo. The hidden fields receive Channel = Paid Social, Channel Drilldown 1 = Facebook, Channel Drilldown 2 = Brand Campaign, Channel Drilldown 3 = North America Ad Set and Channel Drilldown 4 = Green Ad. The landing page URL and landing page group are captured as well, which adds content-performance context to the same record.
Step 4: Report in ActiveCampaign
The channel data arrives in ActiveCampaign together with the contact's name, phone and email. Build reports with ActiveCampaign's native tools, or send the data to Power BI, Google Data Studio or Tableau for deeper analysis. Three useful views: leads by channel per month, to compare Facebook against other channels before shifting budget; customers by campaign per month, to see which campaigns create the most new customers; and revenue by campaign per month, to judge ROI by comparing revenue with ad spend plus agency and creative costs. In the illustrative example, $65,000 of new revenue attributed to Facebook Ads in August would represent positive ROI if total Facebook-related costs were lower. Breaking revenue down by campaign also shows where to invest more and where to stop.
Why this approach covers more than Facebook
Beyond Facebook, the same setup records Direct, Referral, Organic Social and Organic Search arrivals, giving a complete picture of lead sources. Cookie storage improves accuracy when visitors convert on a different page than they landed on. The data is also cleaned: inconsistent values such as utm_source=facebook and utm_source=facebook.com are both assigned to the correct channel, Paid Social in this case. Landing page URL and landing page group capture lets you evaluate content such as blog posts alongside paid campaigns.
| UTM parameter | What to put in it | Example value |
|---|---|---|
| UTM Medium | Channel type | Paid social |
| UTM Source | Platform | |
| UTM Campaign | Campaign name | Brand Campaign |
| UTM Term | Ad set name | North America Ad Set |
| UTM Content | Specific ad | Green Ad |
Conventions are recommendations from the captured workflow; consistency matters more than the exact labels.
| Hidden field | Example value from a Facebook click |
|---|---|
| Channel | Paid Social |
| Channel Drilldown 1 | |
| Channel Drilldown 2 | Brand Campaign |
| Channel Drilldown 3 | North America Ad Set |
| Channel Drilldown 4 | Green Ad |
Values depend on the UTM parameters used on the ad.
Frequently asked questions
What is needed to pass Facebook Ads data into ActiveCampaign?
Add UTM parameters to the ad destination URL, install the tracking snippet on your site, add the five hidden fields to lead forms, and let the snippet store the parameters in a browser cookie until form submission. The values then travel into ActiveCampaign with the contact details.
Does this only work for Facebook traffic?
No. The same setup also records visits from Direct, Referral, Organic Social and Organic Search, so reporting can cover every lead source rather than Facebook alone.
Why store UTM data in a cookie?
Storing the parameters in a cookie means they survive browsing across pages, so the form a visitor eventually submits still carries the original campaign data.
Where can I report on the data once it reaches ActiveCampaign?
Use the captured channel fields in ActiveCampaign's native reports, or export the data to a BI tool such as Power BI, Google Data Studio or Tableau for more advanced reporting.