Track Bing Ads leads and customers in GoHighLevel
Clicks and visits do not tell you whether paid search is producing enquiries, sales or revenue. This guide shows how UTM tagging, hidden form fields and browser-stored attribution data can connect a Bing Ads click to the resulting GoHighLevel contact, so campaign decisions are based on outcomes rather than traffic alone.
Why connect the click to the contact?
Without a link between an ad click and the eventual contact, you cannot tell which campaigns deserve more budget. A practical setup preserves the campaign context from the landing visit and attaches it to the form submission, giving you a record that can later be matched to a customer or revenue value in GoHighLevel.
Use this checklist before launching:
- Confirm every Bing destination URL carries the same UTM naming convention.
- Confirm the attribution code loads on landing pages, not only on form pages.
- Confirm each form has the required hidden fields.
- Submit a test enquiry and inspect the GoHighLevel Contact record.
- Check that channel, campaign, ad set, ad and keyword values are readable and consistently named.
Step 1: Tag Bing Ads destinations with UTM parameters
UTM parameters are short labels appended to the URL behind an ad. They let the receiving site know which medium, source, campaign, ad set and ad produced the visit.
For Bing Ads, use a consistent pattern:
- Medium: paidsearch
- Source: bing
- Campaign: the campaign name
- Term: the ad set name
- Content: the ad name
Consistency matters more than clever naming. Decide whether names use hyphens or underscores, whether they are lower case, and how campaign names will be written before tagging. A UTM builder can help you apply the Bing template without manually editing each URL.
Step 2: Store attribution in the browser and pass it through hidden fields
Install the attribution code on the website, directly or through a tag manager, then add hidden fields to the forms you want to measure, such as Contact Us or Request a Quote.
The flow is:
- A visitor arrives from a Bing ad.
- The code reads the UTM values and stores them in the browser.
- When the visitor submits a form, those values are written into the hidden fields.
- The form tool captures the hidden values together with the visitor's entered details.
- The submission is passed to GoHighLevel.
Because the data is stored at arrival, a visitor who browses first or returns later can still have the original campaign context attached to the eventual submission. The same mechanism can also capture landing page and landing page group, which helps show which content produced the enquiry.
Step 3: Send the submission to GoHighLevel and verify the record
If you use GoHighLevel's built-in form builder, the captured attribution values can appear on the Contact record. If you use a third-party builder such as Gravity Forms, Typeform or Jotform, pass the submission through that builder's integration or through a tool such as Zapier.
After a test submission, verify the record answers three questions: which channel produced the lead, which campaign and ad were involved, and which keyword triggered the ad. If any value is blank or inconsistent, fix the UTM tagging or hidden-field mapping before relying on reports.
Three reports to build from the captured data
Once attribution values are on contact records, three reports become useful.
Leads by channel shows monthly enquiry volume across paid search, paid social, organic search, organic social, referral and direct traffic. This reveals whether Bing is a major source or whether another channel is carrying growth.
Customers by Bing Ads campaign counts converted customers by campaign. This is the report to use when deciding where to increase or reduce spend, because it separates campaigns that generate sales from campaigns that generate only visits.
Revenue by keyword groups new-customer revenue by the keyword that triggered the ad. That view helps identify profitable keywords, where raising bids may be justified, and weak keywords, where spend can be redirected.
Failure points to check before trusting the reports
A common failure is tagging ads correctly but never checking the contact record, so hidden fields silently fail to map. Another is using different campaign names in the ad platform and in UTM values, which fragments reporting. A third is judging campaigns by clicks when the business goal is customers or revenue.
Work through the distinction in order: first confirm the UTM values arrive, then confirm they reach GoHighLevel, then confirm customers and revenue can be matched to the same records. Only then use the reports to move budget.
| Field | What to store | Why it matters |
|---|---|---|
| UTM_Medium | paidsearch | Identifies paid search as the channel |
| UTM_Source | bing | Identifies Bing as the source |
| UTM_Campaign | Campaign name | Groups results by campaign |
| UTM_Term | Ad set name | Groups results by ad set |
| UTM_Content | Ad name | Groups results by individual ad |
Naming pattern recommended for Bing Ads in the supplied material; keep values consistent across campaigns.
Frequently asked questions
What is the shortest setup path for Bing Ads attribution in GoHighLevel?
Add consistent UTM values to the destination URL behind each ad, install the attribution code on the site, add hidden fields to the form, and confirm that submitted records in GoHighLevel contain the channel, campaign, ad and keyword values you expect.
Does attribution survive a visitor browsing before submitting a form?
Yes. The attribution data is stored in the browser when the visitor arrives, so browsing first or returning later does not necessarily lose the original campaign information when a form is eventually submitted.
What changes if I use a third-party form builder instead of GoHighLevel forms?
With GoHighLevel's built-in form builder, the captured fields can appear on the Contact record. With a third-party builder, use its built-in integration or a tool such as Zapier to pass the submission into GoHighLevel.