Microsoft Ads Integration
Connect Convultra to Microsoft Advertising (Bing) to send conversions server-side. This gives Microsoft Ads more complete data for automated bidding and audience targeting, and recovers conversions that browser-based UET tags miss due to ad blockers and cookie restrictions.
Why connect Microsoft Ads?
- Recover missed conversions — UET tags are blocked by many ad blockers. Convultra bypasses this by sending conversion data directly to Microsoft's servers.
- Improved automated bidding — More conversion data leads to better performance from Microsoft's smart bidding strategies.
- Accurate attribution — See the true impact of your Microsoft Ads campaigns with complete conversion data.
Requirements
- A Microsoft Advertising account
- At least one conversion goal created in Microsoft Ads
- An active Convultra project with the SDK installed on your website
Setup Steps
Go to Integrations
Navigate to Dashboard → Integrations in Convultra. Find the Microsoft Ads card and click Connect.
Sign in with Microsoft
A Microsoft sign-in window will appear. Sign in with the account that has access to your Microsoft Advertising account. Convultra uses OAuth, so your credentials are handled by Microsoft directly.
Use the Microsoft account that has admin or standard access to the Microsoft Ads account you want to connect. Read-only access will not work for sending conversions.
Select Your Microsoft Ads Account
After signing in, you will see a list of Microsoft Advertising accounts linked to your Microsoft login. Select the account you want to connect.
If you manage multiple accounts, you can connect each one separately.
Configure UET Tag (Optional)
If you are running a Microsoft UET tag on your website alongside Convultra, enter your UET Tag ID here. This allows Convultra to coordinate with the existing tag and avoid duplicate conversion counting.
You can find your UET Tag ID in Microsoft Ads under Conversion Tracking → UET Tags.
If you are not using a UET tag, you can skip this step.
Enable Enhanced Conversions (Optional)
Toggle on Enhanced Conversions to include hashed customer data with your conversions. This improves Microsoft's ability to match conversions to the correct ad clicks.
See the Enhanced Conversions guide for details.
Send a Test Conversion
Click Send Test Conversion in the Test Center. Convultra will send a test event to Microsoft Ads and show you the delivery result.
A green confirmation means your integration is working and ready to send real conversions.
You are all set
Conversions will now be forwarded to Microsoft Ads automatically through the Offline Conversions API.
Features
Offline Conversions API
Convultra sends conversions through Microsoft's Offline Conversions API. This is a server-to-server connection that is not affected by ad blockers, browser cookie settings, or other client-side restrictions.
UET Tag Integration
If you are running a UET tag alongside Convultra, both systems work together. Convultra coordinates with the UET tag to ensure Microsoft Ads receives complete data without double-counting.
Multi-Account Support
Connect multiple Microsoft Advertising accounts and configure each one independently with its own conversion mapping, settings, and logs.
Test Center
Verify your integration at any time by sending a test conversion. This is useful after setup or whenever you make changes to your conversion goals in Microsoft Ads.
Forward Logs
The Forward Logs tab shows a complete history of every conversion sent to Microsoft Ads, including:
- Timestamp
- Conversion goal name
- Event data (value, currency, transaction ID)
- Delivery status (delivered, pending, failed)
- Error details (if any)
Good to Know
OAuth tokens refresh automatically. You will not need to re-authenticate unless you revoke Convultra's access from your Microsoft account settings.
For technical setup (SDK installation, event tracking, or advanced configuration), see the Developer Docs.