Skip to content

Track Facebook Ads in Zendesk Sell: UTMs, hidden fields and campaign reports

You can connect Facebook campaign activity to leads, opportunities, customers and revenue inside Zendesk Sell by capturing UTM parameters on arrival, storing them in a cookie, and writing them into hidden form fields at submission. This guide explains the setup, the field mapping, a worked example, and the reports that become possible once the data is in the CRM.

Why campaign attribution matters

Without campaign-level attribution, two costly mistakes are easy to make. A profitable Facebook programme may be underfunded because its customer contribution is invisible, while an unprofitable one may keep consuming budget that could work harder elsewhere. The fix is to carry the campaign context from the ad click through to the CRM record, so each lead and deal can be grouped by channel, campaign, ad set and ad.

How the attribution flow works

A website attribution snippet examines how a visitor arrived, classifies that arrival into a standard marketing channel, and stores the result in a browser cookie. When the visitor later submits a form, the stored values are placed into hidden fields on that form. The form submission then carries both the person's contact details and the attribution values into Zendesk Sell and any other connected tools.

Step 1: Install the snippet and add hidden fields

Install the attribution snippet on the website, then add five hidden fields to each lead-capture form: Channel, Channel Drilldown 1, Channel Drilldown 2, Channel Drilldown 3 and Channel Drilldown 4. Most form builders let you drag in a hidden field type or convert an existing field to hidden in its settings. Check each form separately, because a field added to one form will not automatically appear on another.

Step 2: Tag every Facebook ad with UTM parameters

Add UTM parameters to the destination URL in every Facebook campaign. UTM values are extra text appended to the URL, for example a destination path followed by utm_medium=paidsocial, utm_source=facebook and utm_campaign=brand-campaign. A consistent convention makes later reporting far cleaner: set UTM Medium to Paid Social, UTM Source to Facebook, UTM Campaign to the campaign name, UTM Term to the ad set name, and UTM Content to the specific ad. Apply the same pattern to every campaign before launch, and use a URL builder if it helps you avoid typos.

Step 3: Capture UTMs and write them into the form

On arrival from a Facebook ad, the attribution tool reads the UTM parameters and saves them in a cookie, so browsing to other pages does not lose them. At form submission, it writes the values into the hidden fields alongside the lead's name, email and other details. It also captures the landing page and landing page group, which lets you see which content entry point preceded the conversion.

Worked example: from ad click to CRM record

Suppose a marketer promotes Zendesk Sell with a Facebook ad, a visitor browses the site, then requests a demo. With the UTM convention above, the hidden fields could contain: Channel = Paid Social; Channel Drilldown 1 = Facebook; Channel Drilldown 2 = Brand Campaign; Channel Drilldown 3 = North America Ad Group; Channel Drilldown 4 = Green Ad. That single record now tells the sales team exactly which campaign, ad set and ad produced the lead, without anyone manually entering the data.

Step 4: Send the data into Zendesk Sell and verify it

When the form is submitted, the attribution values travel into Zendesk Sell together with the lead's contact details. From there, build reports with Zendesk's native reporting tools, or pass the data to a BI platform such as Tableau or Looker for more advanced analysis. Before trusting the reports, submit a test form from a tagged Facebook URL and confirm all five drilldown fields arrive correctly on the CRM record.

Why use a dedicated attribution tool

The setup captures more than Facebook traffic. Organic Search, Organic Social, Referral and Direct arrivals are classified too, giving a complete picture of lead origins. Cookie storage keeps UTMs intact across pages, normalisation reduces the damage from inconsistent naming, and landing page capture shows which content is converting. Together these features make the CRM data suitable for budget decisions, not just campaign counts.

Three reports to build once data flows

Leads by channel: count leads per channel to see how Facebook compares with SEO, Google Ads and other sources, then shift budget toward the strongest performers. Customers by campaign: count new customers per month per Facebook campaign to identify which campaigns produce buyers, not just enquiries. Revenue by campaign: total revenue per month per campaign and compare it with ad spend plus agency and creative costs to judge return on investment. In the captured example, $65,000 of new revenue in August from Facebook Ads would represent a positive return if total associated costs were lower, and breaking that figure down by campaign shows where to invest more or stop spending.

Pre-launch checklist

Use this checklist before scaling spend: snippet installed on every page; five hidden fields present on every lead form; UTM convention documented and applied to all live campaigns; cookie persistence confirmed across a multi-page test journey; test submission verified in Zendesk Sell; and the three reports above built and reviewed. Revisit the UTM convention whenever a new campaign structure is introduced, because clean input is what makes the downstream reporting trustworthy.

Frequently asked questions

Does this only show Facebook traffic?

No. The same hidden-field setup also captures channels such as Organic Search, Organic Social, Referral and Direct, so reports can compare Facebook against other sources rather than showing Facebook in isolation.

What if a visitor browses several pages before submitting a form?

Yes, the UTM values are stored in a browser cookie when the visitor first arrives. That means the values can still be written into the form even if the visitor browses other pages before submitting.

What happens if UTM naming is inconsistent across campaigns?

Inconsistent values are normalised into a standard channel. For example, variations such as facebook and facebook.com in the source value can still be assigned to Paid Social, reducing split reporting from small naming differences.

Where do I build the reports?

Once the attribution fields arrive in Zendesk Sell with the lead record, you can use Zendesk's native reporting, or send the data to a BI tool such as Tableau or Looker for more advanced breakdowns.