How to capture Bing Ads data in Eloqua
Bing Ads can bring in a steady flow of prospects, but the useful question is not how many clicks you bought — it is how many leads and customers those clicks produced. Answering that means the ad's identity has to travel with the person: from the click, into the form, into Eloqua, and finally into the CRM where you report on it.
This guide walks through that chain in four steps. You will tag your Bing Ads URLs, add six hidden fields to your Eloqua forms, let an attribution tool populate those fields, and then read the captured data in Eloqua. It closes with three report patterns that turn the captured values into budget decisions.
What you are actually building
The setup has one job: make sure a form submission carries the marketing context of the visit that started it. Three pieces have to line up.
- The ad URL carries UTM parameters that describe the medium, source, campaign, ad group and ad.
- The Eloqua form has hidden fields ready to receive that description.
- Something on the page reads the parameters and writes them into those fields before the visitor submits.
If any one piece is missing, the submission arrives with contact details but no usable ad context, and your reports collapse back to counting clicks.
Step 1: Tag your Bing Ads URLs
UTM parameters are short text snippets appended to a landing page URL. They tell your analytics and form tooling how a visitor arrived. A tagged URL keeps the original path and adds the parameters after a question mark, separated by ampersands.
A consistent scheme for Bing Ads looks like this:
- UTM Medium = paidsearch
- UTM Source = bing
- UTM Campaign = the name of your Bing Ads campaign
- UTM Term = the ad group the ad belongs to
- UTM Content = the specific ad
The values are yours to choose, but the format should be fixed before you scale. Decide the casing, decide whether you write "bing" or "bing.com", and write it down where your team and any agency can see it.
Step 2: Add six hidden fields to your Eloqua forms
Open the Eloqua form you want to instrument — typically a contact or enquiry form — and drag the Hidden Field field type from the left-hand menu into the form six times. Then create these fields:
- Channel
- Channel Drilldown 1
- Channel Drilldown 2
- Channel Drilldown 3
- Landing Page
- Landing Page Group
Hidden fields are invisible to visitors, so they do not affect the form's appearance or completion rate. They exist purely to carry data. The exact field names matter: whatever writes into them and whatever reads out of them later must agree on the spelling.
Step 3: Let the attribution tool fill the fields
With parameters on the ads and hidden fields on the form, the attribution layer writes values into those fields whenever someone submits. A worked example makes the mapping concrete. Suppose a law firm runs a Bing Ad promoting free 30-minute consultations for new clients, under a campaign called New Client Campaign, using an ad called Free Consultation Ad. The fields would be populated as follows:
- Channel = Paid Search
- Channel Drilldown 1 = Bing
- Channel Drilldown 2 = New Client Campaign
- Channel Drilldown 3 = Free Consultation Ad
Notice that the raw parameter value and the stored value are not identical. The medium "paidsearch" becomes the readable channel "Paid Search", and the source "bing" becomes "Bing". That translation is the point of the layer: your reports read human labels rather than URL fragments.
Step 4: Confirm the data landed in Eloqua
When a visitor completes the form, Eloqua collects the hidden field values alongside their name, email and anything else they typed. To check a submission, open the form in your Eloqua account, choose Actions, then View Submission Data.
From there you have three practical uses for the captured values:
- Include them in new lead notification emails so the sales team sees the campaign at the moment a lead arrives.
- Pass them into your CRM — Salesforce, Pipedrive, HubSpot and similar — so reporting happens where opportunity and revenue data live.
- Keep them in Eloqua for segmentation and campaign membership rules.
A quick verification habit: submit a test entry from a tagged URL, then confirm all six fields are populated rather than blank.
Why raw UTM capture on the form page often fails
There is a common failure mode worth understanding before you choose a method. Some setups only look for UTM parameters in the URL of the page where the form is submitted. Picture a visitor who clicks your ad, arrives on the homepage, reads a couple of pages, and only then fills in the contact form. By that point the URL no longer contains the ad's parameters, so the submission is recorded as if the ad never existed — even though the visit plainly began there.
A tool that keeps the parameters in the visitor's browser sidesteps this. The values survive navigation, so wherever the visitor finally converts, the original ad context is still available to write into the form. When you compare methods, make this the test: does attribution survive a journey across several pages?
A second, subtler failure is naming drift. Suppose one agency tagged its Bing traffic with utm_source=bing and another used utm_source=bing.com. Raw capture would file those as two unrelated sources, and someone would eventually have to merge them by hand. Normalization — collapsing both into a single Paid Search / Bing channel — removes that cleanup work.
Capture landing pages too, not just the ad
Channel data answers "which ad?" but not "which content?" Capturing the visitor's initial landing page and the section it belongs to adds that second dimension. If someone first arrived on a blog article, the tool records the article URL and its category — for example, a post URL plus the /blog section it sits in.
With both values stored, you can see which pages and content types actually attract leads and customers, not merely which ones get traffic. That is usually a more actionable finding than another channel breakdown.
Three reports worth building first
Once attribution values reach your CRM, the reporting question becomes simple: group by a captured field, count or sum an outcome.
Leads by Channel. A chart of lead counts per marketing channel — Paid Search, Organic Search, Paid Social and so on. Use it to compare Bing Ads against everything else competing for the same budget. If organic search produces most of your leads while paid search absorbs most of your spend, that is a signal worth acting on.
Customers by Campaign. A per-campaign count of customers closed in a period. Use it to find which Bing campaigns actually convert into revenue, then shift budget toward them or reuse their creative and messaging in future campaigns.
Revenue by Ad. Revenue attributed to each individual ad. Use it to cut or reduce spend on weak ads and concentrate budget on the ones producing income.
All three depend on the same prerequisite: the hidden fields were populated at submission time. If a report looks empty, check the form before you check the chart.
Pre-launch checklist
Run through this before you trust the numbers.
- Every active Bing Ad URL carries all five UTM parameters, using the agreed naming scheme.
- Each Eloqua form you care about has exactly six hidden fields, spelled as listed above.
- The attribution layer is installed on the pages where forms appear, not only on landing pages.
- A test submission from a tagged URL shows all six fields populated in View Submission Data.
- A second test that lands on one page and submits on another still shows the original ad's values.
- The CRM mapping for the six fields is confirmed, so reports can group on them.
- Someone owns the UTM naming convention and reviews it when a new agency or team member starts.
Beyond Bing Ads
Bing is rarely the only source of demand. Organic search, referrals, direct visits, organic social and paid social all contribute, and a setup that only instruments one channel gives you a distorted picture of where to invest.
Because the same six fields accept values from any channel, extending the setup to your other campaigns is mostly a matter of tagging consistently. The reporting structure you built for Bing Ads then works unchanged for everything else.
| Hidden field | What it stores | Example value from the consultation ad |
|---|---|---|
| Channel | The high-level marketing channel | Paid Search |
| Channel Drilldown 1 | The specific source within that channel | Bing |
| Channel Drilldown 2 | The campaign name | New Client Campaign |
| Channel Drilldown 3 | The specific ad | Free Consultation Ad |
| Landing Page | The first page the visitor saw | The tagged landing page URL |
| Landing Page Group | The section that page belongs to | The page's category, such as /blog |
Example values illustrate the mapping described in the guide; your own campaign and ad names will differ.
| Report | What it shows | Decision it supports |
|---|---|---|
| Leads by Channel | Lead counts per marketing channel | Whether Bing Ads deserves its share of budget versus organic search, social and other channels |
| Customers by Campaign | Customers generated per Bing campaign in a period | Which campaigns to fund further and which elements to replicate |
| Revenue by Ad | Revenue earned from each individual ad | Where to increase spend and where to cut or pause |
These are report patterns, not fixed templates; the exact chart depends on how your CRM stores the captured fields.
Frequently asked questions
Do hidden fields change how my Eloqua form looks to visitors?
No. Hidden fields are not rendered for the visitor, so the visible form stays the same. They only carry data into the submission record.
Why did a lead show no Bing Ads data even though they clicked an ad?
The most common cause is that the form was submitted on a different page from the one the ad pointed to, and the method in use only reads parameters present in the current URL. Storing the parameters in the browser across pages resolves this.
Can I use my own UTM values instead of the suggested ones?
Yes. The suggested scheme is a convention, not a requirement. What matters is that the values are consistent over time and that your attribution layer can map them to a channel.
Where do I check that the data was captured?
In Eloqua, open the form, select Actions, then View Submission Data. All six hidden fields should show values for a submission that originated from a tagged ad.
Do I need a CRM to get value from this setup?
Not strictly. Eloqua alone lets you review submissions and trigger lead notifications. But customer and revenue reporting generally requires the data in a CRM where those outcomes are recorded.
What if two agencies used different UTM source values for Bing?
Raw capture would treat them as separate sources. A normalization layer maps both to a single channel, which removes the manual reconciliation step.