Braintree Marketing Attribution: Channel & Landing Page Data
Braintree holds customer and payment records, but it does not know which marketing channel or landing page brought a person in.
This guide describes a documented integration pattern: an attribution tool captures marketing data on your lead forms and passes it into Braintree, so you can report on the channels, campaigns, ads and landing pages behind leads, customers and revenue. The workflow below reflects how the integration is documented to work; confirm current product behavior with the tool provider before relying on it.
How attribution data reaches Braintree
The workflow has three stages. First, you add hidden fields to the lead forms on your site. Second, the attribution tool is documented to monitor the marketing channels your leads arrive from and write the relevant values into those hidden fields. Third, when a visitor submits a form, the attribution information is passed into Braintree along with the rest of the submission.
The fields are not filled by the visitor. They are populated by the attribution tool and then carried through the form submission into the Braintree record, which is what makes channel-level reporting possible later.
Setup checklist
Use this checklist to confirm each stage is in place before you rely on the data:
- Hidden fields exist on every lead form you want to track.
- The hidden field names match the attribution fields the tool is configured to write.
- The attribution tool is loaded on the pages where those forms appear.
- A test submission carries channel, campaign and landing page values into Braintree.
- Reports in Braintree or your reporting layer group by the attribution fields you care about.
If a Braintree record has no attribution values, check the hidden fields first. If the fields exist but values are blank, check whether the attribution tool was active on the page where the form was submitted. These are different failures and need different fixes.
What information you get
The attribution data falls into two groups: channel data and landing page data. Used together, they support reporting that shows which channels, campaigns, ads and pages are producing leads, customers and revenue.
Channel data
The channel is captured automatically, for example Paid Search, Paid Social or Organic Search. For each channel, further detail is captured as well. For Paid Search, that includes the campaign, ad group and keyword. This is the level of detail you need to compare performance between campaigns and between individual ads or keywords within a campaign. The tool is documented to capture this automatically; confirm current behavior with the provider.
Landing page data
The entry point recorded is the first page a lead views on your site, and the page's category is stored alongside it. The tool is documented to capture this automatically; confirm current behavior with the provider. Take a visitor whose first page is a pricing comparison article at a URL like example.com/guides/pricing-comparison: the stored category would be Guides. Keeping both the URL and the category means you can report at either level — individual pages for detailed analysis, or categories for a higher-level view of which content types bring people in.
Field map: what each record can carry
The table below summarises the attribution fields and what each one tells you. It is a reader aid, not a replacement for the field names in your own form and Braintree configuration.
| Field family | Example values | What it answers |
|---|---|---|
| Channel | Paid Search, Paid Social, Organic Search | Which broad acquisition route brought the lead in? |
| Campaign detail | Campaign, ad group, keyword (for Paid Search) | Which specific campaign or ad drove the lead? |
| Landing page URL | First page the lead saw, e.g. a blog article URL | Which page was the entry point? |
| Landing page category | Blog, and other page types | Which content type brought the lead in? |
Use the channel and campaign fields for acquisition reporting, and the landing page fields for content and page-level reporting. Combining them shows which pages perform within which channels.
Worked example
Suppose a visitor first lands on a blog article about licensing music, then later submits a lead form. The record passed into Braintree can carry the first page URL and the page category Blog, alongside the channel and, where relevant, the campaign, ad group and keyword. When you later report on that record, you can see both the acquisition route and the content entry point, rather than only the form submission itself.
This is useful when a single campaign sends traffic to several pages. If one campaign's leads mostly enter through blog articles and another's through product pages, the landing page fields make that difference visible in reporting.
Building reports from the captured data
Once the attribution fields are in Braintree, you can build reports that group leads, customers and revenue by channel, campaign, ad or landing page. The value comes from joining the marketing source to the commercial outcome: not just how many leads arrived, but which channels and pages produced customers and revenue.
Frequently asked questions
Do I need to add hidden fields to my forms?
Yes. Hidden fields on your lead forms give the attribution tool a place to write the marketing channel attribution data. Without them, the attribution values have nowhere to go before the form is submitted to Braintree.
What attribution data can be passed into Braintree?
Channel-level data such as channel, campaign name and ad name, plus landing page data: the first page the lead saw and the category of that page. For Paid Search, campaign, ad group and keyword detail is also captured.
Which landing page is recorded?
The first page the lead sees on your site is the one captured, together with that page's category. Later pages visited before the form submission are not the recorded entry point.
Why might a Braintree record have blank attribution values?
Check two things separately. First, confirm the hidden fields exist on the form. Second, confirm the attribution tool was active on the page where the form was submitted. Missing fields and missing data are different problems with different fixes.