Search documentation...

K

Bing Ads

Ensure that you never serve another irrelevant advertisement with Bing Ads

Overview

Deliver highly relevant and targeted ads to your ideal customer profiles by combining data from various sources within your warehouse for marketing campaigns in Bing Ads. Ensure that you never show another irrelevant ad by keeping your custom audiences updated automatically.

Supported syncing

Object TypeDescriptionSupported Sync Modes
EventsSync offline conversion events with data from any sourceInsert
AudiencesCreate new or use an existing audience to sync usersUpsert

Getting started

Authenticate with OAuth

Log in with your Microsoft Ads account, and click Allow. Hightouch requires access to manage your ads account and see your email address.

Syncing data

Events

When syncing offline conversion events, Hightouch treats any records added to your source as new events and sends them to Bing Ads when your sync runs.

To ensure syncs send each event, use a hash function for the event model's primary key . The hash should combine all columns, including member ID, timestamp, etc. See the event sync documentation for more information.

Conversion goal name

This is the conversion goal name to associate with the offline conversions.

Field mapping

Offline conversions require the Microsoft Click ID and Time fields to be valid. The Time field must also:

  • be later than the recorded clickId
  • be within the conversion goal window
  • not be older than 90-days.

For more information, see Microsoft Bing Ads' official documentation.

Audiences

Users get inserted into the Bing Ads customer match list audience. Users removed from the model get removed from the audience.

To sync to a customer match list audience, you need to first create a customer list and accept terms and conditions in the Microsoft Advertising UI.

Field mapping

Customer List Item records require the Email field to be valid and Bing Ads doesn't support mapping other fields.

For more information, see Microsoft Bing Ads' official documentation.

Handling PII

By default, Hightouch automatically detects if your Email field requires hashing and hashes the value before sending requests to Bing Ads if needed.

Tips and troubleshooting

Delayed syncing

Bing Ads suggests waiting up to 48 hours to confirm Audience Size updates.

Common errors

"reason":"8003:CustomerListTermsAndConditionsNotAccepted"

To sync to a customer match list audience, you need to first create a customer list and accept terms and conditions in the Microsoft Advertising UI.

For more information, read the Bing Ads documentation.

Error uploading audience XXX, bulk operation failed: - (4835) - InvalidAudienceId in path

Check the Bing Ads UI to make sure the audience from your sync configuration exists. If the audience no longer exists, you need to create a new sync.

For additional errors, read the Bing Ads error codes documentation.

Live debugger

Hightouch provides complete visibility into the API calls made during each of your sync runs. We recommend reading our article on debugging tips and tricks to learn more.

Sync alerts

Hightouch can alert you of sync issues via Slack, PagerDuty, SMS, or email. For details, please visit our article on alerting.

Ready to get started?

Jump right in or a book a demo. Your first destination is always free.

Book a demoSign upBook a demo

Need help?

Our team is relentlessly focused on your success. Don't hesitate to reach out!

Feature requests?

We'd love to hear your suggestions for integrations and other features.

On this page

OverviewSupported syncingGetting startedAuthenticate with OAuthSyncing dataEventsConversion goal nameField mappingAudiencesTips and troubleshootingDelayed syncingCommon errorsLive debuggerSync alerts

Was this page helpful?