Microsoft Ads
Connect usertrax with Microsoft Ads (formerly Bing Ads) to automatically import your conversion data and optimize your campaigns.
Prerequisites
Section titled “Prerequisites”- Active Microsoft Ads account
- Microsoft Ads conversion goal created
- usertrax account with tracking script installed
Step 1: Create a Conversion Goal
Section titled “Step 1: Create a Conversion Goal”- In Microsoft Ads, go to Tools > Conversion tracking
- Click Create conversion goal
- Select Website as the goal type
- Choose Import from offline conversions
- Name your goal (e.g., “usertrax Purchases”)
- Set the conversion value and attribution settings
Step 2: Get Your Goal Details
Section titled “Step 2: Get Your Goal Details”After creating the conversion goal, note down:
- Goal Name: The exact name you gave your conversion goal
- Customer ID: Your Microsoft Ads account ID
Step 3: Set Up API Access
Section titled “Step 3: Set Up API Access”- Go to Tools > API Center
- Create a new API application or use existing one
- Note your Customer ID and Developer Token
- Generate OAuth credentials if needed
Step 4: Configure usertrax
Section titled “Step 4: Configure usertrax”- In your usertrax dashboard, go to Integrations > Microsoft Ads
- Enter your conversion details:
- Customer ID
- Goal Name
- Developer Token (if using API authentication)
- Click Test Connection to verify setup
- Save your configuration
Step 5: Test the Integration
Section titled “Step 5: Test the Integration”- Generate a test conversion on your website
- Check the usertrax dashboard for the conversion
- Verify in Microsoft Ads that the conversion was imported (may take up to 6 hours)
Troubleshooting
Section titled “Troubleshooting”Conversions Not Appearing
Section titled “Conversions Not Appearing”- Verify your goal name matches exactly (case sensitive)
- Check that your Customer ID is correct
- Ensure conversions have a valid
msclkidparameter
API Authentication Issues
Section titled “API Authentication Issues”- Verify your Developer Token is active
- Check OAuth credentials if using OAuth authentication
- Ensure API access is enabled for your account
Attribution Differences
Section titled “Attribution Differences”- Microsoft Ads may use different attribution models
- Allow up to 24 hours for complete data synchronization
- Check the conversion window settings in both platforms
Advanced Configuration
Section titled “Advanced Configuration”Custom Conversion Values
Section titled “Custom Conversion Values”// Track with custom conversion value for Microsoft Adsusertrax.track({ event: "purchase", total: 199.99, currency: "USD", orderId: "MS-ORDER-456",});Multiple Conversion Goals
Section titled “Multiple Conversion Goals”You can map different events to different Microsoft Ads conversion goals:
- Create multiple conversion goals in Microsoft Ads
- Configure each in usertrax with different event names
- Use specific event names when tracking conversions
Best Practices
Section titled “Best Practices”Conversion Naming
Section titled “Conversion Naming”- Use descriptive, consistent names for conversion goals
- Include the conversion type in the name (e.g., “Purchase”, “Lead”, “Signup”)
- Avoid special characters or spaces in goal names
Value Tracking
Section titled “Value Tracking”- Always include conversion values when possible
- Use consistent currency codes
- Set appropriate conversion windows in Microsoft Ads
Data Quality
Section titled “Data Quality”- Regularly audit your conversion data
- Monitor for unusual patterns or discrepancies
- Test your tracking after any website changes
Comparison with Google Ads
Section titled “Comparison with Google Ads”| Feature | Microsoft Ads | Google Ads |
|---|---|---|
| Import Delay | Up to 6 hours | Up to 3 hours |
| Attribution | Last-click default | Data-driven default |
| Value Support | Yes | Yes |
| Bulk Import | Yes | Yes |