Vendably connects to Microsoft Advertising using OAuth, following the same user-scoped pattern as other ad platform connections. You authorise Vendably from your Microsoft account, Vendably discovers the Microsoft Advertising accounts available to that user, and you select the account to use. Connections are stored against your Vendably user account.
For an overview of the Paid Media capability, see What is Paid Media in Vendably?.
What you need before connecting
- An existing Microsoft Advertising account. This can be a standalone account or an account within a customer hierarchy.
- Permission on your Microsoft account to authorise third-party access. You must have admin or standard access on the intended advertising account.
Connect your Microsoft Ads account
- Go to Ads in the main navigation.
- Open the account connection flow within Ads.
- Choose Microsoft Ads as the platform.
- Vendably redirects you to Microsoft's OAuth consent screen. Sign in with the Microsoft account that has access to your advertising accounts and approve the requested permissions.
- Once you approve, Vendably returns you to the platform and discovers the Microsoft Advertising accounts available to that user.
- Select the account you want to use in Vendably.
The connection is now active.
Import your campaigns
After connecting, use the campaign discovery step to select campaigns to import:
- Go to Ads, then Campaigns.
- Open the discovery step at
/ads/campaigns/discover/. Vendably lists the campaigns found in your connected Microsoft Advertising account. - Select the campaigns you want to import and confirm.
Vendably imports each selected campaign along with its settings and historical data.
A note on performance data timing
Microsoft Advertising uses an async reporting API. When Vendably fetches performance data, the request is submitted to Microsoft and the results are retrieved in the background. This means that after your first connection, or after Vendably requests a new reporting period, metrics may take a little longer to appear compared with Google Ads. This is expected behaviour from Microsoft's API, not a fault with your connection. Allow some time after connecting before expecting fully populated performance data.
Linking a Microsoft Merchant Center account
If you run Shopping campaigns on Microsoft Advertising, you can link a Microsoft Merchant Center account to enable product feed distribution from Vendably's DataHub. This works in a similar way to the Google Merchant Center link for Google Shopping. Set up your product source in DataHub first, then configure the Merchant Center link in the Ads connection settings.
Troubleshooting
OAuth token expired or revoked: Microsoft OAuth tokens have a limited lifespan and may expire or be revoked if your Microsoft account password changes or access is removed. If Vendably shows a connection error for Microsoft Ads, re-open the connection flow, choose Microsoft Ads, and complete the OAuth consent again. Your imported campaign data is preserved.
Performance metrics delayed or not yet visible: this is expected when using the async reporting API. Microsoft processes reporting requests in the background, so there is an inherent delay between Vendably requesting data and the results being available. If metrics remain absent for an extended period beyond a standard sync cycle, check that your Microsoft Ads connection is still active and that the connected account has accessible campaigns with data.
No accounts shown after authorising: confirm that the Microsoft account used during OAuth has access to at least one Microsoft Advertising account. If you manage accounts on behalf of a client, your Microsoft user needs admin or standard access on the relevant account. Try the connection flow again and ensure you sign in with the correct Microsoft account.