Set up your Microsoft account and connect Microsoft Ads so spend and revenue show up in Northbeam.
When you’re done, Northbeam shows your Microsoft (Bing) Ads spend, impressions, visits, and attributed revenue on the same campaigns, ad groups, and ads.
Before you start, make sure you have:
Help from your Microsoft Azure Active Directory administrator
A Business Microsoft account (not a Personal account) for Microsoft Ads
1. Complete the requirements
Set up API access, user consent, and a business account.
2. Connect the account
Sync spend, impressions, and campaign structure from Microsoft Ads.
3. Confirm tracking
Check that the connection is working.
1
Complete the account requirements
Requirement 1: Verify the Microsoft Advertising API Service for your Azure tenant. Ask your Microsoft Azure Active Directory administrator to make sure:
At least one admin user from your Azure AAD tenant is added and enabled for work accounts in the Microsoft Advertising web application.
The Microsoft Advertising API Service (App ID: d42ffc93-c136-491d-b4fd-6f18168c68fd) is active with msads.manage and ads.manage permissions.
Requirement 2: Enable user consent in Microsoft Entra.
Go to Identity → Applications → Enterprise Applications → Consent and permissions → User consent settings.
Choose either Allow user consent for apps from verified publishers, for selected permissions or Let Microsoft manage your consent.
Either of the two highlighted options works
Requirement 3: Confirm you have a Business Microsoft account. Your account must be a Business account, not a Personal account.
In the Microsoft Ads portal, go to Settings > My Settings > Signed In With.
If it says Personal, follow the link there to switch to Business.
If you skip this step: the connection can fail with Error 105 or Error 106 (see the next step).
2
Connect your Microsoft Ads account
Open Connections. If you’re still in onboarding, go to Integrations instead.
Find Microsoft Ads and click Connect.
Sign in with the Business Microsoft account from step 1.
The connection pulls your current and historical campaigns, ad groups, and ads from the Microsoft Ads API, along with spend and impressions. Your dashboard then shows attributed revenue, transactions, and visits for them. Impressions also power the Clicks + Modeled Views attribution model.
Seeing an error when you connect?
Error 105 is a permissions error. Third-party access needs to be enabled on your Microsoft account. See Requirement 1 above.
Error 106 is an account type error. Connect with a Business Microsoft account, not a Personal one. See Requirement 3 above.
Historical spend backfill: Northbeam backfills spend and performance data for up to 180 days before the date you connect your Microsoft Ads account. Older data isn’t pulled automatically. If you need it, add it with a Spend Sheet or Spend API.
No UTM parameters needed. Once your account is connected, Northbeam adds the tracking parameters to your Microsoft ads automatically. Don’t add Northbeam parameters by hand. They can override the automatic ones and cause tracking issues. See the Microsoft Ads FAQ.If you skip this step: all Microsoft Ads performance is missing from Northbeam.
3
Confirm tracking
Connection syncing: follow Checking platform connections to confirm the account shows as connected and data is arriving.
