How to Track Google Ads Campaigns in SaaSOptics
If you can see which Google Ads campaign, ad group, keyword, and landing page brought each customer into your SaaS product, you can report on revenue and customer value instead of guessing from click and lead counts alone. This guide walks through the capture setup, the two ways to pass the data into SaaSOptics, and the reports worth building once the data is there.
Why lead counts alone mislead
A lead-only view can make the wrong campaign look like the winner. Consider a software business running two Google Ads campaigns, one for task management software and one for project management software. A click-and-lead report shows the task campaign ahead on volume. Once you follow the same campaigns through to customers and revenue, the picture reverses.
The two comparison tables below are the supplied campaign examples. They are a dated illustrative reference, not a live benchmark; check your own current numbers before reallocating budget.
[table0001]
[table0002]
Read together, the tables show why the task campaign's lead advantage does not translate into revenue. The project campaign produces more customers and far more revenue from the same spend. The supplied source also lists supporting figures for this example, but they do not agree with its own table: the source text claims 12 project-campaign customers where the table shows 5. Treat the table as the authoritative illustration and the list figures as an unresolved inconsistency in the original material. Either way, the direction holds: the project campaign wins on customers and revenue despite fewer leads.
The practical lesson: report on customers and revenue by campaign, not on form completions alone. When you attach source data to every customer record, you can compare campaigns on the metrics that actually fund the business.
Four steps to capture Google Ads data in SaaSOptics
The setup has four stages: tag the ads, persist the data in the browser, pass it into SaaSOptics, and report on it. Each stage has a specific job, and skipping one usually shows up later as missing or messy source data.
Step 1: Add UTM parameters to your ads
UTM parameters are extra text appended to the URL you send visitors to. A final URL might look like this: https://roipaths.com/integrations/salesforce?utm_medium=paidsearch&utm_source=google&utm_campaign=brand-campaign. You can design your own structure, but a common Google Ads convention is:
- UTM Medium = Paid search
- UTM Source = Google
- UTM Campaign = the name of your Google Ads campaign
- UTM Term = the name of the ad group the ad belongs to
- UTM Content = the specific ad
Free UTM builder tools exist online, so building the tagged URLs is not the hard part. The hard part is making sure the values are consistent and that they survive the journey to the signup form.
Step 3: Pass the Google Ads data into SaaSOptics
When a visitor submits a form, the Google Ads data travels into SaaSOptics alongside the name, company, number, email address, and other fields the visitor entered. There are two ways to make that handoff:
- Hidden fields in forms. Add a set of hidden fields to your forms; the tracking tool writes the necessary values automatically, and they are submitted with the rest of the form data.
- Retrieved from the cookie. A short line of JavaScript in your registration flow reads the UTM values from the cookie and passes them into SaaSOptics. This matters when users can sign up through Google or Facebook sign-in and never fill in a form.
Choose hidden fields when every signup goes through a form you control. Choose the cookie/JavaScript route when social sign-in or multi-step registration skips the form. Many teams use both, with the cookie route as the fallback.
Step 4: Build reports in SaaSOptics and downstream tools
Once campaign, ad group, keyword, and landing-page data sit alongside each customer, you can build reports such as:
- New customers added each month by campaign
- New revenue added 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 inside SaaSOptics itself, or sync the data into analytics tools such as Looker, Profitwell, and Chartmogul for deeper analysis. The downstream tools are optional; the important part is that the source fields are attached to the customer record before reporting begins.
What a dedicated capture layer adds
Other methods exist for getting Google Ads data into SaaSOptics. A dedicated capture layer earns its place for four reasons.
It captures all traffic, not just ads. Organic search, paid social, organic social, and other channels are classified too, so SaaSOptics reports can show the source of every customer. If SEO signups convert better than paid campaigns, you can see that and shift budget accordingly.
It remembers the data across pages. A URL-only approach has a narrow window: it works only when the visitor submits a form on the very page the ad sent them to. The moment the journey continues to a separate signup page, the tagged values are gone. Storing the source in a cookie closes that gap, because the value is read at submit time rather than at landing time.
It normalizes messy values. The same source can arrive spelled several ways depending on who built the ad URL — a capitalized domain, a bare lowercase word, or an old platform name. Passed through raw, each spelling becomes its own line in your reports and someone has to merge them by hand. A capture layer that treats capitalization and domain variants as equivalent collapses them into one Paid Search channel.
It captures landing-page data. Beyond channel, the landing page and landing-page category are recorded, so you can measure how your blog and other content sections perform on leads, customers, and revenue, both as a whole section and as individual posts.
Setup checklist
Before you trust the reports, confirm each item:
- Every Google Ads campaign has UTM parameters with consistent casing and values.
- UTM Campaign carries the campaign name, UTM Term the ad group, and UTM Content the specific ad.
- The tracking code is present on every page a visitor might land on.
- Your signup form includes hidden fields for the source values, or your registration flow reads them from the cookie.
- Social sign-in paths are covered by the cookie route, not only by form fields.
- A test signup from a tagged ad shows the expected campaign and channel in SaaSOptics.
- Reports compare campaigns on customers and revenue, not only on leads.
Where to go next
If you need to know how many customers and how much revenue your Google Ads produce, the setup above gives SaaSOptics the source fields it needs. The same capture also records leads from other channels, so you can see the full picture of where customers come from and where to invest next.
Frequently asked questions
Do I need to add UTM parameters to every Google Ads campaign?
Yes. The capture depends on UTM parameters being present on the ad's final URL. Without them, the visitor cannot be classified as Paid Search or attributed to a specific campaign, ad group, or ad.
What happens if a visitor lands on one page and signs up on another?
With a cookie-based capture layer, the UTM values are stored in the browser and remain available when the visitor submits a form on a different page. Simpler methods that read UTM parameters only from the current URL lose the source in that scenario.
Hidden fields or JavaScript: which should I use?
Use hidden fields when every signup passes through a form you control. Use the cookie/JavaScript route when users can sign up through Google or Facebook sign-in and skip the form. Many teams use both, with the cookie route as a fallback.
Will inconsistent UTM values break my reports?
Raw values that spell the same source differently — a capitalized domain, a bare lowercase word, or an old platform name — would appear as separate sources if passed through unchanged. A capture layer that normalizes capitalization and domain variants can classify all of them as Paid Search.
Can I report on landing pages as well as campaigns?
Yes. Capturing the landing page and landing-page category lets you measure how a blog or other content section performs on leads, customers, and revenue, both as a whole section and as individual posts.
Can I sync SaaSOptics data into other analytics tools?
Yes. SaaSOptics data can be synced into tools such as Looker, Profitwell, and Chartmogul for more detailed reporting. The downstream tool is optional; the source fields need to be attached to the customer record first.
| Task Management Campaign | Project Management Campaign | |
|---|---|---|
| Spend | $2,000 | $2,000 |
| Visitors | 200 | 100 |
| Goal Completions | 20 | 10 |
Dated illustrative example from the supplied source; not a live benchmark.
| 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 |
Dated illustrative example from the supplied source; not a live benchmark. The source's accompanying list cites 12 project-campaign customers, which conflicts with the 5 shown here.