Capture Bing Ads data in Ninja Forms
Visitor counts alone do not show which Bing campaign, ad group, or ad produced a lead. This guide explains how UTM tagging, six hidden form fields, and stored attribution data can connect each Ninja Forms submission to its paid-search origin and landing page.
Why form-level attribution matters
Bing can be a useful channel for reaching buyers, but spend decisions need more than page visits. A form submission should carry enough context to identify the channel, campaign, ad group, specific ad, and first landing page. That context is created before the visitor arrives, preserved during browsing, and attached at submission.
Step 1: Tag each ad destination
Append UTM parameters to each Bing Ads destination URL. Use utm_medium=paidsearch and utm_source=bing for consistency. Put the campaign name in utm_campaign, the ad group name in utm_term, and the specific ad in utm_content. Consistent spelling and casing matter because reports treat differently written values as different entries.
Step 2: Add the hidden fields
Add six hidden fields to the Ninja Forms form: Channel, Channel Drilldown 1, Channel Drilldown 2, Channel Drilldown 3, Landing Page, and Landing Page Group. In Ninja Forms, drag the Hidden field type into the form for each one. Keep the labels stable so downstream email or CRM mappings do not break.
Step 3: Let attribution populate the fields
Once the attribution tool is active, it records where visitors came from and writes the relevant values into those hidden fields when a form is submitted. Because the data is stored in the browser, the UTM parameters do not have to remain on the form page: a visitor can browse elsewhere or return later and still have the original attribution attached. For example, a paid-search visit from Bing for a new-client campaign promoting a free SEO audit ad could produce Channel = Paid Search, Drilldown 1 = Bing, Drilldown 2 = New Client Campaign, and Drilldown 3 = Free SEO Audit Ad.
Step 4: Use the data in each submission
Each submission then combines the visitor-entered details, such as name and email, with the hidden attribution values. Review entries in Ninja Forms > Submissions, add the hidden fields to a lead notification email, or pass them to a CRM such as Salesforce, Pipedrive, or HubSpot for lead and customer reporting. Before launch, submit a test form from a tagged Bing URL and confirm every hidden field arrives with the expected value.
What makes the data more reliable
Four distinctions make the resulting data more useful. First, all channels are recorded, not only Bing, so Paid Search can be compared with Organic Search, Paid Social, Referral, and Direct. Second, stored attribution survives navigation and return visits. Third, inconsistent raw UTM values are normalized into a cleaner channel structure instead of creating duplicate sources in reports. Fourth, the first landing page and its group show which content attracted the lead, making it easier to create more of what works.
Reports to build after setup
With the fields flowing into a CRM, three practical reports stand out. Leads by Channel compares volume across Paid Search, Paid Social, Organic Search, and other channels to guide budget allocation. Customers by Campaign compares paying customers across Bing campaigns so stronger campaigns can receive more budget. Revenue by Ad shows earnings per ad, helping teams learn which messaging and copy produce valuable customers rather than only clicks.
| UTM parameter | Recommended value or meaning |
|---|---|
| utm_medium | paidsearch |
| utm_source | bing |
| utm_campaign | Name of the Bing Ads campaign |
| utm_term | Name of the ad group |
| utm_content | Specific ad |
Recommended tagging convention from the source; keep values consistent across campaigns.
| Hidden field | Purpose |
|---|---|
| Channel | Broad source category, such as Paid Search |
| Channel Drilldown 1 | Source detail, such as Bing |
| Channel Drilldown 2 | Campaign detail |
| Channel Drilldown 3 | Ad or ad-group detail |
| Landing Page | First page visited |
| Landing Page Group | Group or category containing that page |
Field names are the form contract to preserve in email and CRM mappings.
| Report | Question it answers |
|---|---|
| Leads by Channel | How does Bing compare with other channels? |
| Customers by Campaign | Which Bing campaigns produce paying customers? |
| Revenue by Ad | Which ads produce the most revenue? |
Reports require CRM or analytics access to the captured fields and later customer or revenue data.
Frequently asked questions
What are the four steps to capture Bing Ads data in Ninja Forms?
Add UTM parameters to the ad destination, add the six hidden fields to the form, let the attribution tool populate them from the stored visit data, and then review submissions, email notifications, or CRM records.
Which hidden fields should the form contain?
Channel, Channel Drilldown 1, Channel Drilldown 2, Channel Drilldown 3, Landing Page, and Landing Page Group.
Do UTM parameters need to be on the form page itself?
Yes. The attribution data is stored in the browser, so it can still be passed through when the form is submitted on a later page or after a return visit.
What can be done with the captured data after submission?
Review individual entries under Ninja Forms > Submissions, include the fields in a lead notification email, or send the submission data to a CRM for reporting on leads and customers.
Does this only track Bing Ads traffic?
No. The tool also records other sources such as Organic Search, Paid Social, Referral, and Direct, giving a fuller channel comparison.