Track Facebook Ads in Accelo: From Click to Customer
You can connect Facebook Ads activity to leads, opportunities, customers and revenue inside Accelo by capturing campaign tags at the first visit and carrying them through to form submission. The key is not just adding UTM parameters to ads, but preserving them until a lead record is created.
Why attribution inside Accelo matters
Without campaign-level attribution, a profitable Facebook campaign can look invisible and an unprofitable one can keep consuming budget. Once leads carry their originating channel and campaign into Accelo, you can compare Facebook against organic search, paid search, referral and direct traffic in the same view, then follow those leads through opportunities and closed deals. That makes budget decisions concrete: scale what produces customers, pause what does not, and spot where optimisation effort is most likely to pay back.
How the capture works
A small code snippet on the website reads technical signals about how each visitor arrived, classifies the visit into a standard channel such as Paid Social or Organic Search, and stores that classification in a browser cookie. When the visitor completes a form, the stored values are placed into hidden fields on that form. Those fields travel with the name, email and other details into connected backend systems, including Accelo. Because the snippet also records the landing page and its group, you can later see which pages and content sections brought in valuable leads, not only which ads did.
Four-step setup checklist
Install the snippet on the website, either directly through site settings or via a tag manager. Add hidden fields to every lead-capture form you want to measure. Tag Facebook Ads with UTM parameters so the snippet has something to classify. Confirm that a test submission from a tagged ad creates a lead in Accelo with the channel fields populated. Only then build reports; reporting on empty fields will not reveal campaign performance.
Field map: what each hidden field should hold
Channel gives the broad category, such as Paid Social. Channel Drilldown 1 identifies the platform, such as Facebook. Channel Drilldown 2 holds the campaign name. Channel Drilldown 3 holds the ad set. Channel Drilldown 4 holds the specific ad. Together they create a drill path from channel to individual creative, which is exactly the structure needed for campaign and ad-set reporting in Accelo.
UTM convention for Facebook Ads
UTM parameters are extra text appended to a destination URL. For Facebook Ads, a consistent convention is: utm_medium set to paid social, utm_source set to Facebook, utm_campaign set to the campaign name, utm_term set to the ad set name, and utm_content set to the specific ad. For example, a landing page URL can be extended with utm_medium=paidsocial, utm_source=facebook and utm_campaign=brand-campaign. Keep naming stable across campaigns; changing spellings mid-flight fragments your reports even when the underlying ads are unchanged.
Worked example: from ad click to demo request
Imagine a marketer promoting a product through Facebook. A prospect clicks a tagged ad, browses several pages, and then requests a demo. Because the UTM data was stored in a cookie at arrival, the demo form still receives the original campaign context. The submitted lead carries Paid Social as the channel, Facebook as the platform, the campaign name, the ad set name and the ad name in the drilldown fields, alongside the landing page and its group. In Accelo, that lead can then be followed as it becomes an opportunity and, eventually, a customer.
What makes this approach more reliable
Cookie persistence prevents loss when a visitor browses before converting. Channel standardisation reduces errors from inconsistent UTM spellings, grouping variants such as facebook and facebook.com under Paid Social. Capturing all channels, not only Facebook, gives a fair comparison against organic social, organic search, direct and referral. Landing page capture adds a content dimension, showing whether blog or feature pages convert better than other entry points.
Three reports to build in Accelo
Once channel data is in Accelo, three reports answer most budget questions. Leads by channel shows how Facebook compares with other sources and where to shift effort. Customers by campaign shows which campaigns produce new customers each month, guiding where to test and optimise. Revenue by campaign links customers back to monthly revenue, so you can compare revenue generated against ad spend and judge return on investment campaign by campaign. The same fields can also be exported to a business intelligence tool such as Looker or Tableau for deeper analysis.
| UTM parameter | Recommended value for Facebook Ads |
|---|---|
| utm_medium | Paid social |
| utm_source | |
| utm_campaign | Campaign name |
| utm_term | Ad set name |
| utm_content | Specific ad |
Convention only; consistency across campaigns is essential for clean reporting.
Frequently asked questions
What is the minimum setup needed to get Facebook Ads data into Accelo?
Add the attribution snippet to your site, add Channel and Channel Drilldown 1-4 as hidden fields on lead forms, and tag Facebook Ads with consistent UTM parameters. When a visitor later submits a form, the stored channel data is written into those hidden fields and sent with the lead into Accelo.
How should UTM parameters be structured for Facebook Ads?
Use utm_medium for paid social, utm_source for Facebook, utm_campaign for the campaign name, utm_term for the ad set, and utm_content for the specific ad. Consistency matters more than the exact labels, because later reporting groups records by those values.
Why store UTM data in a cookie instead of reading it only on the landing page?
Storing UTM data in a browser cookie means it survives browsing between pages, so the form submitted later still carries the original campaign information instead of losing it when the landing page changes.
What happens if UTM source values are inconsistent?
Standardised channel assignment can group inconsistent source spellings, such as facebook and facebook.com, under the same Paid Social channel, reducing split reporting caused by naming variations.