Skip to content

Send channel and landing-page attribution data into Insightly

Marketing spend is hard to defend when you cannot say which sources produce leads and customers. If channel and landing-page context travelled with every form submission into Insightly, you could rank sources by leads, opportunities, closed-won deals and revenue instead of guessing. This guide covers the four-stage setup, the six hidden fields that carry the data, and the reporting questions the resulting records can answer.

How the capture layer works

A small script on your site observes each visit and notes signals such as UTM parameters, the referring site and the device used. From those signals it sorts the visit into a channel — paid social, organic search, organic social and similar — and writes the result to a cookie in that visitor's browser. Later, when the same person completes a lead form, the script reads the cookie and fills in hidden fields you placed on the form. The submission then carries the attribution values into Insightly alongside the contact details the visitor typed.

The four-stage setup at a glance

Stage one is preparing your forms with the right hidden fields. Stage two is letting the script populate them at submit time. Stage three is the handoff of those values into Insightly with the lead record. Stage four is turning the stored values into reports. Each stage depends on the one before it, so a gap early on will look like missing data later.

Stage 1: Prepare six hidden fields on each lead form

Every lead capture form needs these six fields: Channel, Channel Drilldown 1, Channel Drilldown 2, Channel Drilldown 3, Landing Page and Landing Page Group. Form builders such as Gravity Forms, Typeform and Jotform let you add hidden fields through their interface. On a hand-coded HTML form, declare each one as an input with type="hidden" so it submits without being shown to the visitor.

Stage 2: The script fills the fields at submit time

Because the script has been tracking the visit, it can complete the hidden fields the moment a form is submitted. The captured example uses Dropbox: someone clicks a brand ad in Google's search results and later fills in a form. Channel becomes Paid Search, Channel Drilldown 1 becomes Google, Channel Drilldown 2 becomes Brand Campaign and Channel Drilldown 3 becomes Dropbox. The same record also stores the first page viewed — dropbox.com/features/cloud-storage — and that page's group, features.

Stage 3: Values arrive in Insightly with the lead

On submission, the channel and landing-page values travel into your CRM together with whatever else the form collects, such as name, phone number and email address. From that point the attribution lives on the lead record rather than only in an analytics tool.

Stage 4: Build reports on leads, deals and revenue

With the values stored on records, reporting becomes a matter of grouping. You can compare channels by lead volume, count closed-won deals per channel, and calculate each channel's conversion rate to opportunity, among other measures.

The two questions the data answers

Attribution rests on two essentials. The first is origin: how did this person reach the site? Common answers are referral, paid social, organic search and paid search. The second is entry content: which page did they land on — a features page, a blog post, an ebook? The capture layer exists to record both so neither question is left to memory.

Channel values and their drilldowns

Channel records the broad source type, such as organic search, paid social or paid search. The drilldown fields add resolution within that type; for paid search, the captured detail includes keywords, ad group and campaign. Treat Channel as the grouping level for reporting and the drilldowns as the detail you filter on when a channel looks unusually strong or weak.

Landing page values and their groups

Landing Page stores the first page a lead saw, for example dropbox.com/blog/best-file-storage-tools, while Landing Page Group stores that page's category, such as blog. The pairing lets you report at either level: total leads produced by an entire section, or leads attributed to one specific article.

Three uses once the data is in place

Stored attribution supports three practical activities: channel reporting, more relevant sales follow-up, and content reporting. Each draws on the same six fields but asks a different question of them.

Channel reporting

Grouping leads by channel lets you ask, for a given campaign such as Facebook Ads: how many visitors did it produce, what share converted to opportunities, how many opportunities resulted, how much pipeline was created, how many deals closed won, how much revenue closed, and what the overall return was when spend is set against revenue. These reports can be assembled in Insightly's own report builder, placed on a dashboard, or produced in an analytics or business-intelligence tool connected to Insightly when you need more depth.

More relevant sales follow-up

Knowing the channel, the ad clicked and the first pages viewed gives a salesperson context before the first reply. In the captured Dropbox scenario, a rep can see the visitor arrived from a Google search about sharing large files. That suggests the prospect's priority, so the follow-up can lead with large-file sharing benefits and include case studies from customers with the same need. The reasoning is that a message aimed at the stated problem is more likely to convert than a generic one.

Content reporting

Because both the landing page and its group are stored, content performance can be reported at either level. Typical questions include how many visitors the blog received, which posts drew the most traffic, which posts turned visitors into paying customers, and what return the blog delivered.

Pre-flight checklist

Work through these before you rely on the numbers. Decide which forms capture leads and whether they are built with a form tool or hand-coded HTML. Confirm all six hidden fields exist on every one of those forms. Confirm the capture script runs on the pages where visitors first arrive, not only on the form page. Agree which reports you intend to build, since that determines which fields matter most. Finally, check that Insightly will accept the field values you plan to send.

Field map: origin versus content

The six fields divide cleanly in two. Channel, Channel Drilldown 1, Channel Drilldown 2 and Channel Drilldown 3 describe origin. Channel is the broad type, such as paid search, and each drilldown narrows it — Google, then Brand Campaign, then Dropbox in the captured example. Landing Page and Landing Page Group describe content: the first page seen and its category, such as features or blog. When a report looks wrong, check which half of the map the missing value belongs to.

Telling three failure modes apart

Missing attribution in Insightly usually has one of three causes, and they look alike from the report side. If the hidden fields were never added, there is nowhere for values to be written. If the capture script is not running or not storing a cookie, the fields exist but stay empty. If values are present on records yet nothing is reported, the capture worked and only the reporting step is outstanding. Check the form first, then the capture layer, then the reports.

Frequently asked questions

Which hidden fields do I need to add to my forms?

Six: Channel, Channel Drilldown 1, Channel Drilldown 2, Channel Drilldown 3, Landing Page and Landing Page Group. Add all six to every lead capture form so the attribution values have somewhere to be written.

How does the capture layer remember where a visitor came from?

It writes the visitor's channel and related details to a browser cookie. When that visitor submits a form, the stored values are used to complete the hidden fields.

What can I report on once the data is in Insightly?

Channel performance — leads, opportunities, pipeline, closed-won deals, revenue and return against spend — and content performance, including blog traffic, which posts convert visitors into customers, and blog return.

Can I use this with a hand-coded HTML form?

Yes. Declare each of the six fields as an input with type="hidden" so the values submit with the rest of the form.