Skip to content

Track Bing Ads leads and customers in Sugar CRM

Ad platforms show clicks and impressions, and web analytics shows visits, but neither reliably shows how many enquiries became leads, customers or revenue. Passing campaign information through the form into Sugar CRM closes that gap, so reporting can start from the CRM record rather than from ad-platform estimates.

1. Tag every Bing ad destination

Start with the destination URL for each Bing ad. Small text values appended to that URL tell later tools where the visit originated. A consistent naming pattern matters more than clever values: use the same source and medium spelling across every ad, and reserve the campaign, ad-set and ad fields for the names you will later use in reports.

A practical pattern is:

  • 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

Check the finished URL before launch. If the values are inconsistent, Sugar CRM reports will split one campaign into several apparent campaigns.

2. Install the code and add hidden fields

Place the attribution code on the website so it can read the parameters on arrival. It can be added directly or loaded through a tag manager such as Google Tag Manager. Then add hidden fields to the forms that matter, for example a contact form or a request-a-quote form. Most form builders, including Gravity Forms and Jotform, support hidden fields.

Do a test submission from a tagged URL and inspect the record that arrives in Sugar CRM. Confirm that both the visible form answers and the hidden attribution values are present before relying on the data.

3. Let the code carry the source to the form

When someone lands from a Bing ad, the code stores the parameters in the browser. That storage is important because people rarely submit a form on their first page view. They may read several pages, or leave and return later, and the original source should still be available at submission time.

On submission, the stored values are written into the hidden fields. The same mechanism can also capture other sources, including paid social, organic search, organic social, referral and direct traffic, plus the first landing page and its category. Landing-page capture makes it possible to connect enquiries to content such as a blog post, not only to paid campaigns.

4. Send the submission to Sugar CRM

The form tool receives the hidden values together with the name, email and other details the visitor entered. If that tool connects directly to Sugar CRM, use the built-in connection. If it does not, route the submission through an integration tool such as Zapier.

Map each hidden field to the matching Sugar CRM field, then test with a tagged visit, a second test from an untagged or differently tagged visit, and a check that the CRM record shows the expected channel values. This catches field-mapping errors while they are still easy to fix.

What the captured data looks like

Consider a PR consultancy where a visitor arrives from a Bing ad for a crisis-management campaign and clicks an ad offering a free consultation. The CRM record can show paid search as the channel, Bing as the first drilldown, the crisis-management campaign as the second, and the consultation ad as the third. That structure lets a manager trace a lead back to a specific ad without opening the ad platform.

Use the same drilldown logic for other channels. Keep channel broad enough for budget comparisons, and keep the drilldowns specific enough to identify the campaign and ad that produced the enquiry.

Reports to build in Sugar CRM

Once attribution values sit on CRM records, three reports answer most budget questions:

  • Leads by channel: count leads per month by channel to compare Bing ads with paid social, organic search and other sources, and judge whether the spend is earning its place.
  • Customers by Bing campaign: count closed customers by campaign so budget can move toward campaigns that produce buyers, not only clicks.
  • Revenue by keyword: group revenue from new customers by the keyword that triggered the ad, so profitable keywords can receive higher bids and weak ones can be reviewed.

Build these in Sugar CRM reporting or in a connected reporting tool. Start with one month of clean, consistently tagged data before changing budgets, so the comparison is not distorted by partial tagging.

Putting it together

The overall aim is a single view of where enquiries originate. Bing data can then be compared with organic search, organic social, paid social and other channels, making it easier to spot where growth is most likely. The setup described here is presented as a way to try the approach and confirm the data flow in Sugar CRM before scaling it across campaigns. A useful way to evaluate the result is to pick one campaign, follow a tagged visit through to a Sugar CRM record, and check that the channel, campaign and ad values match what you intended. If they do, extend the same tagging and field-mapping pattern to the rest of your Bing campaigns and compare the resulting lead and customer counts against your other channels.

Frequently asked questions

What should I put in the UTM parameters for a Bing ad?

Add UTM parameters to the ad destination URL so the campaign, ad set and ad can be identified when the visit arrives. The recommended pattern in the material is paidsearch for medium, bing for source, plus the campaign name, ad-set name and ad name in the remaining parameters.

Why are hidden form fields needed?

Install the attribution code on the website, directly or through a tag manager, then add hidden fields to the forms people submit. When a visitor who arrived from an ad completes a form, the stored parameters are written into those fields and travel with the submission.

How does the form data reach Sugar CRM?

Use the form tool's built-in Sugar CRM integration if it has one. If it does not, an integration tool such as Zapier can forward the submitted data to Sugar CRM automatically.

What if a visitor browses for a while before submitting?

The parameters are stored in the browser, so browsing around the site first, or leaving and returning later, does not necessarily lose the original ad source before the form is submitted.