How to capture UTM parameters in Instapage and pass them to your CRM
Instapage makes it quick to publish polished landing pages for Google, Facebook and other ad campaigns. The harder question comes afterwards: which of those campaigns actually produced leads and customers, and at what return? Answering it means the campaign data has to travel with the lead. This guide walks through adding UTM parameters to your ads, wiring six hidden fields into your Instapage form, filling those fields automatically, and pushing the result into your CRM so you can report on it. It also explains where the native Instapage approach stops and what a cookie-based attribution layer adds.
Why campaign data needs to reach the CRM
A landing page builder tells you that a form was submitted. It does not, on its own, tell you that the submission came from a paid search ad, an organic social post or a direct visit. When UTM parameters are captured alongside the lead's name, email and company and then passed into the CRM, reporting becomes possible on questions such as how many leads a Facebook campaign produced, how many customers came from Google Ads, or how much revenue organic search generated.
That is the outcome to aim for: every lead record carrying a reliable description of how the person arrived, stored where sales and marketing already look.
Step 1: tag every campaign, not just the paid ones
Tracking starts upstream. Before anything on the landing page can be captured, the destination URLs need UTM parameters attached. Tag all active campaigns and ads — paid social on Instagram, Facebook, Twitter and LinkedIn, plus search ads on Bing and Google. If you also run email campaigns or advertisements in trade publications, tag those too, otherwise those leads will arrive with nothing to attribute.
A useful habit: treat an untagged link as a bug. A single untagged ad quietly becomes a permanent 'unknown' bucket in your CRM reports.
Step 2: add six hidden fields to the Instapage form
Next, edit the lead capture forms — the ones collecting visitor details — and add hidden fields. Hidden fields are invisible to visitors but travel with the submission, giving an attribution tool somewhere to write its values. The setup assumes you are using Instapage's built-in form tool: in the landing page editor, select the form, choose 'Add Field' and pick the 'Hidden' option.
Add six of them, named exactly as follows so downstream mapping stays predictable:
- Channel
- Channel Drilldown 1
- Channel Drilldown 2
- Channel Drilldown 3
- Landing Page
- Landing Page Group
Keep the names consistent across every form. A field called 'Channel' on one page and 'channel' on another creates exactly the reporting mess this setup is meant to prevent.
Step 3: let the attribution layer fill the fields
With the fields in place, the attribution script monitors how each visitor reached the page — including any UTM parameters they arrived with — and writes the results into the hidden fields. It does this by reading technical signals about the visit (UTM parameters, referrer, device and similar) and sorting the visitor into a channel such as Paid Search, Organic Search or Paid Social. That classification is stored in a cookie in the visitor's browser, and when a form is submitted the stored values populate the hidden fields.
A worked example makes the output concrete. Imagine a marketer at a streaming service running a paid Google ad for a 'Stream movies online' search. A visitor clicks the ad, lands on the campaign page and submits a form. The hidden fields might end up holding:
- Channel = Paid Search
- Channel Drilldown 1 = Google
- Channel Drilldown 2 = Movies Campaign
- Channel Drilldown 3 = Free Trial Ad
Landing page data is captured too, for example:
- Landing Page = www.netflix.com/features/movies
- Landing Page Group = Features
The exact values depend on the UTM parameters you used behind the ad; the structure is what matters.
Step 4: move the data into your CRM
On submission, Instapage captures the visitor's details — name, phone, email and so on — together with the values written into the hidden fields. From there, Instapage's native integrations or Zapier can carry those values into a wide range of destinations, including Salesforce, HubSpot, Pipedrive and Zoho CRM. Once the data sits in the CRM, reports can answer which campaigns produced leads, which produced customers and where revenue originated.
Raw UTM capture vs a cookie-based attribution layer
Instapage offers dynamic text replacement as a way to pull raw UTM parameters into forms, so it is fair to ask why an additional layer would be needed. Four differences matter when you are deciding.
All traffic, not only tagged traffic. Dynamic text replacement only has data for visitors who arrive with UTM parameters attached — typically because an ad carried them. Visitors from organic social, organic search, direct or referral arrive without them. A cookie-based layer classifies those visits too, so CRM reports can identify the source of every lead rather than only paid ones.
Memory across pages. Dynamic text replacement needs the UTM parameters on the same page where the form is completed. If a visitor clicks a Google ad, lands on the campaign page, then clicks 'Contact Us', moves to another page and submits a form there, the parameters are gone. Storing the classification in a cookie means the values survive navigation — and even a visitor leaving and returning later — so the CRM still receives them.
Cleaner values. Raw capture preserves whatever you typed. If some Twitter campaigns use UTM Source=twitter.com, others use UTM Source=twitter and others use UTM Source=tw, the CRM shows three separate sources and the real totals are hard to see. A layer that accounts for capitalization and similar discrepancies assigns those leads to one channel instead.
Landing page data. Beyond UTM parameters, the layer records which landing page was involved and a landing page category, so you can compare pages on leads, customers and revenue rather than guessing which pages convert well and which only generate poor-fit leads.
A setup checklist before you go live
Work through these checks in order; each one catches a failure that is expensive to diagnose later.
- Every active ad and campaign URL carries UTM parameters, including email and print placements.
- All six hidden fields exist on every lead form, spelled and capitalized identically.
- The attribution script is present on the pages where visitors land, not only on the form page.
- A test submission from a tagged ad shows the expected Channel and Drilldown values in the CRM record.
- A test submission that navigates from the ad landing page to a second page with the form still carries the original source.
- A visit with no UTM parameters at all still produces a sensible channel rather than a blank field.
- CRM picklists or field mappings accept the channel values without truncation.
If a test fails, identify which of three distinct problems you have: no values at all (script or field mapping missing), values lost after navigation (no cookie-based memory), or values split across several spellings (raw capture without normalization). Each has a different fix.
What the attribution layer is
The layer is a small piece of code, comparable in placement to a Google Analytics tag, added to your Instapage landing pages. On each visit it inspects the technical signals behind the arrival, classifies the visitor into a channel, and stores that classification in a browser cookie. When a form is completed, it writes the stored UTM and attribution values into the hidden fields, and those values flow onward to the CRM and other tools.
Where to go next
Once the fields are wired and tested, the remaining work is reporting: build CRM views that group leads and revenue by Channel and Channel Drilldown, and review landing page performance using the Landing Page and Landing Page Group fields. For CRM-specific delivery steps, see the integration guides for Salesforce, HubSpot, Pipedrive and Zoho CRM.
| Hidden field | What it holds | Example value |
|---|---|---|
| Channel | Broad channel the visit was classified into | Paid Search |
| Channel Drilldown 1 | First level below the channel | |
| Channel Drilldown 2 | Second level, typically the campaign | Movies Campaign |
| Channel Drilldown 3 | Third level, typically the ad or variant | Free Trial Ad |
| Landing Page | The page the visitor first landed on | www.netflix.com/features/movies |
| Landing Page Group | Category the landing page belongs to | Features |
Example values come from a worked illustration of a paid search visit; your actual values depend on the UTM parameters used behind each ad.
| Consideration | Raw UTM capture (dynamic text replacement) | Cookie-based attribution layer |
|---|---|---|
| Visitors covered | Only those arriving with UTM parameters attached | All visitors, including organic, direct and referral |
| Multi-page journeys | Parameters must be on the same page as the form | Stored in a cookie, so values survive navigation and return visits |
| Value consistency | Whatever was typed is kept, so variants split into separate sources | Capitalization and similar discrepancies are reconciled |
| Landing page data | Not the focus of the feature | Landing page and landing page group captured alongside UTMs |
Comparison reflects the behavior described for Instapage's dynamic text replacement at the time of writing; confirm current feature behavior in Instapage before relying on it.
Frequently asked questions
Do I need UTM parameters on every ad, or only the paid ones?
Tag all active campaigns and ads, including paid social and search, and also email campaigns and trade publication ads if you run them. Untagged links arrive with nothing to attribute, so those leads end up in an unknown bucket.
Why does a lead lose its source when the form is on a different page?
Raw UTM capture depends on the parameters being present on the page where the form is submitted. If a visitor lands on a tagged campaign page and then navigates to another page to complete a form, the parameters are no longer there. Storing the classification in a cookie keeps it available across pages and return visits.
My CRM shows twitter.com, twitter and tw as three sources. What went wrong?
Nothing broke — raw capture simply preserves exactly what was typed into each UTM Source value. A layer that reconciles capitalization and similar variants assigns those leads to a single channel so totals add up.
Can the captured data go somewhere other than a CRM?
Yes. Instapage's native integrations or Zapier can forward the values to a broad range of destinations, including Salesforce, HubSpot, Pipedrive and Zoho CRM.
What should I check first if a test submission shows blank hidden fields?
Confirm the six hidden fields exist with identical names on the form, that the attribution script is present on the landing pages, and that the CRM field mapping accepts the values. Blank fields are a different problem from values that disappear after navigation.