Skip to content

How to Track Google Ads Campaigns in Zuora

Google Ads reports tell you what happened before the sale. Zuora holds what happens after: who became a customer, what they pay, and how long they stay. This guide shows how to connect the two so campaign decisions rest on customers and revenue rather than clicks and form fills.

Why clicks and leads are not enough

A campaign can win on traffic and still lose on business results. Consider a software company running two Google Ads campaigns, one for task management software and one for project management software. A traffic-and-lead view might show the task campaign ahead. A customer-and-revenue view can reverse that conclusion.

The two tables below are the supplied comparison figures. Read them together: the first shows spend, visitors, and goal completions; the second adds leads, customers, and revenue. The point is not that one campaign is always better, but that the metric you stop at changes the decision you make.

Campaign comparison: traffic view and revenue view

The first table is the traffic-and-goal view. The second table extends the same campaigns through leads, customers, and revenue. Both are reproduced in full as supplied.

Reading the example

In the supplied figures, the task management campaign draws twice the visitors (200 vs. 100) at the same $2,000 spend, and twice the goal completions (20 vs. 10). On that basis it looks like the campaign to fund.

The revenue view tells a different story. The project management campaign produces 5 customers against 2, and $25,000 in revenue against $8,000. The supplied analysis also notes a higher trial-to-customer conversion rate for the project campaign (60% vs. 14%), a higher average customer value ($2,083 vs. $1,142), and a lower cost per customer ($416 vs. $714).

The lesson for your own account: decide in advance which metric ends the comparison. If it is leads, you will optimize for leads. If it is customers and revenue, you need campaign data attached to the customer record in Zuora.

Four steps to get Google Ads data into Zuora

The workflow has four stages: tag the ads, persist the attribution data, deliver it to Zuora at signup, and report on it. Each stage has a failure mode worth checking before you rely on the numbers.

Step 1: Tag your ads with UTM parameters

UTM parameters are extra text appended to the destination URL. They tell your tracking layer which campaign, ad group, and ad sent the visitor.

A tagged URL follows the pattern of a base page plus query parameters, for example a page path followed by utm_medium, utm_source, and utm_campaign values. The supplied guidance recommends this convention for Google Ads:

  • UTM Medium = Paid search
  • UTM Source = Google
  • UTM Campaign = the Google Ads campaign name
  • UTM Term = the ad group name
  • UTM Content = the specific ad

You can build these by hand or with a free UTM builder. The important discipline is consistency: the same campaign should always produce the same values.

Step 3: Deliver the data to Zuora

When a visitor submits a form, the Google Ads data travels into Zuora alongside the other fields they entered, such as name, email, and company. There are two delivery methods:

  • Hidden fields in forms. Add hidden fields to your form; the tracking layer writes the attribution values into them automatically, and the submission carries them into Zuora.
  • Retrieve from the cookie. Add a short JavaScript line to your registration flow so the UTM values are read from the cookie and sent to Zuora. This suits signups that skip a form, such as social or Google account sign-in.

Choose hidden fields when a standard form is the main signup path. Choose cookie retrieval when the signup path bypasses a form or when you need the values available in application code.

Step 4: Report on campaigns inside Zuora or downstream

Once campaign data and customer records sit together in Zuora, you can build reports such as:

  • New customers each month by campaign
  • New revenue each month by ad group
  • Average revenue per customer by ad
  • Customer lifetime value by channel or campaign
  • Customer churn rate by channel or campaign

You can run these with Zuora's built-in reporting or sync the data into an analytics tool for deeper analysis. The supplied material points to Looker, Mode, and Grow as examples of downstream tools.

What a dedicated attribution layer adds

Raw UTM capture can work, but four practical gaps tend to appear:

  1. Coverage. A dedicated layer can classify all traffic sources, not only Google Ads, so organic search, organic social, and paid social appear alongside paid search in the same reports.
  2. Persistence across pages. If the form lives on a different page from the landing page, UTM parameters in the URL are lost. A cookie keeps them available.
  3. Cleaner values. Inconsistent source values such as Google.com, google, and adwords would otherwise appear as three separate sources needing manual stitching. Normalization groups them under one channel.
  4. Landing page context. Capturing the landing page and its category lets you compare a whole section, such as a blog, against individual posts.

Pre-launch checklist

  • Every Google Ads campaign URL carries the same UTM convention.
  • The tracking script is present on all pages where a visitor might convert.
  • The cookie persists long enough to cover your typical consideration period.
  • Hidden fields or cookie retrieval are wired into every signup path, including social sign-in.
  • A test signup produces a Zuora record with campaign, ad group, and ad values populated.
  • Source values are normalized so capitalization and domain variants do not split your reports.
  • At least one report ties spend to customers and revenue, not only to leads.

Bottom line

Tracking Google Ads in Zuora is mostly a data-plumbing task: tag consistently, persist the attribution, deliver it at signup, and report on customers and revenue. The campaign comparison above shows why the last step matters. When you can see which campaigns produce customers and revenue, budget decisions become evidence-based rather than click-based.

Frequently asked questions

Do I need UTM parameters if I already use Google Ads auto-tagging?

The workflow described here relies on UTM parameters to identify campaign, ad group, and ad. If you use auto-tagging, you will need a separate mechanism to translate the click identifier into campaign data before it reaches Zuora. The supplied guidance assumes UTM tagging.

What happens if the form is on a different page from the landing page?

If UTM parameters are read only from the URL, they are lost when the visitor moves to another page before converting. Persisting the values in a cookie keeps them available at the form page.

Can I track signups that skip a form, such as social sign-in?

Yes. Instead of hidden fields, add a short JavaScript line to the registration flow so the UTM values are read from the cookie and sent to Zuora.

Which reports become possible once campaign data is in Zuora?

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 are all possible. You can run them in Zuora or sync the data to an analytics tool.

Traffic and goal completions by campaign
Task Management CampaignProject Management Campaign
Spend$2,000$2,000
Visitors200100
Goal Completions2010

Supplied illustrative figures; not a live benchmark.

Customers and revenue by campaign
Task Management CampaignProject Management Campaign
Spend$2,000$2,000
Visitors200100
Leads2010
Customers25
Revenue$8,000$25,000

Supplied illustrative figures; not a live benchmark.