Paid

Microsoft Ads integration for digital marketing agencies

Microsoft Ads (formerly Bing Ads) is the platform every digital marketing agency dismisses until a client asks for it — and then has to scramble to set up correctly. Microsoft Ads imports campaigns from Google Ads with surprising fidelity, but the UET tag and conversion goal setup is independent. Recording the UET configuration explicitly guards against the most common agency mistake: assuming Google Ads conversions transfer to Microsoft.

How Phloz models Microsoft Ads

What Phloz records about Microsoft Ads on each client's tracking map, and what it doesn't. Only GA4, Google Tag Manager and Google Ads connect to Phloz (read-only, through a connected Google account); everything else is recorded by your team. Health states are set by the person who checks, the structural audit re-runs weekly, and graph relationships show what each node connects to — so a node marked broken or overdue for verification shows up in the cross-client tracking-health view.

  • Microsoft Advertising account as a typed node with account ID, UET tag ID, and currency
  • The audit flags a Microsoft Ads account with no UET tag recorded
  • Health status and last-verified date on the account, set by your team — conversion goals themselves stay in Microsoft Advertising
  • Edges from the GTM container (or the site) that fires the UET tag, so the install path is documented

Common Microsoft Ads configuration gotchas

The configuration mistakes agencies most often make with Microsoft Ads, surfaced here as a checklist agencies can run at every client onboarding. Honest, useful, not gated behind a sales pitch — these are real and you should audit for them regardless of whether you use Phloz.

  • Imported conversion goals still need the UET tag: Google Import can bring conversion goals across now, but a goal counts only what the UET tag reports on the site. Check that each imported goal records conversions after the import instead of trusting the list — or imported campaigns optimise blind.
  • UET tag installation: many agencies install via GTM but forget to enable the UET tag on the GTM trigger for "All Pages." Verify the tag fires sitewide, not just on landing pages.
  • Enhanced CPC bidding: requires sufficient conversion volume per goal. Agencies enable Enhanced CPC on day-one Microsoft accounts and bid hits ceiling without enough data to optimise. Wait 30 days minimum.

At launch (V1)

Microsoft Advertising accounts as typed nodes, with the UET tag ID recorded as a field on the account (not its own node). Conversion goals aren't modelled, and Phloz reads no Microsoft Ads data.

Not built yet

Bing Ads API sync for UET tag health and conversion goal status.

Why we built the integration this way

Most agency CRMs treat third-party tools as text fields: "GA4 Property ID" goes in a custom column on the client record. That works at one or two clients and breaks at five. With Microsoft Ads recorded on each client's tracking map — as its own typed node where Phloz has one, as fields and notes where it doesn't — the agency can answer "is this client's Microsoft Ads setup documented, and when was it last verified?" per client, and see every client ranked by tracking health.

Most of it is entered by hand at onboarding: only GA4 properties, GTM containers and Google Ads accounts can be imported from a connected Google account, and nothing syncs afterwards. The manual pass forces explicit verification at the exact moment the agency takes over the client's tracking — the cheapest moment to catch the gotchas listed above, before they become production issues.

When to use this in your client onboarding flow

The pattern we recommend: at every new client onboarding (see the client onboarding audit use case), spend 30 minutes documenting the client's Microsoft Ads configuration on the tracking map — IDs, tracking-code installations, conversion setup, the relationships to other systems. Verify each one fires by triggering a test event, then mark the node verified so the date is recorded. Add a recurring task (monthly, say) for the re-check, assigned to whoever owns tracking — the audit flags anything unverified for 30+ days either way.

Thirty minutes at onboarding costs far less than finding the same tracking issues during the first month of campaign optimisation — when finding them would mean a refund conversation. See the broader tracking infrastructure map use case for the agency-wide pattern.

Frequently asked questions

The three questions agencies ask most often about Phloz's Microsoft Ads integration. Honest answers — same data we'd give a friend evaluating the integration.

Is Microsoft Ads worth setting up for every agency client?
For B2B-heavy clients targeting older demographics, yes — Microsoft Ads users skew higher-income and older, with less competition than Google. For DTC e-commerce targeting Gen Z, often not worth the setup overhead. Phloz models the account as a typed node, so whether a client runs Microsoft Ads — and how it is tagged — is documented per client.
How does the Google-Ads-to-Microsoft import work?
Microsoft Ads has a built-in importer that pulls campaign structure from Google Ads. Phloz doesn't track that import — the Microsoft Ads account node has no import fields, so note the sync mode there if it matters. Agencies running mirrored campaigns set the sync to weekly; agencies treating Microsoft as a fully separate channel turn sync off.
What about LinkedIn Ads — same integration pattern?
Much the same. LinkedIn Ads uses the LinkedIn Insight Tag and conversion tracking, which architecturally resembles Microsoft's UET, and it has its own node type: the LinkedIn Ads account records the Insight Tag ID and a Conversions API on/off flag, and the audit flags an account with no Insight Tag. See the LinkedIn Ads page.

Other integrations

Other paid and adjacent tools, and how Phloz handles each.

Start your free trial

14 days free for new workspaces · No credit card · Starter tier free forever