Carry Marketing Attribution Data into Agile CRM
Agile CRM holds the lead and the opportunity; the question this page answers is how the marketing context that produced that lead gets attached to it.
The approach described here is form-based: hidden fields on your lead forms receive attribution values, and those values travel into Agile CRM when the form is submitted. This page explains the mechanism, the field groups involved, the compatibility conditions, and a short readiness check you can run before committing to a setup.
How the handoff works
The mechanism has four stages. First, hidden fields are added to the lead form. Second, a script fills those fields with the visitor's marketing context. Third, the form submission carries the values into Agile CRM. Fourth, those values become reportable dimensions on leads and, in turn, opportunities.
The important consequence: the form is the transport. If a form cannot carry hidden fields, the attribution values have nowhere to land, regardless of what the CRM can store.
What the two field groups contain
Channel data identifies the source type — for example Paid Search, Paid Social, or Organic Search — and, where the channel supports it, deeper detail such as campaign, ad group, and keyword for paid search.
Landing page data records the first page the lead saw on your site, plus a page category such as Blog. The supplied example of a first page is a blog article URL, which illustrates that the landing page is the entry point, not necessarily the conversion page.
A useful way to think about the split: channel data answers "what brought them," landing page data answers "where they first arrived." Both are attached to the lead so that later revenue can be grouped by either dimension.
Compatibility: what must be true on your side
Two form situations are covered. If you use a third-party form tool that passes leads into Agile CRM, the tool needs to support hidden fields. If you use custom-built forms, a developer needs to add the hidden fields to the markup.
In both cases the test is the same: can the form carry additional named fields through to the CRM record? If yes, attribution values can be populated. If no, the setup cannot proceed until the form is changed.
Readiness checklist before you start
Run these checks in order; the first failure stops the chain.
- Identify every lead form that feeds Agile CRM, including third-party and custom forms.
- Confirm each form can accept hidden fields and that those fields survive submission into the CRM record.
- Confirm the CRM fields that will receive channel, campaign, ad, keyword, landing page URL, and page category exist and are mapped.
- Confirm reporting can group by those fields on both leads and opportunities.
- Only then enable the attribution script on the pages that host the forms.
Three different failures look alike
When attribution data is missing from Agile CRM, the cause is usually one of three distinct problems, and each has a different fix.
Missing hidden field: the form never carried the value, so nothing arrived. Fix the form. Missing attribution value: the hidden field existed but was empty because the visitor had no recognizable marketing context. This is a data-coverage issue, not a transport issue. Missing CRM mapping: the value arrived but was not written to a reportable field. Fix the field mapping and reporting configuration.
Separating these three before troubleshooting saves time, because only the first and third are configuration problems on your side.
Worked example: a blog entry point
Suppose a visitor first lands on a blog article, then later returns and submits a demo form. The landing page field records the blog article as the first page seen, and the page category records Blog. The channel field records how that first visit was sourced. When the form is submitted, those values travel into the Agile CRM lead.
Later, when that lead becomes an opportunity and closes, revenue can be grouped by channel and by landing page category. The blog article is credited as the entry point even though the conversion happened on the demo form — which is the point of capturing the first page separately from the conversion page.
Frequently asked questions
Do I need hidden fields on my forms for this to work?
Yes. The attribution values are carried by hidden fields on the lead form. If a form cannot accept hidden fields, the values cannot be passed into Agile CRM through that form.
Does this work with third-party form tools?
It can, provided the third-party tool supports hidden fields and passes them through to Agile CRM on submission. The form tool is the transport, so its hidden-field support is the deciding factor.
What about custom-built forms?
A developer needs to add the hidden fields to the form markup. Once the fields exist and are mapped into Agile CRM, the same attribution values can be populated.
What attribution data ends up on the lead?
Channel data (channel type plus deeper detail such as campaign, ad group, and keyword for paid search) and landing page data (the first page seen plus a page category such as Blog).
Can I report on leads, customers, and revenue by channel?
The attribution values are stored on the lead, so reports can group leads, customers, and revenue by channel, campaign, ad, and landing page dimensions — subject to how your Agile CRM reporting is configured.