Microsoft Bing Ads Audiences Destination
Beta
This feature is in active development and may change before it's generally availabile.
Destination Info
- Accepts Page, Alias, Group and Track calls.
- Refer to it as Ms Bing Ads Audiences in the Integrations object
- This destination is in Beta
Microsoft Bing Ads Audiences lets you sync Segment audience data to Microsoft Advertising's Customer match lists. This enables real-time or batch audience updates using Microsoft Advertising's Customer Management and Bulk APIs. You can use this destination to keep your audience targeting lists up to date across Microsoft platforms.
- From your workspace's destination catalog page, search for "Ms Bing Ads Audiences".
- Select Ms Bing Ads Audiences and click Add destination.
- Select an existing source to connect to the destination.
- Give the destination a name and click Create destination.
- Connect your Microsoft account:
- Grant Segment permissions to access your Microsoft account (you can disconnect this later).
- Return to the Segment app and navigate to your Ms Bing Ads Audiences desitination's Basic Settings page.
- Enter your Customer Account ID and Customer ID.
- Navigate to the Mappings tab to configure the mappings settings.
- Toggle Enable Destination on to activate your destination.
The account ID of the Microsoft Advertising account you want to manage. You can find it in the URL when viewing the account in the Microsoft Ads User Interface. Not to be confused with Account Number.
The customer (parent) ID associated with your Microsoft Advertising account. You can find this in the URL when viewing your account in the Microsoft Ads User Interface.
Build your own Mappings. Combine supported triggers with the following Ms Bing Ads Audiences-supported actions:
Mapping limits per destination
Individual destination instances have support a maximum of 50 mappings.
Sync users to Microsoft Bing Ads Audiences
Sync Audiences is a Cloud action.
The type of identifier you are using to sync users.
Optional
The email address of the user to add or remove from the audience. If not hashed, Segment will hash this value.
Optional
The CRM ID of the user to add or remove from the audience.
Enable batching of user syncs to optimize performance. When enabled, user syncs will be sent in batches based on the specified batch size.
You can send computed traits and audiences generated using Engage to this destination as a user property. To learn more about Engage, schedule a demo.
For user-property destinations, an identify call is sent to the destination for each user being added and removed. The property name is the snake_cased version of the audience name, with a true/false value to indicate membership. For example, when a user first completes an order in the last 30 days, Engage sends an Identify call with the property order_completed_last_30days: true. When the user no longer satisfies this condition (for example, it's been more than 30 days since their last order), Engage sets that value to false.
When you first create an audience, Engage sends an Identify call for every user in that audience. Later audience syncs only send updates for users whose membership has changed since the last sync.
Real-time to batch destination sync frequency
Real-time audience syncs to Microsoft Bing Ads Audiences may take six or more hours for the initial sync to complete. Upon completion, a sync frequency of two to three hours is expected.