Track Bing Ads leads and customers in Insightly
Ad platforms report clicks and impressions, but non-ecommerce businesses still need to know whether those clicks became enquiries, customers and revenue. This guide explains how to carry campaign information from a Bing Ads click through a website form into Insightly, so reporting can be based on pipeline outcomes rather than visits alone.
Why visits are not enough
Website analytics can count visits, but it cannot by itself show how many of those visits became leads or paying customers. The missing link is campaign information attached to the enquiry. If that information travels with the form submission into the CRM, Insightly reports can group leads, customers and revenue by the campaign, ad or keyword that started the journey.
Four-step setup
Follow these four steps in order:
- Add UTM parameters to every Bing Ads destination URL so the campaign, ad set and ad are identifiable.
- Install the attribution snippet on the website, using the site admin area or a tag manager where appropriate.
- Add hidden fields to enquiry forms such as Contact Us or Request a Quote.
- Connect the form tool to Insightly, either through its built-in integration or through a connector such as Zapier.
Checklist before launch: every Bing ad URL has consistent parameters, the snippet loads on landing pages, hidden fields are present on each form, a test submission reaches Insightly, and the test record shows the expected channel, campaign and ad values.
Build a consistent UTM pattern
UTM parameters are text appended to a URL that analytics and attribution tools can read. For Bing Ads, a consistent pattern helps reporting stay comparable across campaigns:
- Medium set to paidsearch
- Source set to bing
- Campaign set to the campaign name
- Term set to the ad set name
- Content set to the ad name
For example, a landing page URL can carry paidsearch, bing and a named brand campaign as its parameters. Consistency matters more than clever naming: use the same values every time so Insightly groups records correctly.
How the data travels
When a visitor arrives from a Bing ad, the attribution snippet reads the UTM parameters and stores them in the browser. That stored data remains available while the visitor explores other pages or returns later. On form submission, the snippet populates the hidden fields. The form tool then sends those hidden values to Insightly together with the details the visitor typed in, such as name and email.
Worked example
Consider a mobile hair salon. A visitor clicks a Bing ad for a free consultation, browses a few pages, then submits a contact form. The Insightly record could show Paid Search as the channel, Bing as the first drilldown, the home hairdressing campaign as the second, and the free consultation ad as the third. Those four fields make it possible to trace the enquiry back to the exact ad without relying on memory or manual tagging.
Reports to build in Insightly
Once source data is stored on each lead, three reports are especially useful. Leads by channel compares Bing against Paid Social, Organic Search and other sources month by month. Customers by Bing campaign shows which campaigns produce paying customers, not just enquiries, so budget can move toward proven performers. Revenue by keyword breaks new-customer revenue down by the keyword that triggered the ad, helping teams decide where higher bids are justified.
The same stored data can also include the first landing page and its category, which supports reporting on content that generates enquiries.
Customer example
Customer example worksheet
Record a customer example you can verify. Leave unknown fields blank until you have supporting evidence.
| Field | Your details |
|---|---|
| Customer and permission to use the example | ________ |
| Problem and starting point | ________ |
| Configuration or actions | ________ |
| Measurement period | ________ |
| Outcome and supporting evidence | ________ |
| Approval to publish | ________ |
Getting started
Start with one campaign and one form, verify that a test lead arrives in Insightly with the correct channel, campaign, ad and keyword values, then expand the UTM pattern to all Bing Ads. Once the data is flowing, compare channels on leads, customers and revenue rather than clicks alone.
| UTM parameter | Recommended Bing Ads value |
|---|---|
| UTM_Medium | paidsearch |
| UTM_Source | bing |
| UTM_Campaign | [Name of your campaign] |
| UTM_Term | [Name of your ad set] |
| UTM_Content | [Name of ad] |
Values are a recommended pattern; campaign, ad set and ad names should match the advertiser's own naming.
| Insightly field | Example value |
|---|---|
| Channel | Paid Search |
| Channel Drilldown 1 | Bing |
| Channel Drilldown 2 | Home Hairdressing Campaign |
| Channel Drilldown 3 | Free Consultation Ad |
Example values depend on the UTM parameters used on the ad.
Frequently asked questions
What is needed to pass Bing Ads data into Insightly?
Add UTM parameters to the ad destination URL, install the attribution snippet, add hidden fields to the form, and send the submitted form data to Insightly through the form tool's integration or a connector such as Zapier.
Does the attribution data survive return visits and multi-page browsing?
Yes. The attribution data is stored in the visitor's browser, so it can persist while they browse multiple pages or leave and return later, and is then written into the form when they submit it.
Can this capture leads from channels other than Bing Ads?
The same setup can capture source information for other channels, including Organic Search, Organic Social, Referral and Direct, in addition to paid search.