Microsoft Advertising
Microsoft Advertising (formerly known as Bing Ads) is a service that provides pay-per-click advertising for both the Bing and Yahoo search engines. To get an overview of Microsoft Advertising, see its entity hierarchy and limits documentation.
Our Microsoft Advertising connector queries for metadata and performance reports for all your accounts and syncs the data into your destination.
Features
| Feature Name | Supported | Notes |
|---|---|---|
| Capture deletes | ||
| History mode | ||
| Custom data | KEYWORD_CUSTOM_PARAMETER_HISTORY, AD_CUSTOM_PARAMETER_HISTORY, CAMPAIGN_CUSTOM_PARAMETER_HISTORY and AD_GROUP_CUSTOM_PARAMETER_HISTORY tables. | |
| Data blocking | ||
| Column hashing | ||
| Re-sync | ||
| Row filtering | ||
| API configurable | API configuration | |
| Priority-first sync | ||
| Fivetran data models | ||
| Private networking | ||
| Authorization via API |
Supported deployment models
We support the SaaS and Hybrid deployment models for the connector.
You must have an Enterprise or Business Critical plan to use the Hybrid Deployment model.
Source API version
This connector uses Microsoft Advertising API version 13.0.
Setup guide
Follow our step-by-step Microsoft Advertising setup guide to connect Microsoft Advertising with your destination using Fivetran connectors.
Sync overview
Rollback sync
A rollback sync is a sync that automatically starts once a day. Rollback syncs capture the changes that happen outside of the incremental sync time frame. You can configure this parameter in the setup form.
Fivetran does not automatically capture the conversion window size.
Since we only run the rollback once a day, we recommend that you set a greater rollback window size for your Microsoft Advertising connection than your conversion window value set in Microsoft Advertising to capture all conversion data. For example, our default rollback window size of 35 days corresponds to the default Microsoft conversion window value of 30 days.
Table re-sync
When the connection requests data from Microsoft Advertising, the data is retrieved in bulk. This means that a single response contains entities related to different tables, and all these tables share a common cursor. As a result, a re-sync of just a single entity table is not supported. When a re-sync of an entity table is triggered, the cursor for all entity tables is reset, and all entity tables are re-synced as well.
The following tables are entity tables:
ad_attribute_historyad_custom_parameter_historyad_group_custom_parameter_historyad_group_history,ad_group_label_historyad_historyad_label_historyad_publisher_countryasset_group_historyasset_group_attribute_historybudget_historycampaign_custom_parameter_historycampaign_historycampaign_label_historyconversion_goal_historykeyword_custom_parameter_historykeyword_historykeyword_label_historykeyword_publisher_countrylabel_history
Multithreading
The Microsoft Advertising connector supports multithreading. Fivetran uses multiple parallel API requests to sync Ads data from your Microsoft Advertising account to your destination. Your connection’s sync speed depends on your Microsoft Advertising account metadata.
Schema information
This schema applies to all Microsoft Advertising connections.
Microsoft Advertising schema
To zoom, open the ERD in a new window.Schema notes
In the ACCOUNT_HISTORY table, we add last_modified_time as EPOCH for the accounts which do not have a last_modified_time.
The Microsoft Advertising Bulk API doesn't return deleted entities (for example, campaigns, ad groups, ads, and keywords). Deleted entities are therefore not included in metadata tables, but you can still find them in different report tables.