Skip to content

How to track Google Ads campaigns in Microsoft Dynamics CRM

Google Ads can generate clicks and form fills without telling you which campaigns produce qualified leads, opportunities or customers. This guide shows a practical way to carry campaign context from the ad click into Microsoft Dynamics CRM so you can compare campaigns on business outcomes rather than clicks alone.

Why connect Google Ads data to Microsoft Dynamics CRM

When campaign information travels with each lead into Microsoft Dynamics CRM, you can see which campaigns produced leads, opportunities and customers. That lets you decide which campaigns to keep, adjust or drop. You can also build reports inside Microsoft Dynamics CRM, or connect a reporting tool such as Power BI, to compare campaigns that return positive value with those that do not.

What the tracking layer does

The tracking layer is a small piece of code placed on your website. When a visitor arrives, it inspects technical information about the visit and classifies the visitor into a channel such as paid search, paid social or organic search. That channel information is stored in the visitor's browser as a cookie. When the visitor submits a lead form, the channel details are passed into Microsoft Dynamics CRM alongside the name, company, email and other form data. A lead from a Google Ads campaign can therefore arrive with values such as paid search, the campaign name, the ad group name and the landing page.

Four setup steps

The setup follows a simple sequence: tag the ads, prepare the form, let the tracking layer fill the hidden fields, then confirm the data reaches Microsoft Dynamics CRM.

1. Add UTM parameters to Google Ads campaigns

UTM parameters are extra pieces of text appended to the URL you send people to. For example, a page at https://roipaths.com/integrations/dynamics could be tagged as https://roipaths.com/integrations/dynamics?utm_medium=paidsearch&utm_source=google&utm_campaign=brand-campaign. The exact values are your choice, but a consistent convention for Google Ads is: UTM Medium = Paid search; UTM Source = Google; UTM Campaign = the Google Ads campaign name; UTM Term = the ad group name; UTM Content = the specific ad. Free URL-building tools can help construct these tags.

2. Add hidden fields to lead capture forms

Add hidden fields to the forms used to collect visitor information. The fields are: Channel; Channel Drilldown 1; Channel Drilldown 2; Channel Drilldown 3; Landing Page; Landing Page Group. Most form builders, including Gravity Forms, Typeform and Jotform, let you drag a hidden field type into the form. Builder-specific instructions are available in the help center.

3. The hidden fields receive Google Ads data

After setup, the tracking layer records where visitors come from. When a visitor completes a form, the hidden fields are populated from the UTM values. For example, a visitor from a brand campaign in paid search would produce: Channel = Paid search; Channel Drilldown 1 = Google; Channel Drilldown 2 = Brand campaign; Channel Drilldown 3 = Free account ad. The visitor's first landing page (for example, olmo.com/features/music-licencing) and first landing page group (for example, features) are also captured.

4. Send the data into Microsoft Dynamics CRM

When the form is submitted, the Google Ads data derived from the UTM parameters is sent into Microsoft Dynamics CRM together with the lead's name, email, phone and other details. Inside Microsoft Dynamics CRM you can report with the built-in reporting tools or connect a tool such as Power BI for more advanced analysis.

Hidden field map and worked example

Use this map to check that each hidden field is wired to the right value before you rely on reports.

Why this approach beats raw UTM capture

Capturing raw UTM parameters directly has four common weaknesses. First, raw capture usually covers only tagged campaigns, while this approach also records visitors from organic search, referral, organic social and direct traffic, so reports can show where all leads and customers come from. Second, raw capture often depends on the UTM parameters being present on the page where the form is completed; if a visitor clicks an ad, lands on a campaign page, then moves to a different page to complete the form, the parameters can be lost. Storing the values in a cookie keeps them available across pages. Third, raw values can be messy: UTM_Source=Google.com, UTM_Source=google and UTM_Source=adwords can appear as three separate sources and require manual stitching. Normalizing capitalization and other inconsistencies lets leads be assigned to paid search regardless. Fourth, landing page data is captured as well, including the full landing page and its group, so you can compare whole content sections such as a blog with individual posts.

Three reports to build

Once the data is flowing, these reports turn campaign data into decisions.

Leads by channel

A monthly count of leads by channel shows where leads originate and which channels deserve more resources. For example, if organic search produces most leads, additional SEO investment may be justified.

Customers by campaign

A monthly count of new customers from Google Ads, colored by campaign, shows which campaigns actually generate customers rather than only clicks and visits.

Revenue by keyword

A monthly revenue chart broken down by the keyword the customer searched for shows which keywords generate the most revenue, which may warrant higher bids and which could be paused.

Pre-launch checklist

Before trusting the reports, confirm each item: every Google Ads ad has a final URL with UTM parameters; the UTM values follow one convention for medium, source, campaign, term and content; all six hidden fields exist on every lead capture form; a test submission from a tagged ad shows the expected Channel and Channel Drilldown values in Microsoft Dynamics CRM; a test submission from an untagged channel still records a channel; and the landing page and landing page group fields contain the first landing page rather than the form page.

Wrap-up

Connecting Google Ads data to Microsoft Dynamics CRM lets you record the UTM parameters behind each campaign and report on which campaigns perform best. The same setup also captures leads from other channels, giving a fuller view of lead sources.

Hidden field map with worked example
Hidden fieldExample valueWhat it represents
ChannelPaid searchThe marketing channel
Channel Drilldown 1GoogleThe source within the channel
Channel Drilldown 2Brand campaignThe campaign name
Channel Drilldown 3Free account adThe specific ad
Landing Pageolmo.com/features/music-licencingThe first page the visitor landed on
Landing Page GroupfeaturesThe category of the first landing page

Example values are illustrative and use the source's Olmo Software scenario.

Frequently asked questions

Why do UTM parameters sometimes disappear before the form is submitted?

Many capture methods require the UTM parameters to be present on the page where the form is completed. If a visitor lands on a campaign page from an ad and then navigates to a different page to fill in the form, those parameters may not be available. Storing the values in a cookie keeps them available across pages.

Why do Google Ads leads show up under several different source names?

Raw UTM values can vary in capitalization and wording, for example Google.com, google and adwords. Without normalization, Microsoft Dynamics CRM treats them as separate sources and you have to stitch them together manually. Normalizing the values assigns all of them to paid search.

Does this setup capture leads that do not come from Google Ads?

Yes. Visitors from organic search, referral, organic social and direct traffic are also classified, so reports can show where all leads and customers come from, not only those from paid campaigns.

Can I report on the data inside Microsoft Dynamics CRM, or do I need another tool?

You can use Microsoft Dynamics CRM's built-in reporting tools. For more advanced reporting, you can connect a tool such as Power BI.