How to send Google Analytics attribution data into Braintree
Google Analytics can show where visitors came from, but on its own it does not connect that visit to payment, lifetime value or churn in a billing system. Passing channel and landing page context into Braintree at signup lets revenue reporting be grouped by the marketing source and content that produced each customer.
Why join visit context to billing records
Analytics tools are strong at describing visits, yet billing records hold the commercial outcomes that matter after a visit: whether a trial became a customer, what was paid, how long the account stayed and how much recurring revenue it produced. Joining the two views at the moment of signup avoids later manual matching. The visit context is captured first, stored in the browser, then attached to the signup record as it enters Braintree.
How the attribution snippet works
A small snippet on the website examines technical signals on arrival to classify the visit into a channel such as paid social, paid search or organic search. That classification is kept in a cookie. When a visitor later signs up, the stored channel information is passed to Braintree alongside the details entered in the form, including name, email address and company name. With that link in place, questions such as which ad platform produced customers, how average MRR differs between platforms, and how churn varies for organic search customers can be answered from billing data rather than guesswork.
Four steps to connect the data
Step 1: Add hidden fields to signup forms for Channel, Channel Drilldown 1, Channel Drilldown 2, Channel Drilldown 3, Landing Page and Landing Page Group. Step 2: Let the snippet populate those fields from the stored visit data when a form is completed. Step 3: Submit the form so the attribution values arrive in Braintree with the lead details. Step 4: Build reports grouped by channel, campaign, landing page or landing page group. If signups can happen through Google or Facebook account options without a standard form, use a small script that reads the cookie and passes the values onward at signup instead. Checklist before launch: confirm every signup route has the fields or script, submit a test signup from a tagged campaign link, and verify each field appears correctly in Braintree.
Channel data and landing page data
Two kinds of context are worth capturing. Channel data records how the visitor reached the site and adds detail beneath it, for example the platform, campaign, ad group or keyword behind a paid search visit. Landing page data records the first page seen and the group that page belongs to, so a blog post can be viewed both on its own and as part of the whole blog section. A worked example: a visitor arriving from a branded paid search campaign could be stored as Channel = Paid search, Drilldown 1 = Google, Drilldown 2 = Brand campaign, Drilldown 3 = Zoho, with the first landing page and its group captured alongside. That structure lets a team compare a single post against the blog overall, or one campaign against the channel total.
Reports you can build once data flows
With attribution fields flowing into Braintree, subscription metrics can be sliced by channel or campaign: new trials per month, trial-to-customer conversion, new customers, new MRR, new ARR, ARPU, lifetime value, customer churn and MRR churn. Channel reporting can answer how many signups, customers and how much MRR or ARR a platform such as LinkedIn produced, how its lifetime value compares with other channels, and what its overall return looks like against spend. Content reporting uses landing page and group to show signups by section or post, which posts convert into customers, and whether a section such as a blog generates signups that rarely become paying customers. Reports can be built with Braintree reporting tools or sent onward to analytics and business intelligence tools that integrate with Braintree for deeper analysis.
| Field | Example value | What it tells you |
|---|---|---|
| Channel | Paid search | Broad source of the visit |
| Channel Drilldown 1 | Platform within the channel | |
| Channel Drilldown 2 | Brand campaign | Campaign detail |
| Channel Drilldown 3 | Zoho | Further campaign detail |
| Landing Page | First page seen | Entry point content |
| Landing Page Group | Section of the site | Content section for roll-up reporting |
Illustrative example based on a branded paid search visit; actual values depend on UTM parameters used.
Frequently asked questions
What needs to be added to a form before attribution data can reach Braintree?
Add hidden fields for channel, three channel drilldowns, landing page and landing page group to the signup form. A small website snippet then determines the visit source, stores it in a browser cookie, and fills those fields when the form is submitted so the values travel with the signup into Braintree.
What is the difference between channel data and landing page data?
Channel answers how the visitor arrived, such as paid search or organic search, with drilldowns for the platform and campaign detail. Landing page and landing page group show which page the visitor first saw and which section of the site that page belongs to, such as a blog.
Which billing metrics can be broken down by channel or campaign?
Once the fields are present in Braintree, reports can be grouped by channel or campaign for new trials, trial-to-customer conversion, new customers, new MRR and ARR, ARPU, lifetime value, customer churn and MRR churn. The same grouping can be applied to landing page or landing page group to compare content sections and individual pages.
What if someone signs up with Google or Facebook instead of using a form?
Use a small script that reads the stored cookie values and passes them onward at signup. That route suits signups completed through Google or Facebook account options, where the person may create an account without completing the standard form.