Skip to content

Track Instagram Ads in WS Form

Website analytics can show that Instagram ads brought visitors to your site, but it rarely tells you which of those visitors became leads. This guide shows how to attach Instagram ad details to every WS Form submission so your CRM or spreadsheet can answer that question.

Why form-level ad data matters

Google Analytics and similar tools count sessions and visitors. They do not know which form submission belongs to which ad, so they cannot report leads or customers by campaign. To close that gap, the form itself must carry the ad information into the systems where you store leads.

WS Form can hold that information in hidden fields. The missing piece is a way to read the ad parameters from the visitor's URL and write them into those fields automatically. The setup below uses Attribution Analytics for that job, and the field structure and reporting logic stay the same throughout.

Four-step setup

  1. Tag each Instagram ad URL with UTM parameters. The URL behind the ad should identify the medium, source, campaign, ad set and ad. A typical pattern is utm_medium=paidsocial, utm_source=instagram, utm_campaign for the campaign name, utm_term for the ad set and utm_content for the specific ad. Free UTM builders exist, and the recommended-parameter guidance is a useful reference.
  1. Install the capture script site-wide and add hidden fields to the WS Form. The script is usually added through your site's settings area, and the exact placement depends on your website builder (WordPress, Squarespace, Wix and others differ). In WS Form, drag a Hidden field type into the form for each value you want to store; the platform makes this a simple drag-and-drop step. At minimum, create fields for Channel, Channel Drilldown 1, Channel Drilldown 2 and Channel Drilldown 3.
  1. Let the script populate the hidden fields. When a visitor arrives from an Instagram ad, the script reads the UTM values and writes them into the matching hidden fields. The campaign and ad details are therefore present in the form before the visitor submits it.
  1. Submit the form and confirm capture. On submission, WS Form stores the hidden-field values alongside the name, email, phone and other entered data. You can then view them in the Submissions table, include them in notification emails, forward them to a CRM such as Salesforce, Pipedrive, HubSpot or Dynamics through native integrations, or send them to Google Sheets.

Pre-flight checklist: is attribution actually working?

A form that submits successfully is not proof that attribution is working. Use this checklist before trusting the reports.

  • The ad URL contains all five UTM parameters you intend to use.
  • The capture script appears on every page where the form can be reached, not only the landing page.
  • Each hidden field name in WS Form matches the field name the script writes to.
  • A test submission from a tagged URL shows the expected values in the Submissions table.
  • A submission from an untagged URL still records a channel rather than a blank value.
  • The CRM or spreadsheet mapping includes the hidden fields, not just the visible ones.

If the form submits but the hidden fields are empty, the problem is usually the script placement or a field-name mismatch. If the hidden fields are populated but the CRM record is blank, the problem is in the integration mapping.

What data lands in WS Form

Two groups of values are written into the hidden fields.

Marketing channel data describes how the lead arrived. For an Instagram campaign, the values follow the UTM tags: Channel becomes Paid Social, Channel Drilldown 1 becomes Instagram, Channel Drilldown 2 becomes the campaign name (for example, Spring Campaign) and Channel Drilldown 3 becomes the ad or creative (for example, Blue Ad). The exact labels depend on the UTM values you set, so consistent naming is what makes the reports readable.

Landing page data records the first page the visitor saw and its category. For example, a visitor who first landed on a blog post would produce a landing page value for that post and a category value such as /blog. This lets you compare lead volume across content sections as well as individual pages.

Field-to-source map

Use this map when creating the hidden fields so each one has a clear job.

  • Channel receives the broad source type, such as Paid Social.
  • Channel Drilldown 1 receives the network, such as Instagram.
  • Channel Drilldown 2 receives the campaign name from utm_campaign.
  • Channel Drilldown 3 receives the ad or creative from utm_content.
  • Landing page fields receive the first page visited and its category.

The four standard Channel and Drilldown fields do not include a slot for the ad set. utm_term carries the ad-set name, so if you want ad-set-level reporting, create a separate hidden field for it and map it alongside the drilldowns rather than expecting it to appear inside the drilldown chain. Keep the naming identical between the ad platform, the hidden field and the CRM property; renaming at one stage is the most common reason a report shows split or missing values.

Worked example: a home builder's spring campaign

Suppose a home-building company runs a spring campaign on Instagram with a blue creative. The ad URL is tagged with utm_medium=paidsocial, utm_source=instagram, utm_campaign=spring-campaign and utm_content=blue-ad.

A visitor clicks the ad, lands on a blog post, and later completes a form. The hidden fields record Channel: Paid Social, Channel Drilldown 1: Instagram, Channel Drilldown 2: Spring Campaign and Channel Drilldown 3: Blue Ad. The landing page fields record the blog post and the /blog category.

When the record reaches the CRM, the sales team can see that this lead came from Instagram rather than organic search, and marketing can count how many leads the spring campaign produced. If the same creative also ran on Facebook, the network field separates the two sources even though both were managed in the same ads platform.

Three reports worth building

Leads by channel. Group submissions by the Channel field and plot them over time. This shows whether paid social is contributing leads at the level you expect relative to organic search, referral and other channels. If most leads come from organic search while most budget goes to Instagram, the report makes that mismatch visible.

Leads by network. Group by Channel Drilldown 1. Instagram ads are often delivered across Meta's other placements, so this view separates Instagram from Facebook, WhatsApp, Messenger and similar surfaces and shows where the ads actually produce leads.

Leads by campaign. Group by Channel Drilldown 2. This ranks campaigns by lead volume and helps decide where to put more budget. Add the ad-level field if you want to compare creatives within a campaign.

Where to send the data

WS Form keeps submissions in its own Submissions table, which is useful for spot checks. Notification emails can include the hidden-field values so the sales team sees the source immediately. For ongoing reporting, send the data to a CRM such as Salesforce, Pipedrive, HubSpot or Dynamics through a native integration, or to Google Sheets where you can build charts. The same field values work in either destination, so choose based on where your team already reviews leads.

Frequently asked questions

Do I need UTM parameters for every Instagram ad?

Yes, if you want campaign- and ad-level reporting. Without UTM parameters the form can still record a channel, but it cannot tell you which campaign or creative produced the lead. Tag each ad URL consistently so the values line up across reports. The usual pattern is utm_medium=paidsocial, utm_source=instagram, utm_campaign for the campaign, utm_term for the ad set and utm_content for the specific ad.

What is the difference between a broken form and broken attribution?

A broken form fails to submit or loses entered data. Broken attribution means the form submits correctly but the hidden fields are empty or wrong. Check script placement and field-name matching for the second case, and form configuration for the first.

Can I see Instagram ad data without a CRM?

Yes. The values appear in the WS Form Submissions table and can be included in notification emails. Sending them to Google Sheets adds charting without requiring a CRM.

Why do my reports show Facebook and Instagram separately?

The network is stored in Channel Drilldown 1, based on utm_source. If the same campaign runs across Meta placements, tagging each placement with its own source value lets the report separate them.