Skip to content

Track Google Ads campaigns in Chargify: from click to customer and revenue

Google Ads can show spend, visits and form completions, but that stops short of the question subscription businesses need answered: which campaigns create paying customers and how much revenue follows? This guide explains how campaign tagging, a browser cookie, and form data together carry the original campaign through to Chargify, so reporting can connect spend to customers and revenue rather than only to traffic.

Why traffic alone can mislead campaign decisions

Consider a subscription software seller running two Google Ads campaigns with identical spend. One campaign brings more visits and more completed forms, so a traffic-only view favours it. Extend the same period through to paid customers and revenue and the picture can reverse: fewer, higher-intent leads may convert at a much higher rate, produce larger average customer value, and cost less per customer. That reversal is why campaign decisions need downstream billing outcomes, not only upstream clicks. The worked example below uses the source's captured figures to show the decision change.

Step 1: Tag every ad URL consistently

Start by appending UTM parameters to the destination URL for each ad. These are additional query values that label the visit. A consistent Google Ads convention is: medium for the buying type, source for the platform, campaign for the campaign name, term for the ad group, and content for the specific ad. Consistency matters more than clever naming — pick one spelling and capitalisation pattern and apply it everywhere. Free UTM builders can help assemble the URL, but the naming discipline is what makes later reporting reliable.

Step 2: Store the campaign context in a cookie

When the attribution script is installed on the site, it checks incoming visits for those parameters. If they identify paid search, it records that channel assignment and saves the values in a cookie in the visitor's browser. The cookie is the bridge between arrival and conversion: it keeps the campaign context available later, when the visitor starts a trial or buys a subscription, even if that action happens on a different page from the landing page.

Step 3: Pass the stored values into Chargify at signup

At conversion, the stored campaign values travel into Chargify alongside the details the visitor entered, such as name, email and company. There are two routes. Hidden form fields let the tool fill values automatically so they submit with the form. Alternatively, a small script during registration reads the cookie directly — useful when signup happens through a social or Google account and there is no conventional form to carry hidden fields. Choose based on how your registration flow actually works.

Step 4: Report customers and revenue by campaign

Once campaign, ad group and keyword context sit on the Chargify record, reporting can group billing outcomes by acquisition source. Useful starting reports include new customers per month by campaign, new revenue per month by ad group, average revenue per customer by ad, lifetime value by channel or campaign, and churn by channel or campaign. The same data can also be synced to tools such as ChartMogul or ProfitWell for deeper analysis. Before building reports, run this checklist: every ad URL tagged, naming normalised, cookie present on landing, values arriving on the Chargify record, and one test signup traced end to end.

What makes the cookie-based approach stronger

Four practical advantages separate this approach from raw UTM forwarding. First, it captures all signup sources — organic search, paid and organic social and others — so Google Ads can be judged in context rather than in isolation. Second, cookie storage survives navigation between landing and signup pages. Third, values are normalised to a channel, avoiding duplicate sources created by capitalisation or naming variants. Fourth, landing page and landing page category are also captured, so content sections such as a blog can be assessed both as a whole and post by post.

Same spend, different downstream value: traffic view vs customer view
MetricTask Management CampaignProject Management Campaign
Spend$2,000$2,000
Visitors200100
Leads / goal completions2010
Customers (table)25
Revenue (table)$8,000$25,000
Customers (source narrative bullet)212
Free trial-to-customer conversion (source narrative)14%60%
Average customer value (source narrative)$1,142 per customer$2,083 per customer
Cost per customer (source narrative)$714$416

Illustrative captured example from source; figures are example data, not current verified results. Source conflict flagged: the source table shows 5 Project Management customers, while the source narrative bullet says 12; narrative conversion, revenue-per-customer and cost-per-customer figures below are reproduced as stated in that narrative and do not reconcile with the table counts.

UTM field map for Google Ads URLs
UTM parameterGoogle Ads conventionWhat it identifies
utm_mediumPaid searchBuying type / channel
utm_sourceGooglePlatform
utm_campaignCampaign nameCampaign
utm_termAd group nameAd group
utm_contentSpecific adAd

General best-practice convention described in source; exact values are owner-configurable.

Frequently asked questions

How do I get Google Ads campaign data into Chargify?

Add consistent UTM parameters to campaign URLs, store them in a first-party cookie when the visitor arrives, then pass the stored values into Chargify when the signup or purchase form is submitted — via hidden fields or by reading the cookie during registration. Once stored in Chargify, report customers and revenue by campaign, ad group, ad, channel, or landing page.

What if a visitor lands on one page but signs up on another?

Yes. The cookie approach preserves the original campaign values even when the visitor moves from the ad landing page to a separate signup page, whereas reading UTM parameters only on the submission page loses them after navigation.

Why not send raw UTM values directly to Chargify?

Raw values such as different capitalisations or variants of the same source can appear as separate sources in reports. Normalising them to a single channel, such as Paid Search, avoids manual stitching and keeps campaign reporting cleaner.

Task Management CampaignProject Management Campaign
Spend$2,000$2,000
Visitors200100
Goal Completions2010
Task Management CampaignProject Management Campaign
Spend$2,000$2,000
Visitors200100
Leads2010
Customers25
Revenue$8,000$25,000