Skip to content

Capture Bing Ads Attribution in Formstack

Visitor counts alone do not show whether Bing Ads produce enquiries, customers, or revenue. This guide explains how to attach campaign information to each Formstack submission so those outcomes can be reported by channel, campaign, and ad.

Why form-level attribution matters

Bing can bring qualified search traffic, but a visit is only the first step. The business question is whether that visit became a lead, a customer, or revenue. Standard web analytics can show visits, yet it may not connect those visits to the contact details and outcome recorded when a form is submitted. Attaching attribution fields to the form closes that gap: every submission carries both the person's details and the campaign context that brought them to the site.

Step 1: Tag Bing ad destinations consistently

Start with the destination URL for each Bing ad. Add UTM parameters so the campaign, ad group, and ad can be distinguished later. A consistent pattern is: medium set to paidsearch, source set to bing, campaign set to the campaign name, term set to the ad group name, and content set to the specific ad. Consistency matters more than clever naming; changing the pattern mid-flight makes later reporting harder to compare.

Step 2: Add six hidden fields to the form

Open the relevant Formstack form and add six short-answer fields, then mark each one hidden so visitors do not see or fill them in. Name them Channel, Channel Drilldown 1, Channel Drilldown 2, Channel Drilldown 3, Landing Page, and Landing Page Group. These fields are the container; the attribution tool fills them automatically at submission time.

Step 3: Let the tool populate the fields at submission

Once the tool is active, it reads the UTM values from the visit, stores them in a browser cookie, and writes cleaned values into the hidden fields when the form is submitted. Because the values persist in the cookie, attribution survives browsing to a different page before submission. It also normalises variant spellings, so differently formatted source values are grouped under one channel instead of splitting the reporting.

Worked example: from click to submission record

Consider a law firm promoting estate planning through Bing. A submission might record Channel as Paid Search, Drilldown 1 as Bing, Drilldown 2 as the services campaign, and Drilldown 3 as the estate planning ad, alongside the landing page and its group. That single record lets the firm see not just that someone enquired, but which ad and page produced the enquiry. The same record can then be viewed in Formstack, included in notifications, sent to a CRM, or exported to a spreadsheet for dashboard tools.

What else the captured data can show

The tool described here captures attribution for all channels, not only Bing, so the same fields can support Google Ads, social ads, and organic search reporting. Landing-page capture adds another dimension: it records the first page visited and the section it belongs to, which helps show whether blog content, product pages, or service pages generate enquiries. Before publishing reports, check that hidden fields are present on every lead form, that UTM naming is consistent, and that CRM or spreadsheet destinations receive the fields without renaming them.

Hidden fields to add to each Formstack form
Hidden fieldWhat it records
ChannelBroad channel, such as Paid Search
Channel Drilldown 1Source, such as Bing
Channel Drilldown 2Campaign name
Channel Drilldown 3Ad name
Landing PageFirst page the visitor landed on
Landing Page GroupSection or category of that landing page

Field names as listed in the captured setup; confirm exact labels in the owned implementation.

Three reports to build from captured attribution data
ReportDecision it supports
Leads by ChannelCompare monthly lead volume across marketing channels
Customers by CampaignShift budget toward Bing campaigns producing the most customers
Revenue by AdIdentify which ads generate the most revenue and pause underperformers

Reporting examples depend on CRM or analytics data being connected after capture.

Frequently asked questions

What is the basic setup for capturing Bing Ads data in Formstack?

Add consistent UTM parameters to the ad destination, add six hidden short-answer fields to the form, let the attribution tool write channel, drilldown, and landing-page values into those fields, then review or sync each submission in Formstack.

Does attribution still work if someone browses other pages before submitting?

Yes. The attribution data is stored in a browser cookie, so a visitor who lands on one page and submits a form on another page can still have the original attribution carried through.

Which reports become possible once the data is captured?

Useful views include leads by channel, customers by campaign, and revenue by ad. Together they show which channels produce leads, which campaigns produce customers, and which ads produce revenue.