Skip to main content Skip to complementary content
Already have an account? Sign in

Microsoft Advertising (v1)

Last updated: 9/15/2026

Microsoft Advertising feature snapshot

A high-level look at Stitch's Microsoft Advertising (v1) integration, including release status, useful links, and the features supported in Stitch.

STITCH
Release status

Sunset on October 31, 2018

Supported by

Stitch

Stitch plan

Standard

API availability

Not available

Singer GitHub repository

singer-io/tap-bing-ads

REPLICATION SETTINGS
Anchor Scheduling

Supported

Advanced Scheduling

Unsupported

Table-level reset

Unsupported

Configurable Replication Methods

Unsupported

DATA SELECTION
Table selection

Supported

Column selection

Supported

Select all

Supported

TRANSPARENCY
Extraction Logs

Supported

Loading Reports

Supported

Microsoft Advertising replication

There are two types of tables in Stitch’s Microsoft Advertising integration: Core Object and Report.

  • Core Object tables contain foundational data that’s useful for analysis. These are the following tables:

    With the exception of the accounts table, these tables are replicated using Full Table Replication.

  • Report tables are the various Microsoft Advertising reports. The replication process for these tables is a bit unlike that of other tables:
    • Extraction: Data is extracted using a Conversion Window. A Conversion Window is a period of time after a customer clicks an ad that a conversion (ex: a purchase) is recorded in Microsoft Advertising.

    Stitch currently uses a Conversion Window of 30 days.

    This means that data from the past 30 days will be replicated during every replication job.

    • Loading: Data is loaded into your data warehouse using Append-Only Replication.

For Report tables, this means that:

  1. Due to the Conversion Window, a high Replication Frequency may not be necessary. Because Stitch will replicate data from the past 30 days during every replication job, recent data will be re-replicated and count towards your row quota.

    To reduce your row usage and replicating redundant data, consider setting the integration to replicate less frequently. For example: every 12 or 24 hours.

  2. Querying for the latest data in Report tables will require a different strategy than you might usually use. Stitch will add a column named _sdc_report_datetime to Report tables to help you identify the most recent records in a table. See the Query for the Latest Data section for more info and a sample query.

Each part of the replication process for Report tables is explained below.

Report Tables: Data Extraction & Conversion Windows

Every time Stitch runs a replication job for Microsoft Advertising, the last 30 days’ worth of data will be replicated for any Report tables currently being tracked.

Stitch replicates data in this way to account for updates made during the Conversion Window.

For historical and full re-replications of Microsoft Advertising data, Stitch will query for and extract data newer than or equal to the date defined in the Start Date field in the Integration Settings page.

The Start Date, in conjunction with the Conversion Window, defines the minimum date Stitch should query for when extracting historical data. This is calculated as:

Start Date - Conversion Window = Minimum Extraction Date

Example

During the initial set up, the Start Date field is set to July 3, 2017, or 2017-07-03 00:00:00.

To account for the Conversion Window, Stitch would calculate the Minimum Extraction Date value as: 2017-07-03 00:00:00 - 30 days = 2017-06-03 00:00:00

If you were to write a SQL query using this date for the ad_performance_report table, it might look like this:

  SELECT *
    FROM bing_ads.ad_performance_report
   WHERE TimePeriod >= '2017-06-03 00:00:00'   /* Min. Extraction Date */
ORDER BY TimePeriod

For ongoing replication jobs, Stitch will query for and extract data using the last saved maximum value in the table’s Replication Key column and the Conversion Window for the table.

Note: This applies to every replication job that takes place after the historical replication job.

Example

The last maximum saved Replication Key value for the ad_performance_report table is 2017-10-01 00:00:00.

To account for the Conversion Window of 30 days, we’d subtract this from the last maximum saved Replication Key value:

2017-10-01 00:00:00 - 30 days = 2017-09-01 00:00:00

In this case, Stitch would query for and extract data that is newer than or equal to 2017-09-01 00:00:00 and older than or equal to 2017-10-01 00:00:00.

If this were a SQL query, it might look like this:

  SELECT *
    FROM ad_performance_report
   WHERE TimePeriod >= '2017-09-01 00:00:00'
                              /* max Replication Key value - Conversion Window */
     AND TimePeriod <= '2017-10-01 00:00:00'
                              /* max Replication Key value from previous job */
ORDER BY TimePeriod

Report Tables: Data Loading & Append-Only Replication

When Stitch loads the extracted data for Report tables into your destination, it will do so using Append-Only Replication. This is a type of Incremental Replication where existing rows aren’t updated, but appended to the end of the table.

Additionally, the number of rows loaded into the table during each replication job is dependent on the combination of unique values in the dimension columns you track. See the Column Selection and Statistic Aggregation section for more info and examples.

Example

Let’s say these columns are tracking in the ad_performance_report table:

  • campaignId (dimension) - This is the ID associated with a campaign. In this example, there are two campaigns: 929007494 and 929599581
  • deviceType (dimension) - The device type. There are two values for this example: Computer and Tablet
  • impressions (metric) - The total number of impressions.

Every time Stitch replicates and loads data, a row for each unique combination of the dimension columns will be appended to the end of the table:

_sdc_report_datetime TimePeriod AccountId campaignId deviceType impressions
2017-10-01 17:48:26.791 2017-09-10 00:00:00 71086605 929007494 Computer 61
2017-10-01 17:48:26.791 2017-09-10 00:00:00 71086605 929007494 Tablet 15
2017-10-01 17:48:26.791 2017-09-10 00:00:00 71086605 929599581 Computer 37
2017-10-01 17:48:26.791 2017-09-10 00:00:00 71086605 929599581 Tablet 9

Report Tables: Query for the Latest Data

If you want only the most recently replicated data for any Microsoft Advertising Report table, you can use the sample query below to account for the Append-Only Replication Stitch uses.

This query uses two columns - which are automatically included for every Report table - to return the latest data:

  • TimePeriod - The day that the record pertains to.
  • _sdc_report_datetime - The starting time of the Stitch job that extracted the record.
SELECT *
  FROM (
        SELECT *,
        RANK() OVER (PARTITION BY TimePeriod, 
                     ORDER BY _sdc_report_datetime DESC)
        FROM ad_performance_report
        ORDER BY TimePeriod ASC
       ) AS latest
 WHERE latest.rank = 1

In this query:

  1. A subquery first uses a window function to create a ‘window’ of data for each TimePeriod,
  2. The values of the _sdc_report_datetime column are ranked within each window partition, and
  3. Then, in the outer query, only the rows with _sdc_report_datetime values ranked as 1 - which is equal to the maximum timestamp - are returned.

Microsoft Advertising table reference

Report Tables: Column Selection and Statistic Aggregation

The dimension columns selected for replication in Report tables can impact how performance statistics are aggregated. Additionally, this can also affect the number of rows replicated and loaded into your destination.

For example: if gregorianDate, accountId, campaignId, deviceType, and impressions were selected, the impressions column would contain the total number of impressions for the device type for that date:

gregorianDate accountId campaignId deviceType impressions
2018-01-05 00:00:00 71086605 240531207 Computer 4
2018-01-05 00:00:00 71086605 240531207 Smartphone 3
2018-01-05 00:00:00 71086605 240531207 Tablet 3
2018-01-05 00:00:00 71086605 240531207 Unknown 1

If the network column were also selected, a row for every unique combination of deviceType and network would be created and impressions would be aggregated accordingly:

gregorianDate accountId campaignId deviceType network impressions
2018-01-05 00:00:00 71086605 240531207 Computer AOL Search 3
2018-01-05 00:00:00 71086605 240531207 Smartphone AOL Search 1
2018-01-05 00:00:00 71086605 240531207 Tablet AOL Search 0
2018-01-05 00:00:00 71086605 240531207 Unknown AOL Search 0
2018-01-05 00:00:00 71086605 240531207 Computer Bing and Yahoo! search 1
2018-01-05 00:00:00 71086605 240531207 Smartphone Bing and Yahoo! search 2
2018-01-05 00:00:00 71086605 240531207 Tablet Bing and Yahoo! search 3
2018-01-05 00:00:00 71086605 240531207 Unknown Bing and Yahoo! search 1

accounts

The accounts table contains high-level information about each of the ad accounts you selected during setup. Each row in this table corresponds to a single account.

This is a Core Object table.

Replication Method

Key-based Incremental

Primary Keys

id

lastModifiedTime

Replication Key

lastModifiedTime

Useful links

Microsoft Advertising API method

ad_groups

The ad_groups table contains info about the ad groups associated with the campaigns in your Bing Ads account.

This is a Core Object table.

Replication Method

Full Table

Primary Key

id

Useful links

Microsoft Advertising documentation

Microsoft Advertising API method

ad_performance_report

The ad_performance_report table contains performance info about ads, including clicks and conversions. This data can be used to identify and improve under-performing ads.

This is a Report table. See the Replication section for information on how data is replicated and loaded for this table.

Replication Method

Append-Only (Incremental)

Primary Keys

accountId

_sdc_report_datetime

gregorianDate

Replication Key

gregorianDate

Useful links

Microsoft Advertising documentation

adgroup_performance_report

The adgroup_performance_report table contains performance data for ad groups, aggregated by day.

This is a Report table. See the Replication section for information on how data is replicated and loaded for this table.

Replication Method

Append-Only (Incremental)

Primary Keys

accountId

_sdc_report_datetime

gregorianDate

Replication Key

gregorianDate

Useful links

Microsoft Advertising documentation

ads

The ads table contains info about the following ad types:

  • AppInstall
  • DynamicSearch
  • ExpandedText
  • Product
  • Text
  • Image

This is a Core Object table.

Replication Method

Full Table

Primary Key

id

Useful links

Microsoft Advertising documentation

Microsoft Advertising API method

age_gender_performance_report

The age_gender_performance_report table contains info about the age and gender demographics of people interacting with your campaigns and ad groups.

This is a Report table. See the Replication section for information on how data is replicated and loaded for this table.

Replication Method

Append-Only (Incremental)

Primary Keys

accountId

_sdc_report_datetime

gregorianDate

Replication Key

gregorianDate

Useful links

Microsoft Advertising documentation

campaign_performance_report

The campaign_performance_report table contains performance data for campaigns, aggregated by day..

This is a Report table. See the Replication section for information on how data is replicated and loaded for this table.

Replication Method

Append-Only (Incremental)

Primary Keys

accountId

_sdc_report_datetime

gregorianDate

Replication Key

gregorianDate

Useful links

Microsoft Advertising documentation

campaigns

The campaigns table contains info about the campaigns in your Bing Ads account.

This is a Core Object table.

Replication Method

Full Table

Primary Key

id

Useful links

Microsoft Advertising documentation

Microsoft Advertising API method

geographic_performance_report

The geographic_performance_report table contains info about the physical locations of people searching for an ad or the locations people are searching for. This data can be used to validate or improve location targeting strategies.

This is a Report table. See the Replication section for information on how data is replicated and loaded for this table.

Replication Method

Append-Only (Incremental)

Primary Keys

accountId

_sdc_report_datetime

gregorianDate

Replication Key

gregorianDate

Useful links

Microsoft Advertising documentation

goals_and_funnels_report

The goals_and_funnels_report table contains information about your audience’s progression through your conversion funnel. Use this report to determine the point at which users leave the funnel, thereby allowing you to improve and increase conversion.

This is a Report table. See the Replication section for information on how data is replicated and loaded for this table.

Replication Method

Append-Only (Incremental)

Primary Keys

accountId

_sdc_report_datetime

gregorianDate

Replication Key

gregorianDate

Useful links

Microsoft Advertising documentation

keyword_performance_report

The keyword_performance_report table contains performance data about keywords.

This is a Report table. See the Replication section for information on how data is replicated and loaded for this table.

Replication Method

Append-Only (Incremental)

Primary Keys

accountId

_sdc_report_datetime

gregorianDate

Replication Key

gregorianDate

Useful links

Microsoft Advertising documentation

search_query_performance_report

The search_query_performance_report table contains performance data for search terms that resulted in a significant number of clicks in the last 30 days. As this data may change over time, use the keyword_performance_report table to analyze the overall performance of keywords.

Note: This data in this table is not applicable to Bing Shopping campaigns.

This is a Report table. See the Replication section for information on how data is replicated and loaded for this table.

Replication Method

Append-Only (Incremental)

Primary Keys

accountId

_sdc_report_datetime

gregorianDate

Replication Key

gregorianDate

Useful links

Microsoft Advertising documentation

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!