Track Google Ads Campaigns in Stripe: A Practical Attribution Guide
If your Google Ads reports stop at clicks and form fills, you can rank campaigns by activity without knowing which ones produce paying customers. This guide explains how to carry campaign data into Stripe customer records, how to choose a capture method, and how to read the results without being misled by lead volume alone.
Why campaign decisions need customer and revenue data
A campaign can look strong at the top of the funnel and weak at the bottom. Consider a software business running two Google Ads campaigns: one for task management searches and one for project management searches. If you only compare spend, visitors and goal completions, the task campaign may appear to produce twice as many leads for the same spend.
The picture changes when you follow those leads through to customers and revenue. In the supplied comparison, the project management campaign produced fewer leads but more customers and much more revenue. That is the decision-relevant difference: the campaign with the lower lead count had the higher average customer value and the lower cost per customer.
The two comparison tables below preserve the original figures exactly. They are a worked illustration, not a benchmark for your own account. Use them to see which metrics change the conclusion, then apply the same comparison to your own Stripe data.
The lead-only view
This table shows the kind of picture you get when the measurement stops at visitors and goal completions. Both campaigns spent the same amount, but the task campaign generated twice the visitors and twice the goal completions.
The customer-and-revenue view
Once customers and revenue are attached to each campaign, the ranking reverses. The project management campaign produced more customers and substantially more revenue from the same spend.
The original article's bullet analysis goes further and reports 12 customers for the project management campaign versus 2 for the task campaign, a 60% versus 14% trial-to-customer conversion rate, an average customer value of $2,083 versus $1,142, and a cost per customer of $416 versus $714. Those derived figures do not reconcile with the table above, which shows 5 customers for the project management campaign and 2 for the task campaign. Treat the bullet figures as an unverified worked example and use the table values as the consistent set when you build your own comparison.
The four-step workflow
The workflow has four stages: tag the ads, persist the attribution, pass it into Stripe, and report on it. Each stage has a specific failure mode, so it helps to check them in order rather than treating the whole chain as one setup task.
Step 1: Add UTM parameters to your ads
UTM parameters are text appended to the destination URL. They tell an analytics tool where a visitor came from. A tagged URL might look like the original example, with the page path followed by a query string containing medium, source and campaign values.
A practical Google Ads convention is:
- 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 choose a different structure, but consistency matters more than the exact labels. Free UTM builders are widely available if you prefer not to assemble the query string by hand.
Step 3: Pass the Google Ads data into Stripe
When a visitor submits a form, the Google Ads data travels with the other submitted details, such as name, email address and company. There are two ways to make that happen.
Hidden form fields. Add hidden fields to the form and let the tracking script populate them. On submission, the values go to Stripe with the rest of the form data.
Read from the cookie. Add a short JavaScript line to the registration process so the UTM values are read from the cookie and passed into Stripe. This is the better fit when users can sign up through a Google or Facebook account and therefore never complete a form.
A simple decision rule: if every signup path includes a form you control, hidden fields are usually the simpler route. If any signup path bypasses the form, plan for cookie retrieval as well.
Step 4: Report on campaign performance
With campaign, ad group and keyword data stored alongside each customer in Stripe, 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
These reports can be run inside Stripe or by syncing Stripe data into another analytics tool. The original article points to Profitwell and Chartmogul as examples of tools used for more detailed reporting.
What this approach adds beyond a basic UTM pass-through
There are several ways to send Google Ads data into Stripe, including building your own integration. The points below are the practical differences worth checking when you compare options.
All traffic, not only ads. The same setup can record signups and customers from organic search, organic social and other channels, so paid search can be compared with the rest of the acquisition mix.
Persistence across pages. Methods that rely on the UTM parameters being present on the form page fail when the visitor lands on one page and signs up on another. A cookie keeps the attribution available across that journey.
Consistent source naming. Raw UTM values can arrive as different spellings of the same source. Normalising them avoids manually stitching together separate source rows before reporting.
Landing-page context. Capturing the landing page and its category lets you compare sections of the site, such as a blog, as well as individual posts.
Two different attribution failures
It helps to separate two problems that both look like missing campaign data.
The first is a lost parameter. The visitor clicked an ad, but the form was completed on a different page, so the UTM values were no longer in the URL. Cookie-based persistence addresses this.
The second is inconsistent labelling. The parameter was captured, but the same source appears under several spellings, so reports split one source into multiple rows. Normalisation addresses this. Check which failure you have before changing your setup, because the fixes are different.
UTM field map for reporting
Use this as a quick reference when deciding which level of detail you need in Stripe.
- utm_campaign maps to the campaign dimension, useful for monthly customer and revenue comparisons.
- utm_term maps to the ad group dimension, useful when you want to compare themes within a campaign.
- utm_content maps to the individual ad, useful for creative-level revenue per customer.
- utm_source and utm_medium identify the channel, useful for comparing paid search with organic and other sources.
- Landing page and landing-page category add a site-section view, useful for content performance.
If a report needs a dimension that is not being captured, add it at the tagging stage rather than trying to reconstruct it later.
| Metric | Task Management Campaign | Project Management Campaign |
|---|---|---|
| Spend | $2,000 | $2,000 |
| Visitors | 200 | 100 |
| Goal Completions | 20 | 10 |
Illustrative figures from the original worked example. They are not a benchmark and do not describe your account.
| 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 figures from the original worked example. They are not a benchmark and do not describe your account. The original article's bullet analysis reports different customer counts (12 vs 2) that do not reconcile with this table; the table values are preserved exactly as supplied.
Frequently asked questions
Do I have to use UTM parameters to track Google Ads in Stripe?
UTM parameters are the tagging method described here. They carry the campaign, ad group and ad information in the URL so the tracking script can identify the source. Without a tagging convention, the campaign details will not be available to pass into Stripe.
Should I use hidden form fields or read the cookie?
Use hidden fields when every signup path includes a form you control. Add cookie retrieval when a signup can happen without a form, such as signing in with a Google or Facebook account.
Why do my UTM parameters disappear before signup?
The UTM values are present only on the URL where the visitor landed. If the form is on a different page, those values are no longer in the URL. Storing the attribution in a cookie keeps it available for the later form submission.
Why does one campaign appear as several sources in my reports?
Raw UTM values can differ in capitalisation or wording, so the same source may be recorded under multiple spellings. Normalising the source values before reporting avoids splitting one source into separate rows.
What reports can I run once the data is in Stripe?
You can report 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. The reports can be run in Stripe or in another analytics tool that receives your Stripe data.
| 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 |