Bing Ads
API Documentation: Microsoft Advertising API Documentation
High-Level Information:
The Microsoft Advertising API (Bing Ads) provides access to campaign management, reporting, and customer data within the Microsoft Ads ecosystem. It allows you to retrieve detailed information about your advertising campaigns on the Microsoft Advertising platform, including performance metrics, campaign structures, and geographic insights.
Authentication
This connector uses OAuth 2.0 to authenticate with Microsoft Advertising.
When you connect, you’ll be prompted to sign in and grant access. Make sure you choose the same sign-in provider you use to access Microsoft Advertising:
- Microsoft account (personal) (for example, Outlook/Hotmail)
- Work or school account (Microsoft Entra ID / Azure AD)
- Google (Sign in with Google)
If you select the wrong provider, Microsoft Advertising may reject requests with an error indicating a different identity type is required (for example, GoogleAccountIsRequired, PersonalAccountIsRequired, or WorkAccountIsRequired). If this happens, reconnect and choose the correct provider. Note that a Gmail address can be associated with either a Google sign-in or a Microsoft account, depending on how the Microsoft Advertising user was created.
Source Setup Guide
Step 1
in the Edit Source form to the left.
Step 2
Follow the authentication flow (OAuth) in Microsoft to grant Extract the required permissions.
Step 3
Ensure that your email and profile picture are visible, and verify that the source status is Connected.
Connection Setup Guide
Once you connect Bing Ads to a destination, you will also need to configure:
- Connection Pull Schedule: Determines how frequently data is extracted from the source.
- Backfill (Days): Specifies the duration for which historical data will be retrieved during each connection run.
- Destination specific settings: Different settings such as "Dataset Name" or "Target Schema" (depending on your destination).
- Schema Migration Policy: Controls how Extract will handle schema changes from the source.
If you run into an authentication error indicating a different identity type (for example, messages like GoogleAccountIsRequired, PersonalAccountIsRequired, or WorkAccountIsRequired), select the same sign-in provider you use for Microsoft Advertising and reconnect. Note that a Gmail address may be associated with either provider.
Connector Information
Schema ERD
Explore the interactive entity relationship diagram for Bing Ads.
Data Streams
account_performance_report
accounts
ad_groups
ad_performance_report
ads
billing_documents
campaign_criterions
campaign_performance_report
campaigns
geographic_performance_report
goals_and_funnels_report
keyword_performance_report
keywords
product_partition_unit_performance_report
product_partitions
Troubleshooting
If you see an authentication error mentioning identity type (for example, error Code 126 or a message like “different identity type”), the account you used to authorize doesn’t match the sign-in provider configured for your Microsoft Advertising user.
This commonly happens because a Gmail address can be associated with either sign-in provider.
How to fix
- In Microsoft Advertising, confirm which sign-in provider your user is set up to use (for example, Google vs a Microsoft account such as personal or work).
- In your connector setup, select the same sign-in provider and reconnect the source.
- If the error includes a reason such as
GoogleAccountIsRequired,PersonalAccountIsRequired, orWorkAccountIsRequired, use that as the definitive hint for which provider to choose.