Skip to content

Track Facebook Ads in Intercom

Meta ad clicks are easy to buy and harder to attribute. This guide shows how to attach the campaign, ad set and ad behind each Intercom chat, so your CRM and reports can answer a simple question: which ads actually produce leads?

Three steps to connect Facebook Ads data to Intercom

The setup has three moving parts: tag the ad links, place the attribution script on your site, and confirm the data appears with each new chat. Once those are in place, every chat opened through the Intercom widget can carry the original source details.

  1. Add UTM parameters to your Facebook Ads.
  2. Install the attribution script on your website.
  3. Check that the ad data shows up alongside the chat in Intercom.

Step 1: Tag Facebook Ad links with UTM parameters

UTM parameters are short text fragments appended to a URL. Analytics tools read them to identify where a visitor came from. For a Meta ad, the recommended pattern is:

  • UTM Medium = paidsocial
  • UTM Source = facebook
  • UTM Campaign = the campaign name
  • UTM Term = the ad set name
  • UTM Content = the specific ad

A tagged link might look like this: https://roipaths.com/integrations/intercom?utm_medium=paidsocial&utm_source=facebook&utm_campaign=brand-campaign. The exact values are yours to choose, but keeping the medium and source consistent is what makes later reporting reliable.

Step 2: Install the attribution script on your website

Once you have an account, the platform provides a small snippet of code to place on your website. Where that snippet goes depends on how your site is built, but the task itself is usually brief. Step-by-step placement guidance is available for common website builders, including WordPress, Wix, Squarespace and Webflow.

Step 3: Confirm ad data is captured with each Intercom chat

Once the script is live, it begins tracking where visitors come from, including clicks from Facebook Ads. When a visitor opens a chat through the Intercom widget, the attribution data — campaign, ad set and ad name — is passed into Intercom. It appears beside the conversation and is stored with the lead.

What gets captured at the chat moment

The following field map shows the practical inputs and outputs of the setup. It is a reader aid, not a schema.

  • UTM Medium: paidsocial — used to classify the channel.
  • UTM Source: facebook — identifies the network.
  • UTM Campaign: campaign name — groups leads by campaign.
  • UTM Term: ad set name — groups leads by ad set.
  • UTM Content: ad name — identifies the specific creative.
  • Landing page: the first page visited — recorded in full and grouped by section.

A worked example: a visitor clicks an ad pointing to https://roipaths.com/integrations/intercom with utm_medium=paidsocial and utm_source=facebook. They browse several pages, then open an Intercom chat. The chat record can show Paid Social as the channel, Facebook as the source, and the campaign name from the link. If the same visitor had arrived from an organic search instead, the chat would carry that source rather than the ad data.

Where to send the captured data

Two practical destinations are common:

  • CRM: push the data into Salesforce, Pipedrive, HubSpot or another CRM. Reports can then show how many leads came from Facebook Ads, how many became customers, and the revenue involved.
  • Spreadsheet: use a tool such as Zapier to send records to Google Sheets or Excel. From there you can filter, sort, analyse, or connect to Looker Studio or Power BI for dashboards.

A quick decision checklist: choose the CRM route if you need lead-to-customer and revenue reporting in one place; choose the spreadsheet route if you need fast ad-hoc analysis or a custom dashboard before committing to a CRM workflow.

What the attribution layer adds

Four capabilities matter when comparing this approach with manual UTM tracking:

  • Broader capture: every chat lead is attributed, not only those from Facebook Ads. Organic search, social clicks and direct visits are recorded too.
  • Persistence: when a visitor first arrives, their UTM values are saved in the browser. Navigation across pages, a later return, or a delayed chat start does not erase the original source — it is still there to be passed along.
  • Normalisation: tags that disagree on spelling, such as utm_source=facebook versus utm_source=fb, are reconciled. Instead of fragmenting your reporting into two sources, those leads land in the Paid Social channel.
  • Landing-page context: the first page visited is recorded in full and grouped by section, for example /blog.

Three reports to run once data is flowing

With ad data attached to each chat and forwarded to a CRM or analytics tool, three reports give a useful starting view.

  1. Leads by channel. Compare Paid Social with Paid Search, Organic Search and other channels. This supports budget decisions, such as shifting spend toward a channel that produces more leads.
  2. Leads by network. Meta distributes ads across Instagram, Messenger, WhatsApp and other placements. A network breakdown shows which placements generate leads and which do not.
  3. Leads by campaign. See how many leads each campaign produces month by month, moving beyond clicks and impressions to actual lead volume.

These reports are illustrative patterns, not a claim about any specific account's results.

Getting started

Connecting an attribution script to Intercom means each chat can carry a record of where the visitor came from. The work is straightforward: tag your ad links, add the script to your site, and verify that new chats show the source details. After that, your choice of CRM or spreadsheet determines how you analyse and report on the results.

Frequently asked questions

Does the attribution data survive if a visitor browses before chatting?

Yes. The UTM values are stored in the visitor's browser when they first land. They can move across pages, leave and return, and the original source is still available when they open a chat.

What happens if some ads use utm_source=facebook and others use utm_source=fb?

The attribution layer normalises inconsistent tags and assigns those leads to the Paid Social channel, rather than treating them as two separate sources.

Is a chat the same as a converted lead?

No. A chat records that someone made contact and carries their source data. Whether they become a customer is a separate step, usually tracked in the CRM after the lead is qualified.