Lead Insights for Statamic: Practical Lead Attribution with UTMs, Referrer & Landing Page
Most websites can collect inquiries, but many teams still can’t answer a simple question: which channels and campaigns consistently generate leads—not just traffic. Analytics tools can show sessions and page views, but attribution often gets lost between marketing reports and the actual form submissions your sales or delivery team works with. Lead attribution becomes truly useful when it’s attached directly to each lead, so you can review outcomes by source, campaign, form, and landing page without building a complex tracking stack.
The gap between “traffic analytics” and “lead reality”
In a typical B2B setup, marketing and sales look at different worlds. Marketing has dashboards full of sessions, clicks, and engagement charts. Sales (or the delivery team) sees a short message, an email address, and maybe a phone number. The missing piece is the context that explains how a person arrived at the moment of submitting the form.
That context is usually attribution: what campaign brought the visitor, what channel they came from, which page they entered on, and whether there was a referrer (for example, a partner site or a directory listing). When you don’t have this, decision-making becomes guesswork. Teams debate budgets and landing pages based on assumptions because it’s hard to connect “source data” to actual leads.
What “lead attribution” means in practice
Lead attribution is not about tracking every move a visitor makes. For many businesses, the most valuable signals are the simplest ones:
- UTM parameters (utm_source, utm_medium, utm_campaign, utm_term, utm_content) to understand campaign performance.
- Referrer to capture where the visitor came from when UTMs are missing (or to validate partner/directory traffic).
- Landing URL to see which entry pages actually produce submissions.
These data points are small, but they answer real questions: “Which campaign drives qualified inquiries?” “Which channel produces leads at all?” “Which landing pages are not just visited, but actually convert?”
Where Lead Insights fits: attribution attached to Statamic form submissions
Lead Insights for Statamic focuses on making attribution usable by attaching it directly to the object that matters most: the form submission. Instead of keeping attribution only in external analytics dashboards, it stores attribution data alongside each Statamic submission under a dedicated field. This makes it possible to review and aggregate lead outcomes inside Statamic’s Control Panel.
Add-on link: https://statamic.com/addons/isapp/lead-insights
How the workflow works (without turning your site into a tracking project)
The approach is deliberately simple and operational:
- Capture attribution on arrival: when a visitor lands on the site with UTMs (or has a meaningful referrer), the attribution data is stored in a first-party cookie. This allows the attribution context to remain available when the visitor navigates to a form later.
- Attach attribution at the moment of conversion: when the visitor submits a Statamic form, the stored attribution payload is appended to the submission.
This avoids the common situation where attribution is “somewhere in analytics,” while the team processing leads can’t access it quickly. With this model, attribution becomes part of the lead record itself.
Consent and privacy: practical EU/UK-friendly behavior
For Western Europe and the UK, consent-aware behavior isn’t a nice-to-have. If you require consent before setting cookies, the attribution layer must respect that. Lead Insights can be configured so attribution is stored only when consent is present.
There is also an optional “minimal fallback” behavior: if consent is not present, you can still store only the landing URL with the submission. That gives you a lightweight view of which entry pages tend to result in inquiries, while avoiding broader attribution storage without consent. Many teams find this useful because it preserves operational insight without over-collecting data.
What you can answer once attribution is attached to leads
When attribution is stored with submissions, the conversation changes. Instead of asking, “How much traffic did this campaign get?” you can ask, “How many inquiries did it generate?” That distinction matters because traffic is not the business outcome—submissions are.
1) Which channels generate leads consistently
A channel can look “successful” in traffic reports while producing very few inquiries. Conversely, a smaller channel may generate fewer visits but a higher proportion of submissions. With lead attribution, you can measure channels by lead outcomes and stop optimizing for vanity metrics.
2) Which campaigns are actually worth repeating
UTM campaigns are only valuable if you can reliably review results. Once campaign names are stored with submissions, you can compare campaigns across weeks or months and build a repeatable playbook: campaigns that consistently produce leads are scaled; campaigns that bring only low-intent traffic are deprioritized.
3) How different forms perform (and how they are fed)
Many sites have more than one form: a general contact form, a “request a quote” form, a “book a call” form, or an audit request form. Without attribution, you see form counts but not the context behind them. With attribution attached to each submission, you can observe patterns like “paid search drives mostly quote requests,” while “referral traffic drives call bookings,” which can influence how you structure CTAs and follow-up.
4) Which landing pages produce submissions (not just visits)
Landing URL is an underrated metric. Teams often invest heavily in pages that get traffic, while the pages that quietly produce inquiries remain under-optimized. Seeing which entry pages lead to submissions helps you prioritize improvements: clarify messaging, strengthen proof (case studies, process, guarantees), and refine CTAs on the pages that actually matter.
What this is not: setting expectations correctly
To avoid disappointment, it helps to define the scope. Lead Insights is an attribution layer, not a full behavioral analytics tool. It will not tell you scroll depth, micro-click patterns, or every page view a visitor made. If you need that, you’ll want a different class of tools.
What it does provide is the attribution context that a business can act on quickly: UTMs, referrer, and landing URL attached to the lead itself. For many teams, this is the 80/20 that moves decisions from opinion to evidence.
Operational best practices: getting value quickly
The fastest way to benefit is not “install and forget.” A small amount of process makes attribution dramatically more useful:
- Define a UTM naming standard: agree on a limited set of allowed values for utm_source and utm_medium, plus a clear campaign naming convention. This prevents reporting fragmentation (for example, “linkedin” vs “LinkedIn” vs “li”).
- Decide how consent will work: if consent gating is required, define which consent cookie indicates permission to store attribution and keep it consistent with your CMP setup.
- Review attribution weekly: in the first two weeks, you will often discover broken UTMs, inconsistent campaign naming, or unexpected referrers. Fixing those early improves the reliability of every future report.
After this initial cleanup, the reporting becomes stable enough that teams can confidently compare channels and campaigns over time.
Why this matters for PMs and delivery teams, not only marketing
Attribution data is often treated as a marketing-only concern, but in practice it affects delivery and sales workflows. When a lead is clearly attributed to a specific campaign or landing page, it’s easier to understand the promise that brought the person in. That reduces misalignment: the team can align discovery questions and proposals with the messaging that attracted the lead in the first place.
For agencies and product teams, this also helps evaluate whether the website structure supports the business. If certain landing pages never produce submissions, it’s a signal to revisit positioning, proof, or CTA placement—without needing a full redesign cycle.
Conclusion
Lead attribution is most useful when it is attached to the lead itself. Lead Insights for Statamic captures practical attribution signals—UTM parameters, referrer, and landing URL (with consent-aware behavior)—and stores them with form submissions so you can analyze lead outcomes by channel, campaign, form, and entry page inside Statamic.
If your goal is to understand where inquiries come from and make marketing and website decisions based on lead outcomes rather than traffic metrics, this approach is a straightforward, operationally friendly next step.
Add-on link: https://statamic.com/addons/isapp/lead-insights
The gap between “traffic analytics” and “lead reality”
In a typical B2B setup, marketing and sales look at different worlds. Marketing has dashboards full of sessions, clicks, and engagement charts. Sales (or the delivery team) sees a short message, an email address, and maybe a phone number. The missing piece is the context that explains how a person arrived at the moment of submitting the form.
That context is usually attribution: what campaign brought the visitor, what channel they came from, which page they entered on, and whether there was a referrer (for example, a partner site or a directory listing). When you don’t have this, decision-making becomes guesswork. Teams debate budgets and landing pages based on assumptions because it’s hard to connect “source data” to actual leads.
What “lead attribution” means in practice
Lead attribution is not about tracking every move a visitor makes. For many businesses, the most valuable signals are the simplest ones:
- UTM parameters (utm_source, utm_medium, utm_campaign, utm_term, utm_content) to understand campaign performance.
- Referrer to capture where the visitor came from when UTMs are missing (or to validate partner/directory traffic).
- Landing URL to see which entry pages actually produce submissions.
These data points are small, but they answer real questions: “Which campaign drives qualified inquiries?” “Which channel produces leads at all?” “Which landing pages are not just visited, but actually convert?”
Where Lead Insights fits: attribution attached to Statamic form submissions
Lead Insights for Statamic focuses on making attribution usable by attaching it directly to the object that matters most: the form submission. Instead of keeping attribution only in external analytics dashboards, it stores attribution data alongside each Statamic submission under a dedicated field. This makes it possible to review and aggregate lead outcomes inside Statamic’s Control Panel.
Add-on link: https://statamic.com/addons/isapp/lead-insights
How the workflow works (without turning your site into a tracking project)
The approach is deliberately simple and operational:
- Capture attribution on arrival: when a visitor lands on the site with UTMs (or has a meaningful referrer), the attribution data is stored in a first-party cookie. This allows the attribution context to remain available when the visitor navigates to a form later.
- Attach attribution at the moment of conversion: when the visitor submits a Statamic form, the stored attribution payload is appended to the submission.
This avoids the common situation where attribution is “somewhere in analytics,” while the team processing leads can’t access it quickly. With this model, attribution becomes part of the lead record itself.
Consent and privacy: practical EU/UK-friendly behavior
For Western Europe and the UK, consent-aware behavior isn’t a nice-to-have. If you require consent before setting cookies, the attribution layer must respect that. Lead Insights can be configured so attribution is stored only when consent is present.
There is also an optional “minimal fallback” behavior: if consent is not present, you can still store only the landing URL with the submission. That gives you a lightweight view of which entry pages tend to result in inquiries, while avoiding broader attribution storage without consent. Many teams find this useful because it preserves operational insight without over-collecting data.
What you can answer once attribution is attached to leads
When attribution is stored with submissions, the conversation changes. Instead of asking, “How much traffic did this campaign get?” you can ask, “How many inquiries did it generate?” That distinction matters because traffic is not the business outcome—submissions are.
1) Which channels generate leads consistently
A channel can look “successful” in traffic reports while producing very few inquiries. Conversely, a smaller channel may generate fewer visits but a higher proportion of submissions. With lead attribution, you can measure channels by lead outcomes and stop optimizing for vanity metrics.
2) Which campaigns are actually worth repeating
UTM campaigns are only valuable if you can reliably review results. Once campaign names are stored with submissions, you can compare campaigns across weeks or months and build a repeatable playbook: campaigns that consistently produce leads are scaled; campaigns that bring only low-intent traffic are deprioritized.
3) How different forms perform (and how they are fed)
Many sites have more than one form: a general contact form, a “request a quote” form, a “book a call” form, or an audit request form. Without attribution, you see form counts but not the context behind them. With attribution attached to each submission, you can observe patterns like “paid search drives mostly quote requests,” while “referral traffic drives call bookings,” which can influence how you structure CTAs and follow-up.
4) Which landing pages produce submissions (not just visits)
Landing URL is an underrated metric. Teams often invest heavily in pages that get traffic, while the pages that quietly produce inquiries remain under-optimized. Seeing which entry pages lead to submissions helps you prioritize improvements: clarify messaging, strengthen proof (case studies, process, guarantees), and refine CTAs on the pages that actually matter.
What this is not: setting expectations correctly
To avoid disappointment, it helps to define the scope. Lead Insights is an attribution layer, not a full behavioral analytics tool. It will not tell you scroll depth, micro-click patterns, or every page view a visitor made. If you need that, you’ll want a different class of tools.
What it does provide is the attribution context that a business can act on quickly: UTMs, referrer, and landing URL attached to the lead itself. For many teams, this is the 80/20 that moves decisions from opinion to evidence.
Operational best practices: getting value quickly
The fastest way to benefit is not “install and forget.” A small amount of process makes attribution dramatically more useful:
- Define a UTM naming standard: agree on a limited set of allowed values for utm_source and utm_medium, plus a clear campaign naming convention. This prevents reporting fragmentation (for example, “linkedin” vs “LinkedIn” vs “li”).
- Decide how consent will work: if consent gating is required, define which consent cookie indicates permission to store attribution and keep it consistent with your CMP setup.
- Review attribution weekly: in the first two weeks, you will often discover broken UTMs, inconsistent campaign naming, or unexpected referrers. Fixing those early improves the reliability of every future report.
After this initial cleanup, the reporting becomes stable enough that teams can confidently compare channels and campaigns over time.
Why this matters for PMs and delivery teams, not only marketing
Attribution data is often treated as a marketing-only concern, but in practice it affects delivery and sales workflows. When a lead is clearly attributed to a specific campaign or landing page, it’s easier to understand the promise that brought the person in. That reduces misalignment: the team can align discovery questions and proposals with the messaging that attracted the lead in the first place.
For agencies and product teams, this also helps evaluate whether the website structure supports the business. If certain landing pages never produce submissions, it’s a signal to revisit positioning, proof, or CTA placement—without needing a full redesign cycle.
Conclusion
Lead attribution is most useful when it is attached to the lead itself. Lead Insights for Statamic captures practical attribution signals—UTM parameters, referrer, and landing URL (with consent-aware behavior)—and stores them with form submissions so you can analyze lead outcomes by channel, campaign, form, and entry page inside Statamic.
If your goal is to understand where inquiries come from and make marketing and website decisions based on lead outcomes rather than traffic metrics, this approach is a straightforward, operationally friendly next step.
Add-on link: https://statamic.com/addons/isapp/lead-insights
Get In Touch
Need help with Statamic?
We help teams build, improve, and maintain Statamic sites—performance, integrations, content architecture, and ongoing support.