Microsoft Ads conversion goals: import from GA4 or fire the UET tag directly?

Say you already have GA4 running on a lead gen site and you're adding Microsoft Ads. You can import the GA4 key events as goals, or put the UET tag on the thank-you page and build the goals there. Importing looks tidier since everything is tracked in one place, but I'm not sure it's the better call. The import depends on GA4 attribution and processing, so the signal reaches Bing's bidding later and with less detail on which click produced it. UET records the msclkid on the conversion itself, which gives the bid strategy a cleaner and faster read. For anything feeding Maximize Conversions or Target CPA, I'd fire UET and keep GA4 for cross-channel reporting. Has anyone seen imported goals match UET counts closely on a low-volume account? That's where I'd expect the gap to hurt most.

Agreed on the bidding side. For low volume I'd add one rule: each goal gets exactly one source. If a GA4 import and a UET goal both count the same lead, Microsoft books it twice and Target CPA learns from inflated numbers, so keep the bidding goals on UET only.

Jun's rule holds, but the double count usually comes from two goals rather than one. Say a dental clinic has a GA4 key event on the form submit and a UET goal on the thank-you page, and both fire for the same lead. Each goal has a single source, so the rule looks satisfied, but if both are marked as primary, Maximize Conversions learns that lead twice. Check which goals actually count toward bidding, and keep the GA4 import as secondary so it only shows up in reports.

Mira's right, and what decides it is whether the GA4 import is set as primary or secondary. Microsoft's primary/secondary split controls bidding, so a dual-source setup only double counts if both sides are primary. It takes a minute to check.

Primary versus secondary only decides which goal feeds bidding, it doesn't stop a goal from counting twice. If the thank-you page reloads or someone revisits it, UET can still fire twice for one lead, so the goal needs to fire once per lead, not once per page view. How do you usually stop that?

Mostly it comes down to the Count setting on the UET goal. Each Microsoft Ads conversion goal is set to either "Every" or "One", and for lead gen you want "One". It counts only the first conversion per click, so reloading the thank-you page or coming back from the same click doesn't add a second lead. It's easy to miss because the default can stay on "Every" when a goal gets copied over from an ecommerce setup, where every purchase should count.

The catch is that Count works per click, not per person. If someone fills the form on Monday from one ad click and again on Thursday from another, both count, and that's usually correct. The double count shows up when the form auto-submits on refresh, or when the same person returns through a new click, like a retargeting ad. For a small clinic that's rare enough to ignore, but on a high-volume form it's worth comparing the lead list against the conversion count once a week.

Counting per click is the right setup here, but it's also why your GA4 import won't match UET one-to-one on a low-volume account. GA4 attributes by session using its own model, not by click, so on small numbers the gap shows up fast. Is your thank-you page a separate URL or an on-page confirmation?

Honestly it comes down to whether the thank-you page is its own URL. If it is, the UET goal is usually a page-load match, so reloads and back-button visits are where the extra counts sneak in. Setting the count to "One" takes care of that. With an on-page confirmation, the form fires a single success event and both GA4 and UET can key off it, so the two numbers tend to land much closer, even at low volume.