Request an Attribution Demo
A short demo call is the fastest way to see whether a lead-source attribution tool fits how your team already captures and stores leads.
This page explains what the request form asks for, which fields are visible to you, which are hidden tracking fields, and how to get the most from the walkthrough.
What the demo is for
The walkthrough is intended to show how a lead-source attribution tool records where leads come from and passes that information into a CRM. Use the call to check whether the captured channel, landing page and lead-source details match the fields your sales and marketing teams actually report on. Bring a real example of a lead journey so the discussion stays concrete rather than theoretical.
What the request form asks for
The form collects a small set of contact and qualification details. Visible fields include First Name, Last Name, Work Email, Company Name and a lead-volume selector. The lead-volume selector offers four bands: 0 - 100, 100 - 500, 500 - 1,000 and 1,000+. A hidden Email field is present for validation purposes and should be left unchanged. The submit control is labelled Get A Demo.
Hidden tracking fields on the form
Several fields are hidden when viewing the form and are populated automatically with tracking placeholders. These include Channel Drilldown 1, Channel Drilldown 2, Channel Drilldown 3, Landing Page URL, Landing Page Group, Lead Source, Lead Sub Source, Lead Sub Source Description and Testing Data. In the captured form, Lead Source is pre-filled with Marketing Leads, Lead Sub Source with Demo Request and Lead Sub Source Description with Get Started. These hidden fields are how the form itself can carry attribution context alongside the contact details you type in.
Pre-demo checklist
Before the call, gather the following so the walkthrough can focus on your setup:
- Your current CRM and the lead or contact fields your team uses.
- One or two example landing pages and the campaign links that point to them.
- The lead-volume band that best matches your monthly intake.
- The channel and sub-channel names your marketing reports already use.
- Any open questions about how attribution data should appear on a CRM record.
Worked example: what a demo request can carry
Suppose a visitor arrives from a paid social campaign, lands on a pricing page and then submits the demo form. The hidden fields can carry the channel drilldown values, the landing page URL and the landing page group alongside the visible contact details. When that submission reaches a CRM, the sales team can see not only the person's name and company but also the channel and page that brought them in. The value of the demo is in checking whether that same context survives into the fields your team already reports on.
How to read the form fields
The visible fields are the ones you fill in. The hidden fields are populated by the page and are not intended for manual entry. If you are reviewing the form before submitting, focus on the contact details and the lead-volume band; the tracking fields will be filled automatically. The validation field labelled Email should be left unchanged.
Frequently asked questions
What information do I need to provide to request a demo?
The visible form asks for First Name, Last Name, Work Email, Company Name and a monthly lead-volume band. The lead-volume options are 0 - 100, 100 - 500, 500 - 1,000 and 1,000+.
Why are there hidden fields on the demo form?
The hidden fields carry attribution context such as channel drilldowns, landing page URL, landing page group and lead source details. They are populated automatically and are not meant to be filled in by hand.
What does the Email field with the validation note mean?
It is a validation field that should be left unchanged. The Work Email field is the one used for contact.
What happens after I submit the form?
The form is a request for a walkthrough. The next step is a conversation with the team to see how the tool fits your lead capture and CRM setup. Specific scheduling and follow-up arrangements are confirmed by the team handling the request.