Skip to content

Track Facebook Ads in Insightly: a four-step attribution setup

You can connect Facebook Ads activity to leads, opportunities, customers and revenue in Insightly by capturing UTM parameters on arrival, storing them for the visit, and writing the resulting channel data into lead forms. This guide explains the setup, the fields involved and the reports it enables.

How the attribution flow works

The workflow has three parts. First, arrival data is examined to identify how a visitor reached the site. Second, that origin is grouped into a standard channel such as Paid Social, Organic Search or Paid Search and stored in a browser cookie. Third, when a form is submitted, the stored values are placed into hidden fields and travel with the contact details into connected systems such as Insightly. Because the values are stored, a visitor does not need to convert on the first page viewed.

Step 1: Install the code and add hidden fields

Install the supplied website snippet through site settings or a tag manager. Then add five hidden fields to each lead-capture form: Channel, Channel Drilldown 1, Channel Drilldown 2, Channel Drilldown 3 and Channel Drilldown 4. In most form builders this means inserting a hidden field type or changing a field setting so it is not visible to visitors. Check every form that creates a lead, not only the contact form, because a missing field means that submission will not carry attribution data.

Step 2: Tag Facebook Ads with UTM parameters

Append UTM parameters to the destination URL for each Facebook campaign. A consistent convention is: utm_medium = paid social, utm_source = Facebook, utm_campaign = campaign name, utm_term = ad set name, and utm_content = specific ad. For example, a destination URL can carry utm_medium=paidsocial, utm_source=facebook and utm_campaign=brand-campaign. Keep spelling and casing consistent across campaigns so reporting groups matching activity together.

Step 3: Let stored data populate the form

On arrival, the parameters are read and stored in a cookie. On form submission, they are converted into channel values and written into the hidden fields alongside name, email and phone. In one worked example, the fields resolve to Channel = Paid Social, Drilldown 1 = Facebook, Drilldown 2 = Brand Campaign, Drilldown 3 = North America Ad Group and Drilldown 4 = Green Ad. The landing page URL and its group, such as /features, are captured as well, which helps show which content areas preceded conversion.

Step 4: Report inside Insightly

Once submitted, the contact details and attribution fields arrive together in Insightly. Reporting can then be done with Insightly's native tools, or the data can be taken into a business intelligence tool for more detailed analysis. Before trusting a report, run a test click and a test submission and confirm that all five drilldown fields arrive populated and correctly grouped.

Why this approach is useful

Four practical advantages stand out. The same method captures other channels, including Direct, Referral, Organic Social and Organic Search, so Facebook can be compared fairly. Cookie storage preserves parameters across pages. Inconsistent UTM spellings, such as facebook versus facebook.com as a source, are normalised to the same channel. Landing page and landing page group data add content context beyond the ad itself.

Checklist and common failure points

Use a pre-launch checklist: snippet installed on all relevant pages, hidden fields present on every lead form, UTM convention documented, test submission verified in Insightly, and report filters built for channel, campaign and revenue. A common failure is tagging ads but omitting hidden fields, which breaks the chain at submission. Another is inconsistent UTM naming, which fragments campaigns in reports even though the underlying clicks occurred.

Facebook Ads UTM convention
UTM parameterSuggested valueWhat it identifies
utm_mediumPaid socialBroad channel type
utm_sourceFacebookPlatform
utm_campaignCampaign nameCampaign
utm_termAd set nameAd set
utm_contentSpecific adIndividual ad

Suggested convention from captured guidance; exact naming is configurable but should be consistent.

Reports to build in Insightly
ReportQuestion it answersDecision it supports
Leads by channelHow many leads came from each channel?Where to shift budget between channels
Customers by campaignWhich campaigns produced new customers each month?Which campaigns deserve more investment
Revenue by campaignHow much revenue did each campaign generate?Whether campaign revenue exceeds ad spend

Report types described in captured guidance; figures in examples are illustrative.

Frequently asked questions

What is the shortest setup sequence?

Add the attribution snippet to the website, add the five hidden fields to lead forms, apply consistent UTM parameters to Facebook Ads, then let form submissions carry the stored channel data into Insightly with the lead details.

Which hidden fields are needed on forms?

Channel, Channel Drilldown 1, Channel Drilldown 2, Channel Drilldown 3 and Channel Drilldown 4. Most form builders let you insert a hidden field type or hide an existing field in its settings.

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 name and utm_content for the specific ad. Consistency matters more than the exact naming style.

Does the setup still work if someone browses before submitting a form?

Yes. Storing the parameters in a browser cookie means the values can still be written to the form even if the visitor browses other pages before converting, rather than relying on parameters remaining in the current URL.

Which reports become possible in Insightly?

Build leads by channel to compare Facebook with other sources, customers by campaign to see which campaigns create paying customers, and revenue by campaign to compare campaign revenue with ad spend for a return view.