Track Google Ads Campaigns in Zendesk Sell
You can connect paid-search activity to the leads, opportunities, customers and revenue created in Zendesk Sell by tagging ads consistently, capturing the resulting channel data on lead forms, and reporting on the stored fields inside the CRM.
How the attribution flow works
A visitor arrives from a paid campaign. A small attribution script reads the technical origin signals on that visit, classifies the channel, and stores the result in a browser cookie. When the visitor later submits a lead form, the stored channel details are written into hidden form fields and sent to Zendesk Sell together with the submitted contact information. The resulting lead record therefore shows not only who converted, but also which campaign, ad group, ad and landing page preceded the conversion.
Four-step setup checklist
Use this sequence before building reports:
1. Tag the ads
Tag every paid URL with a consistent UTM structure. For Google Ads, use paid search for the medium, Google for the source, the campaign name for the campaign value, the ad-group name for the term value, and the specific ad for the content value. Consistency matters more than inventing new labels for each campaign.
2. Add hidden form fields
Add hidden fields to each lead-capture form for Channel, Channel Drilldown 1, Channel Drilldown 2, Channel Drilldown 3, Landing Page and Landing Page Group. Visitors do not see these fields, but the form system can still submit their values with the lead.
3. Populate the fields at submission
On form submission, populate those fields from the stored attribution data. A worked example is a visitor arriving from a brand paid-search campaign for a free-account ad: Channel becomes Paid search, Drilldown 1 becomes Google, Drilldown 2 becomes the brand campaign, and Drilldown 3 becomes the free-account ad. The landing page and its group are captured alongside those values.
4. Report inside Zendesk Sell
Send the completed lead record into Zendesk Sell. Once the data is present, use the CRM's native reporting or a connected business-intelligence tool to analyse performance by campaign, ad group or ad.
Reports worth building first
Build three monthly views and compare them together. Leads by campaign show volume and the effect of optimisation over time. Customers by campaign reveal whether apparently productive lead sources actually convert; a campaign with many leads but no customers may not justify continued spend. Revenue by campaign connects the same breakdown to commercial value, making it possible to judge return against campaign cost. In the captured example, March paid-social activity was associated with $236,156 in new revenue, illustrating how the revenue view can be compared with spend to assess return.
Why normalised attribution beats raw UTM values
Raw UTM capture has three practical weaknesses. First, it may miss non-paid visits, leaving organic, direct and referral leads unattributed. Second, UTM values on the landing page can disappear when the conversion form sits on a different page. Third, inconsistent tagging creates fragmented sources that need manual cleaning. Cookie-based attribution addresses the second issue, broader channel classification addresses the first, and normalisation addresses the third. Landing-page and landing-page-group capture adds a further view of which site sections and individual pages produce leads, customers and revenue.
Decision checklist
Before trusting the reports, check that every campaign uses the same UTM conventions, every lead form contains all six hidden fields, test submissions populate the drilldowns correctly, and leads from non-paid channels are also classified. Then review leads, customers and revenue together rather than optimising for lead volume alone. If you plan to evaluate a trial or paid plan, confirm the current offer terms, duration and any usage limits directly with the provider before relying on them.
Frequently asked questions
Does this only track Google Ads traffic?
No. The attribution script also records visits from organic search, organic social, direct and referral traffic, so reports can cover every lead source rather than paid campaigns alone.
What if a visitor lands on one page but submits a form on another?
Yes. Channel data is stored in a browser cookie on arrival, so it can still be attached when the form is submitted on a later page.
Why not pass raw UTM values directly into the CRM?
Raw values can create duplicate sources through differences such as capitalisation or naming variants. Normalising them into a channel hierarchy avoids manual stitching in reports.
Which fields should I report on first?
Use the channel and drilldown fields for campaign, ad group and ad breakdowns, and use the landing-page fields to compare pages and page groups. Then compare leads, customers and revenue side by side.