Skip to content

Track Instagram Ads leads in Webflow forms

You can connect Instagram advertising to Webflow enquiries by tagging each ad destination, storing the visitor's origin, and writing that origin into hidden form fields at submission. The result is a lead record that shows the campaign, ad set and ad behind the enquiry, rather than only a visit count.

Why visits alone do not prove lead value

Google Analytics and similar tools can show visits, but a visit is not a lead. To count enquiries by advertising origin, the origin must travel with the submission itself. That means capturing source data when the visitor arrives, keeping it available during the visit, and attaching it to the form record when the visitor submits.

Four-step setup checklist

Use this sequence as a pre-launch checklist:

  • Tag every Instagram ad URL so campaign, ad set and ad are distinguishable.
  • Install the attribution snippet on the site.
  • Add hidden fields for Channel, Channel Drilldown 1, Channel Drilldown 2, Channel Drilldown 3 and Channel Drilldown 4.
  • In Webflow, add the fields through an Embed block using the supplied help code.
  • Submit a test form from a tagged URL and confirm the hidden values appear in the submission.
  • Check the same values in the Forms area, notification email, CRM or spreadsheet destination you plan to use.

Tag ad URLs with a consistent UTM convention

UTM parameters are additional URL text that tells analytics and attribution tools where a visitor came from. A practical Instagram convention is to use Paid Social for medium, Instagram for source, the campaign name for campaign, the ad set name for term, and the specific ad for content. The exact values are your choice, but consistency matters because those values become the labels in later reports.

How origin data reaches the form record

After installation, the attribution tool watches incoming visits and categorises them into channels such as Paid Social, Paid Search and Organic Search. It stores that categorisation in a cookie. When a visitor completes a form, the stored origin is written into the hidden fields, and Webflow captures those values with the visible answers such as name, email or phone.

What the captured record can show

Two kinds of detail are useful. Channel data explains how the lead found the site and how far the drilldown goes: for example, Paid Social, then Instagram, then a named campaign, then the ad creative. Landing page data records the first page visited and its category, such as a blog path, so you can compare lead volume by content section and by individual page.

Worked example: a pool company sends a click from an Instagram ad to a blog article. The captured record could show Paid Social as the channel, Instagram as the first drilldown, the campaign name as the second, and the ad creative as the third, alongside the article URL and its blog category. That lets the team separate the effect of the ad from the effect of the landing content.

Three reports to run after capture

Once submissions carry origin fields, three reports answer different budget questions:

  • Leads by channel: compare monthly lead volume across Paid Social, Paid Search, Organic Search and other channels to see where enquiries actually come from.
  • Leads by network: separate Instagram from other Meta-owned placements such as Facebook, Messenger and WhatsApp when the same ad platform serves them.
  • Leads by campaign: compare Instagram campaigns month by month to identify which campaigns produce the most leads.

A common failure distinction is worth checking before changing budget: high spend on Instagram with most leads from Organic Search points to a channel-mix question, while strong Instagram leads concentrated in one campaign points to a campaign-scaling question. The report you choose should match the decision you are about to make.

Before you start

The source presents the workflow as a way to capture the exact campaign, ad set or ad behind each lead and send that data to a CRM or other tools for return-on-investment reporting. Trial length and setup time are owner-confirmed terms: {{OWNER_TRIAL_DURATION}}. Confirm the supported attribution tool and code before starting: {{OWNER_ATTRIBUTION_TOOL}}.

Frequently asked questions

Why is visitor traffic not enough to judge Instagram Ads?

Visitor counts alone do not show which campaign, ad set or ad produced a form submission. Capturing the source alongside the lead's name, email and other form answers lets you count leads by origin in Webflow, a CRM or a spreadsheet.

What if someone lands on one page and submits a form on another?

The source describes a cookie-based approach: the attribution tool stores where the visitor came from, so the origin data can still be written into a form even if the submission happens on a different page from the landing page.

What happens if UTM values are inconsistent across ads?

The source says the tool is designed to tolerate inconsistent UTM values, such as different spellings for the same source, and still assign the lead to the correct channel.