How to track Google Ads campaigns in Chargebee
If you run Google Ads for a subscription product, clicks and trial signups are only the first part of the story. The useful question is which campaigns, ad groups and ads produce paying customers and revenue. This guide shows how to carry Google Ads data into Chargebee, how to choose between the two capture methods, and how to read the resulting reports without being misled by lead volume alone.
Why customer and revenue tracking changes the decision
A lead-count view can point you toward the wrong campaign. Consider a project management software company running two campaigns: one for task management searches and one for project management searches. The first table below is the kind of summary you get when you only count visitors and form completions. Both campaigns spent the same amount, but the task management campaign produced twice the visitors and twice the goal completions, so it looks like the stronger buy.
The second table adds customers and revenue. The picture changes: the project management campaign produced fewer leads but more customers and much more revenue. That is the difference between optimizing for form fills and optimizing for the business outcome you actually want.
Read the two tables together. The first is a lead-volume snapshot; the second is the same snapshot extended with customer and revenue columns. The campaign names, spend, visitor and lead figures are the same in both, so any change in your conclusion comes from the added customer and revenue evidence, not from different traffic.
Reading the campaign comparison correctly
The second table shows 2 customers and $8,000 of revenue for the task management campaign, and 5 customers and $25,000 for the project management campaign. The supporting list in the original article states 12 customers for the project management campaign and 2 for the task management campaign. That 12 is a typo in the source: the list's own derived ratios are consistent with the table's 5 and 2 customers, not with 12. The 60% versus 14% trial-to-customer conversion, the $2,083 versus $1,142 average customer value and the $416 versus $714 cost per customer all follow from 5 and 2 customers. Use the table's customer counts as the figures that match the stated ratios.
Use the example as a method, not as a benchmark. The lesson is that a campaign with fewer leads can still be the better investment when its trial-to-customer conversion, average customer value and cost per customer are stronger. Before you copy any ratio from this example into a budget decision, rebuild it from your own Chargebee records.
The four-step capture workflow
The workflow has four stages: tag the ads, store the attribution data, pass it into Chargebee at signup, and report on it inside Chargebee or in a connected analytics tool.
- Add UTM parameters to your ads. These are extra pieces of text appended to the destination URL. A typical Google Ads pattern is medium set to paid search, source set to Google, campaign set to the campaign name, term set to the ad group name, and content set to the specific ad. You can build the tagged URL with a free UTM builder rather than typing the query string by hand.
- Let the attribution tool store the data in a cookie. Once its code is on your site, it checks arriving visitors for those UTM parameters. When they are present, the visitor is assigned to the Paid Search channel and the information is kept in a browser cookie so it remains available when the visitor later submits a form.
- Send the data to Chargebee at form submission. The Google Ads data travels with the other details the user enters, such as name, company and phone number. There are two delivery methods, covered in the checklist below.
- Report on customers and revenue. With campaign, ad group, keyword and related data stored alongside each customer, you can build reports such as new customers by campaign, new revenue by ad group, average revenue per customer by ad, customer lifetime value by channel or campaign, and churn rate by channel or campaign. You can report inside Chargebee or sync Chargebee data into another analytics product for deeper analysis.
Checklist: hidden form fields or cookie-based capture
Both methods move the same attribution data into Chargebee, but they suit different signup flows.
- Use hidden form fields when every signup passes through a form you control. Add the hidden fields to the form, let the attribution tool write the values into them, and submit the form as usual. The attribution data arrives with the user-entered fields.
- Use cookie-based capture when users can sign up without filling a form, for example by logging in with a Google or Facebook account. A short line of JavaScript reads the stored UTM parameters from the cookie and passes them into Chargebee during registration.
- Confirm the destination fields exist in your Chargebee setup before you wire either method. The point of the exercise is to have campaign, ad group, ad and landing-page values stored on the customer record, not merely collected on the page.
- Test one signup per method and inspect the resulting customer record. If the attribution fields are empty, fix the capture path before you spend more on ads.
- Keep your UTM naming consistent across campaigns. Inconsistent source spellings are the most common reason a report splits one channel into several rows.
Field map: UTM parameter to reporting dimension
The mapping below follows the common Google Ads tagging pattern. It is a starting convention you can adapt to your own campaign structure, not a fixed schema.
- UTM Medium: paid search. This is the channel-level label.
- UTM Source: Google. This identifies the platform.
- UTM Campaign: the Google Ads campaign name. Use this to compare campaigns.
- UTM Term: the ad group name. Use this to compare ad groups within a campaign.
- UTM Content: the specific ad. Use this to compare creative variants.
Two further dimensions are captured independently of the UTM string: the landing page and the landing page category. The landing page is the full URL the visitor first arrived on, and the category is its section, such as a blog. Keeping both lets you report on a whole content section and on individual posts within it.
Two different attribution failures
Lost parameters and messy parameters look similar in a report, but they have different causes and different fixes.
Lost parameters happen when the UTM string is only read on the page where the form is completed. If a visitor lands on a campaign page, clicks through to a separate signup page and completes the form there, the original parameters are no longer in the URL. Cookie storage solves this because the values persist across pages in the visitor's browser.
Messy parameters happen when the same channel is tagged in several ways. If one campaign uses a capitalized source with a domain, another uses a lowercase source, and a third uses an older platform name, a raw UTM report shows three separate sources. You then have to merge them by hand. Normalizing the source value at capture time, or enforcing a naming convention at build time, prevents the split.
Diagnose which failure you have before changing tools. If the attribution fields are empty, you have a loss problem. If they are populated but fragmented, you have a consistency problem.
Why capture all channels, not only Google Ads
A Google Ads-only view can flatter paid search simply because other channels were never measured. The same capture method can record organic search, paid social, organic social and other sources, so every signup and customer has a source. That broader view lets you compare paid search against organic search and the rest of your mix on customers and revenue, not just on traffic.
This matters when organic content is doing more work than expected. If your blog or another content section produces more signups and customers than a paid campaign, you can shift budget with evidence. Landing-page and landing-page-category capture make that comparison possible at both the section and the individual-post level.
Putting it to work
Start by tagging your Google Ads URLs with a consistent UTM convention. Choose hidden form fields or cookie-based capture according to how users sign up, and verify that the attribution values actually land on the Chargebee customer record. Then build reports around customers, revenue, average customer value and churn by campaign or ad group, and compare those results with your other channels. The aim is a budget decision based on which campaigns produce durable revenue, not on which ones produce the most form fills.
| Metric | Task Management Campaign | Project Management Campaign |
|---|---|---|
| Spend | $2,000 | $2,000 |
| Visitors | 200 | 100 |
| Goal Completions | 20 | 10 |
Captured historical example. Figures are illustrative and are not current benchmarks.
| Metric | Task Management Campaign | Project Management Campaign |
|---|---|---|
| Spend | $2,000 | $2,000 |
| Visitors | 200 | 100 |
| Leads | 20 | 10 |
| Customers | 2 | 5 |
| Revenue | $8,000 | $25,000 |
Illustrative example. The customer counts here (2 task management, 5 project management) are the ones consistent with the stated trial-to-customer conversion, average customer value and cost-per-customer figures; the accompanying list's figure of 12 project management customers is a typo. Rebuild any ratio from your own Chargebee records before using it in a budget decision.
Frequently asked questions
Do I have to use UTM parameters to track Google Ads in Chargebee?
Yes. The capture method relies on UTM parameters appended to your ad destination URLs. Without them, the attribution tool has no campaign, ad group or ad information to store and pass into Chargebee.
What happens if a visitor lands on one page and signs up on another?
If the UTM parameters are only read from the current URL, they are lost when the form sits on a different page. Cookie-based storage keeps the values available across pages, so the signup can still be attributed to the original campaign.
Why does my Google Ads traffic show up as several different sources?
Inconsistent source spellings fragment one channel into multiple rows. Capitalization, domain suffixes and older platform names are common causes. Normalize the source value at capture time or enforce a naming convention when you build the URLs.
Can I report on landing pages as well as campaigns?
Yes. The landing page and its category can be captured alongside the UTM data and stored with the customer, so you can compare a whole content section with individual posts, or compare landing pages within a campaign.
Can I report inside Chargebee, or do I need another analytics tool?
Both are possible. You can build reports in Chargebee, or sync Chargebee data into another analytics product for more detailed analysis. The reports listed in this guide, such as new customers by campaign and customer lifetime value by channel, are examples of what the stored data supports.
| Task Management Campaign | Project Management Campaign | |
|---|---|---|
| Spend | $2,000 | $2,000 |
| Visitors | 200 | 100 |
| Goal Completions | 20 | 10 |
| Task Management Campaign | Project Management Campaign | |
|---|---|---|
| Spend | $2,000 | $2,000 |
| Visitors | 200 | 100 |
| Leads | 20 | 10 |
| Customers | 2 | 5 |
| Revenue | $8,000 | $25,000 |