Skip to content

Capture Bing Ads attribution in Tally Forms in four steps

Visitor counts alone do not show whether paid search produced enquiries. The workflow below connects Bing Ads campaign labels to a Tally Forms submission, so each lead carries the channel, campaign, ad and first landing page that preceded it. It also preserves attribution when the visitor browses to another page before submitting.

Why form-level attribution matters

Analytics platforms commonly report visits rather than downstream enquiries. If a visitor arrives from Bing Ads, browses several pages and later completes a form, the eventual submission needs to retain the original campaign context. UTM parameters provide that context at the click level, while hidden form fields provide a place to store it with the lead record.

Step 1: Tag Bing Ads URLs consistently

Append consistent parameters to every Bing Ads destination URL. A practical convention is paidsearch for medium, bing for source, the campaign name for campaign, the ad-group name for term, and the specific ad for content. Consistency matters more than the exact labels: changing spellings such as bing and Bing.com across campaigns will fragment later reporting unless the attribution tool normalises them.

Checklist before launch:

  • Every Bing Ads URL uses the same parameter names.
  • Campaign, ad group and ad values match the names used in reporting.
  • A test click reaches the intended landing page with parameters intact.
  • Parameters remain consistent across desktop and mobile destinations.

Step 2: Add six hidden fields to Tally Forms

Create six hidden fields in the Tally Form: Channel, Channel Drilldown 1, Channel Drilldown 2, Channel Drilldown 3, Landing Page and Landing Page Group. Hidden fields stay out of the visitor's view, so they do not add visual friction. In the form editor, place the cursor where a field should go, enter /hidden, choose Hidden field, and repeat until all six are present. Configure each field so the attribution tool can populate it on submission.

Step 3: Let attribution populate the hidden fields

Once tagging and fields are ready, the attribution tool records where the visitor came from and writes that information into the hidden fields when the form is completed. For a consulting example, Channel could be Paid Search, Drilldown 1 could be Bing, Drilldown 2 could be Services Campaign, and Drilldown 3 could be Strategic Advisory Ad. The tool also stores the first landing page and its group, such as a services URL grouped under /services. Because the parameters are retained in the browser, attribution can survive navigation from the landing page to a separate contact page.

Step 4: Use the captured data in submissions, email, CRM or spreadsheets

On submission, Tally Forms stores the attribution values beside the person's name, email, phone and other answers. Those values can then be reviewed in the submissions view, included in notification emails, sent to a CRM such as Salesforce, Pipedrive or HubSpot for dashboards, or exported to a spreadsheet for lightweight reporting. Before relying on the data, submit a test form from a tagged Bing Ads URL and confirm every hidden field is populated correctly.

Three reports to build from the captured fields

Three reports make the captured fields immediately useful. Leads by Channel compares Bing Ads with Google Ads, social, organic search and other sources month by month. Customers by Campaign shows which Bing campaigns produce new customers, supporting bid and budget decisions. Revenue by Ad shows monthly revenue per ad, making it easier to fund strong performers and stop weak ones. Landing-page fields add a fourth lens: which topics and individual pages first attracted converting visitors.

Final check

A reliable setup depends on disciplined tagging, correctly configured hidden fields and a test submission that proves the full path works. Before promoting any signup offer, check the current plan and trial terms directly with the provider, since availability and conditions can change.