- Getting started
- Account management
- Security
- Destinations
- Integrations
- SaaS
- Overview
- 3PL Central
- ActiveCampaign
- AdRoll
- Amplitude
- AppsFlyer
- Asana
- Autopilot
- BigCommerce
- Braintree
- Bronto
- Campaign Manager
- Campaign Monitor
- Chargebee
- Chargify
- CircleCI
- Close.io
- Club Speed
- Codat
- COVID-19 Public Data
- Crossbeam
- Darksky
- Deputy
- Desk
- Dixa
- Doorbell.io
- eBay
- Eloqua
- Facebook Ads
- Freshdesk
- Front
- FullStory
- GitHub
- GitLab
- Google Ads
- Google Ads (AdWords)
- Google Analytics
- Google Analytics (AdWords)
- Google Analytics 360
- Google Analytics 4
- Google ECommerce
- Google Search Console
- Google Sheets
- Harvest
- Harvest Forecast
- Heap
- Help Scout
- HubSpot
- iLEVEL
- Impact
- Intacct
- Intercom
- Invoiced
- Iterable
- JIRA
- Klaviyo
- Kustomer
- Lever
- LinkedIn Ads
- Listrak
- LivePerson
- Looker
- LookML
- MailChimp
- Mailshake
- Mambu
- Marketo
- Microsoft Advertising
- Microsoft Teams
- Mixpanel
- NetSuite
- NetSuite Suite Analytics
- Onfleet
- Outbrain
- Outreach
- Pardot
- Pendo
- Pepperjam
- Pipedrive
- Quick Base
- QuickBooks
- Recharge
- Recurly
- Referral SaaSquatch
- Revinate
- RingCentral
- SaaSOptics
- Sailthru
- Salesforce
- Salesforce Marketing Cloud
- Selligent
- SendGrid Core
- ShipHero
- Shippo
- Shopify
- Slack
- Snapchat Ads
- Square
- Stripe
- SurveyMonkey
- Taboola
- TikTok Ads
- Toggl
- Trello
- Twilio
- Twitter Ads
- Typeform
- UJET
- Urban Airship
- UserVoice
- Wootric
- Workday RaaS
- Xero
- Yotpo
- Zendesk Chat
- Zendesk Support
- Zoom
- Zuora
- Databases
- Overview
- Amazon Aurora MySQL RDS
- Amazon Aurora PostgreSQL RDS
- Amazon DynamoDB
- Amazon Microsoft SQL Server RDS
- Amazon MySQL RDS
- Amazon Oracle RDS
- Amazon PostgreSQL RDS
- Amazon S3 CSV
- Google CloudSQL MySQL
- Google CloudSQL PostgreSQL
- Heroku
- Magento
- MariaDB
- Microsoft Azure MySQL
- Microsoft Azure SQL Database
- Microsoft SQL Server
- MongoDB
- MongoDB Atlas
- MySQL
- Oracle
- PostgreSQL
- Responsys
- SFTP
- Webhooks
- All integrations
- Connection cloning
- Connect other data sources
- SaaS
- Extracting data
- Loading data
- Analysis tools
- Troubleshooting
- Developers
- Changelog
- version 2 (Latest)
- version 1 (Sunset)
Get started with a free trial today
Already have an account? Sign in
Microsoft Advertising (v1)
This version of Microsoft Advertising reached end of life onOctober 31, 2018 and is no longer functioning.
Upgrade to the latest version (v2) to continue replicating data.
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 plan | Standard | API availability | Not available |
| Singer GitHub repository | |||
| 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
accountstable, these tables are replicated usingFull 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 of30 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.
ForReport tables, this means that:
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.
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_datetimeto 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 forReport 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 anyReport 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 theStart Date field in the Integration Settings page.
TheStart Date, in conjunction with theConversion 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, theStart Date field is set toJuly 3, 2017, or2017-07-03 00:00:00.
To account for the Conversion Window, Stitch would calculate theMinimum 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 thead_performance_report table, it might look like this:
SELECT*FROMbing_ads.ad_performance_reportWHERETimePeriod>='2017-06-03 00:00:00'/* Min. Extraction Date */ORDERBYTimePeriodFor 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 thead_performance_report table is2017-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 to2017-09-01 00:00:00 and older than or equal to2017-10-01 00:00:00.
If this were a SQL query, it might look like this:
SELECT*FROMad_performance_reportWHERETimePeriod>='2017-09-01 00:00:00'/* max Replication Key value - Conversion Window */ANDTimePeriod<='2017-10-01 00:00:00'/* max Replication Key value from previous job */ORDERBYTimePeriodReport 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 theColumn Selection and Statistic Aggregation section for more info and examples.
Example
Let’s say these columns are tracking in thead_performance_report table:
campaignId(dimension) - This is the ID associated with a campaign. In this example, there are two campaigns:929007494and929599581deviceType(dimension) - The device type. There are two values for this example:ComputerandTabletimpressions(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
You may need to alter this query
The query below is meant to act as a foundation for writing your own. Depending on your SQL syntax and the dimensions contained in a given table, you may need to alter this query for your own usage.
When querying your Microsoft Advertising data, you’ll want to include the Dimensions you’re analyzing in the partition. For example: If you’re analyzing campaigns over time, you’d include columns likecampaignId anddate.
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(PARTITIONBYTimePeriod,ORDERBY_sdc_report_datetimeDESC)FROMad_performance_reportORDERBYTimePeriodASC)ASlatestWHERElatest.rank=1In this query:
- A subquery first uses a window function to create a ‘window’ of data for each
TimePeriod, - The values of the
_sdc_report_datetimecolumn are ranked within each window partition, and - Then, in the outer query, only the rows with
_sdc_report_datetimevalues ranked as1- which is equal to the maximum timestamp - are returned.
Microsoft Advertising table reference
Schemas and versioning
Schemas and naming conventions can change from version to version, so we recommend verifying your integration’s version before continuing.
The schema and info displayed below is forversion 1 of this integration.
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: ifgregorianDate,accountId,campaignId,deviceType, andimpressions were selected, theimpressions 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 thenetwork column were also selected, a row for every unique combination ofdeviceType andnetwork would be created andimpressions 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 |
Table and column names in your destination
Depending on your destination, table and column names may not appear as they are outlined below.
For example: Object names are lowercased in Redshift (CusTomERs >customers), while case is maintained in PostgreSQL destinations (CusTomERs >CusTomERs). Refer to theLoading Guide for your destination for more info.
accounts
Theaccounts 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.
Key-based Incremental | |
Primary Keys | id lastModifiedTime |
Replication Key | lastModifiedTime |
| Useful links |
| Join accounts with | on |
|---|---|
| ad_performance_report | accounts.id = ad_performance_report.accountId |
| adgroup_performance_report | accounts.id = adgroup_performance_report.accountId |
| age_gender_performance_report | accounts.id = age_gender_performance_report.accountId |
| campaign_performance_report | accounts.id = campaign_performance_report.accountId |
| geographic_performance_report | accounts.id = geographic_performance_report.accountId |
| goals_and_funnels_report | accounts.id = goals_and_funnels_report.accountId |
| keyword_performance_report | accounts.id = keyword_performance_report.accountId |
| search_query_performance_report | accounts.id = search_query_performance_report.accountId |
accountFinancialStatus STRING | |||
accountLifeCycleStatus STRING | |||
accountType STRING | |||
billToCustomerId INTEGER | |||
countryCode STRING | |||
currencyType STRING | |||
forwardCompatibilityMap ARRAY
| |||
id INTEGER | |||
language STRING | |||
lastModifiedByUserId INTEGER | |||
lastModifiedTime DATE-TIME | |||
name STRING | |||
number STRING | |||
parentCustomerId INTEGER | |||
pauseReason INTEGER | |||
paymentMethodId INTEGER | |||
paymentMethodtype STRING | |||
primaryUserId INTEGER | |||
timestamp TIMESTAMP | |||
timezone STRING |
ad_groups
Thead_groups table contains info about the ad groups associated with the campaigns in your Bing Ads account.
Full Table | |
Primary Key | id |
| Useful links |
| Join ad_groups with | on |
|---|---|
| ad_performance_report | ad_groups.id = ad_performance_report.adGroupId |
| adgroup_performance_report | ad_groups.id = adgroup_performance_report.adGroupId |
| age_gender_performance_report | ad_groups.id = age_gender_performance_report.adGroupId |
| geographic_performance_report | ad_groups.id = geographic_performance_report.adGroupId |
| goals_and_funnels_report | ad_groups.id = goals_and_funnels_report.adGroupId |
| keyword_performance_report | ad_groups.id = keyword_performance_report.adGroupId |
| search_query_performance_report | ad_groups.id = search_query_performance_report.adGroupId |
adDistribution STRING | |||
adRotation STRING | |||
biddingScheme STRING | |||
contentMatchBid NUMBER | |||
endDate DATE-TIME | |||
forwardCompatibilityMap ARRAY
| |||
id INTEGER | |||
language STRING | |||
name STRING | |||
nativeBidAdjustment INTEGER | |||
network STRING | |||
pricingModel STRING | |||
remarketingTargetingSetting STRING | |||
searchBid NUMBER | |||
settings ARRAY
| |||
startDate DATE-TIME | |||
status STRING | |||
trackingUrlTemplate STRING | |||
urlCustomParameters ARRAY |
ad_performance_report
Thead_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 aReport table. See theReplication section for information on how data is replicated and loaded for this table.
Append-Only (Incremental) | |
Primary Keys | accountId _sdc_report_datetime gregorianDate |
Replication Key | gregorianDate |
| Useful links |
| Join ad_performance_report with | on |
|---|---|
| accounts | ad_performance_report.accountId = accounts.id |
| adgroup_performance_report | ad_performance_report.accountId = adgroup_performance_report.accountId ad_performance_report.adGroupId = adgroup_performance_report.adGroupId |
| age_gender_performance_report | ad_performance_report.accountId = age_gender_performance_report.accountId ad_performance_report.adGroupId = age_gender_performance_report.adGroupId |
| campaign_performance_report | ad_performance_report.accountId = campaign_performance_report.accountId |
| geographic_performance_report | ad_performance_report.accountId = geographic_performance_report.accountId ad_performance_report.adGroupId = geographic_performance_report.adGroupId |
| goals_and_funnels_report | ad_performance_report.accountId = goals_and_funnels_report.accountId ad_performance_report.adGroupId = goals_and_funnels_report.adGroupId |
| keyword_performance_report | ad_performance_report.accountId = keyword_performance_report.accountId ad_performance_report.adGroupId = keyword_performance_report.adGroupId |
| search_query_performance_report | ad_performance_report.accountId = search_query_performance_report.accountId ad_performance_report.adGroupId = search_query_performance_report.adGroupId |
| ad_groups | ad_performance_report.adGroupId = ad_groups.id |
accountId INTEGER |
adGroupId INTEGER |
adId INTEGER |
campaignId INTEGER |
gregorianDate DATE |
_sdc_report_datetime DATE-TIME |
adgroup_performance_report
Theadgroup_performance_report table contains performance data for ad groups, aggregated by day.
This is aReport table. See theReplication section for information on how data is replicated and loaded for this table.
Append-Only (Incremental) | |
Primary Keys | accountId _sdc_report_datetime gregorianDate |
Replication Key | gregorianDate |
| Useful links |
| Join adgroup_performance_report with | on |
|---|---|
| accounts | adgroup_performance_report.accountId = accounts.id |
| ad_performance_report | adgroup_performance_report.accountId = ad_performance_report.accountId adgroup_performance_report.adGroupId = ad_performance_report.adGroupId |
| age_gender_performance_report | adgroup_performance_report.accountId = age_gender_performance_report.accountId adgroup_performance_report.adGroupId = age_gender_performance_report.adGroupId |
| campaign_performance_report | adgroup_performance_report.accountId = campaign_performance_report.accountId |
| geographic_performance_report | adgroup_performance_report.accountId = geographic_performance_report.accountId adgroup_performance_report.adGroupId = geographic_performance_report.adGroupId |
| goals_and_funnels_report | adgroup_performance_report.accountId = goals_and_funnels_report.accountId adgroup_performance_report.adGroupId = goals_and_funnels_report.adGroupId |
| keyword_performance_report | adgroup_performance_report.accountId = keyword_performance_report.accountId adgroup_performance_report.adGroupId = keyword_performance_report.adGroupId |
| search_query_performance_report | adgroup_performance_report.accountId = search_query_performance_report.accountId adgroup_performance_report.adGroupId = search_query_performance_report.adGroupId |
| ad_groups | adgroup_performance_report.adGroupId = ad_groups.id |
accountId INTEGER |
adGroupId INTEGER |
campaignId INTEGER |
gregorianDate DATE |
_sdc_report_datetime DATE-TIME |
ads
Theads table contains info about the following ad types:
AppInstallDynamicSearchExpandedTextProductTextImage
Full Table | |
Primary Key | id |
| Useful links |
adFormatPreference STRING | |||
devicePreference INTEGER | |||
editorialStatus STRING | |||
finalAppUrls STRING
| |||
finalMobileUrls ARRAY
| |||
finalUrls STRING
| |||
forwardCompatibilityMap ARRAY
| |||
id INTEGER | |||
status STRING | |||
trackingUrlTemplate STRING | |||
type STRING | |||
urlCustomParameters STRING |
age_gender_performance_report
Theage_gender_performance_report table contains info about the age and gender demographics of people interacting with your campaigns and ad groups.
This is aReport table. See theReplication section for information on how data is replicated and loaded for this table.
Append-Only (Incremental) | |
Primary Keys | accountId _sdc_report_datetime gregorianDate |
Replication Key | gregorianDate |
| Useful links |
| Join age_gender_performance_report with | on |
|---|---|
| accounts | age_gender_performance_report.accountId = accounts.id |
| ad_performance_report | age_gender_performance_report.accountId = ad_performance_report.accountId age_gender_performance_report.adGroupId = ad_performance_report.adGroupId |
| adgroup_performance_report | age_gender_performance_report.accountId = adgroup_performance_report.accountId age_gender_performance_report.adGroupId = adgroup_performance_report.adGroupId |
| campaign_performance_report | age_gender_performance_report.accountId = campaign_performance_report.accountId |
| geographic_performance_report | age_gender_performance_report.accountId = geographic_performance_report.accountId age_gender_performance_report.adGroupId = geographic_performance_report.adGroupId |
| goals_and_funnels_report | age_gender_performance_report.accountId = goals_and_funnels_report.accountId age_gender_performance_report.adGroupId = goals_and_funnels_report.adGroupId |
| keyword_performance_report | age_gender_performance_report.accountId = keyword_performance_report.accountId age_gender_performance_report.adGroupId = keyword_performance_report.adGroupId |
| search_query_performance_report | age_gender_performance_report.accountId = search_query_performance_report.accountId age_gender_performance_report.adGroupId = search_query_performance_report.adGroupId |
| ad_groups | age_gender_performance_report.adGroupId = ad_groups.id |
accountId INTEGER |
adGroupId INTEGER |
campaignId INTEGER |
gregorianDate DATE |
_sdc_report_datetime DATE-TIME |
campaign_performance_report
Thecampaign_performance_report table contains performance data for campaigns, aggregated by day..
This is aReport table. See theReplication section for information on how data is replicated and loaded for this table.
Append-Only (Incremental) | |
Primary Keys | accountId _sdc_report_datetime gregorianDate |
Replication Key | gregorianDate |
| Useful links |
| Join campaign_performance_report with | on |
|---|---|
| accounts | campaign_performance_report.accountId = accounts.id |
| ad_performance_report | campaign_performance_report.accountId = ad_performance_report.accountId |
| adgroup_performance_report | campaign_performance_report.accountId = adgroup_performance_report.accountId |
| age_gender_performance_report | campaign_performance_report.accountId = age_gender_performance_report.accountId |
| geographic_performance_report | campaign_performance_report.accountId = geographic_performance_report.accountId |
| goals_and_funnels_report | campaign_performance_report.accountId = goals_and_funnels_report.accountId |
| keyword_performance_report | campaign_performance_report.accountId = keyword_performance_report.accountId |
| search_query_performance_report | campaign_performance_report.accountId = search_query_performance_report.accountId |
accountId INTEGER |
campaignId INTEGER |
gregorianDate DATE |
_sdc_report_datetime DATE-TIME |
campaigns
Thecampaigns table contains info about the campaigns in your Bing Ads account.
Full Table | |
Primary Key | id |
| Useful links |
biddingScheme OBJECT
| |||
budgetId INTEGER | |||
budgetType STRING | |||
campaignType STRING | |||
dailyBudget NUMBER | |||
description STRING | |||
forwardCompatibilityMap ARRAY
| |||
id INTEGER | |||
languages STRING | |||
name STRING | |||
nativeBidAdjustment INTEGER | |||
settings ARRAY
| |||
status STRING | |||
timeZone STRING | |||
trackingUrlTemplate STRING | |||
urlCustomParameters STRING |
geographic_performance_report
Thegeographic_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 aReport table. See theReplication section for information on how data is replicated and loaded for this table.
Append-Only (Incremental) | |
Primary Keys | accountId _sdc_report_datetime gregorianDate |
Replication Key | gregorianDate |
| Useful links |
| Join geographic_performance_report with | on |
|---|---|
| accounts | geographic_performance_report.accountId = accounts.id |
| ad_performance_report | geographic_performance_report.accountId = ad_performance_report.accountId geographic_performance_report.adGroupId = ad_performance_report.adGroupId |
| adgroup_performance_report | geographic_performance_report.accountId = adgroup_performance_report.accountId geographic_performance_report.adGroupId = adgroup_performance_report.adGroupId |
| age_gender_performance_report | geographic_performance_report.accountId = age_gender_performance_report.accountId geographic_performance_report.adGroupId = age_gender_performance_report.adGroupId |
| campaign_performance_report | geographic_performance_report.accountId = campaign_performance_report.accountId |
| goals_and_funnels_report | geographic_performance_report.accountId = goals_and_funnels_report.accountId geographic_performance_report.adGroupId = goals_and_funnels_report.adGroupId |
| keyword_performance_report | geographic_performance_report.accountId = keyword_performance_report.accountId geographic_performance_report.adGroupId = keyword_performance_report.adGroupId |
| search_query_performance_report | geographic_performance_report.accountId = search_query_performance_report.accountId geographic_performance_report.adGroupId = search_query_performance_report.adGroupId |
| ad_groups | geographic_performance_report.adGroupId = ad_groups.id |
accountId INTEGER |
adGroupId INTEGER |
campaignId INTEGER |
gregorianDate DATE |
_sdc_report_datetime DATE-TIME |
goals_and_funnels_report
Thegoals_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 aReport table. See theReplication section for information on how data is replicated and loaded for this table.
Append-Only (Incremental) | |
Primary Keys | accountId _sdc_report_datetime gregorianDate |
Replication Key | gregorianDate |
| Useful links |
| Join goals_and_funnels_report with | on |
|---|---|
| accounts | goals_and_funnels_report.accountId = accounts.id |
| ad_performance_report | goals_and_funnels_report.accountId = ad_performance_report.accountId goals_and_funnels_report.adGroupId = ad_performance_report.adGroupId |
| adgroup_performance_report | goals_and_funnels_report.accountId = adgroup_performance_report.accountId goals_and_funnels_report.adGroupId = adgroup_performance_report.adGroupId |
| age_gender_performance_report | goals_and_funnels_report.accountId = age_gender_performance_report.accountId goals_and_funnels_report.adGroupId = age_gender_performance_report.adGroupId |
| campaign_performance_report | goals_and_funnels_report.accountId = campaign_performance_report.accountId |
| geographic_performance_report | goals_and_funnels_report.accountId = geographic_performance_report.accountId goals_and_funnels_report.adGroupId = geographic_performance_report.adGroupId |
| keyword_performance_report | goals_and_funnels_report.accountId = keyword_performance_report.accountId goals_and_funnels_report.adGroupId = keyword_performance_report.adGroupId |
| search_query_performance_report | goals_and_funnels_report.accountId = search_query_performance_report.accountId goals_and_funnels_report.adGroupId = search_query_performance_report.adGroupId |
| ad_groups | goals_and_funnels_report.adGroupId = ad_groups.id |
accountId INTEGER |
adGroupId INTEGER |
campaignId INTEGER |
gregorianDate DATE |
_sdc_report_datetime DATE-TIME |
keyword_performance_report
Thekeyword_performance_report table contains performance data about keywords.
This is aReport table. See theReplication section for information on how data is replicated and loaded for this table.
Append-Only (Incremental) | |
Primary Keys | accountId _sdc_report_datetime gregorianDate |
Replication Key | gregorianDate |
| Useful links |
| Join keyword_performance_report with | on |
|---|---|
| accounts | keyword_performance_report.accountId = accounts.id |
| ad_performance_report | keyword_performance_report.accountId = ad_performance_report.accountId keyword_performance_report.adGroupId = ad_performance_report.adGroupId |
| adgroup_performance_report | keyword_performance_report.accountId = adgroup_performance_report.accountId keyword_performance_report.adGroupId = adgroup_performance_report.adGroupId |
| age_gender_performance_report | keyword_performance_report.accountId = age_gender_performance_report.accountId keyword_performance_report.adGroupId = age_gender_performance_report.adGroupId |
| campaign_performance_report | keyword_performance_report.accountId = campaign_performance_report.accountId |
| geographic_performance_report | keyword_performance_report.accountId = geographic_performance_report.accountId keyword_performance_report.adGroupId = geographic_performance_report.adGroupId |
| goals_and_funnels_report | keyword_performance_report.accountId = goals_and_funnels_report.accountId keyword_performance_report.adGroupId = goals_and_funnels_report.adGroupId |
| search_query_performance_report | keyword_performance_report.accountId = search_query_performance_report.accountId keyword_performance_report.adGroupId = search_query_performance_report.adGroupId |
| ad_groups | keyword_performance_report.adGroupId = ad_groups.id |
accountId INTEGER |
adGroupId INTEGER |
campaignId INTEGER |
gregorianDate DATE |
_sdc_report_datetime DATE-TIME |
search_query_performance_report
Thesearch_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 thekeyword_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 aReport table. See theReplication section for information on how data is replicated and loaded for this table.
Append-Only (Incremental) | |
Primary Keys | accountId _sdc_report_datetime gregorianDate |
Replication Key | gregorianDate |
| Useful links |
| Join search_query_performance_report with | on |
|---|---|
| accounts | search_query_performance_report.accountId = accounts.id |
| ad_performance_report | search_query_performance_report.accountId = ad_performance_report.accountId search_query_performance_report.adGroupId = ad_performance_report.adGroupId |
| adgroup_performance_report | search_query_performance_report.accountId = adgroup_performance_report.accountId search_query_performance_report.adGroupId = adgroup_performance_report.adGroupId |
| age_gender_performance_report | search_query_performance_report.accountId = age_gender_performance_report.accountId search_query_performance_report.adGroupId = age_gender_performance_report.adGroupId |
| campaign_performance_report | search_query_performance_report.accountId = campaign_performance_report.accountId |
| geographic_performance_report | search_query_performance_report.accountId = geographic_performance_report.accountId search_query_performance_report.adGroupId = geographic_performance_report.adGroupId |
| goals_and_funnels_report | search_query_performance_report.accountId = goals_and_funnels_report.accountId search_query_performance_report.adGroupId = goals_and_funnels_report.adGroupId |
| keyword_performance_report | search_query_performance_report.accountId = keyword_performance_report.accountId search_query_performance_report.adGroupId = keyword_performance_report.adGroupId |
| ad_groups | search_query_performance_report.adGroupId = ad_groups.id |
accountId INTEGER |
adGroupId INTEGER |
campaignId INTEGER |
gregorianDate DATE |
_sdc_report_datetime DATE-TIME |
| Related | Troubleshooting |
Questions? Feedback?
Did this article help? If you have questions or feedback, feel free tosubmit a pull request with your suggestions,open an issue on GitHub, orreach out to us.