This version of Google Analytics (AdWords) reached end of life on December 4, 2017 and is no longer functioning.
Upgrade to the latest version (v05-12-2017) to continue replicating data.
Google Analytics (AdWords) feature snapshot
A high-level look at Stitch's Google Analytics (AdWords) (v15-10-2015) integration, including release status, useful links, and the features supported in Stitch.
STITCH | |||
Release status |
Sunset on December 4, 2017 |
Supported by | |
Stitch plan |
Standard |
API availability |
Not available |
Singer GitHub repository |
Not applicable |
||
REPLICATION SETTINGS | |||
Anchor Scheduling |
Unsupported |
Advanced Scheduling |
Unsupported |
Table-level reset |
Unsupported |
Configurable Replication Methods |
Unsupported |
DATA SELECTION | |||
Table selection |
Unsupported |
Column selection |
Unsupported |
Select all |
Unsupported |
||
TRANSPARENCY | |||
Extraction Logs |
Unsupported |
Loading Reports |
Supported |
Google Analytics (AdWords) replication
Google Analytics (AdWords) Replication and Attribution Windows
Every time Stitch runs a replication job for Google Analytics (AdWords), the last 15 days’ worth of data will be replicated.
This is applicable to all tables in the integration.
Stitch replicates data in this way to account for updates made to existing records within the default attribution window of 15 days, thus ensuring you won’t make decisions based on stale (or false) data. As a result, you may see a higher number of replicated rows than what’s being generated in Google Analytics (AdWords).
Setting the Replication Frequency to a higher frequency - like 30 minutes - can result in re-replicating recent data and contribute to greater row usage. Selecting a lower frequency can help keep your row count low.
Google Analytics (AdWords) 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 for version 15-10-2015 of this integration.
After the first successful sync of your Google Analytics (AdWords) data, you’ll see two tables in your destination. These tables follow this naming convention:
adwords[GA profile id]_integration version
For example: adwords123456789_v2
. In this case, the profile ID is 123456789
and the version of the AdWords integration is 2
.
In the section below, you’ll find a list of the attributes in these tables, a brief description, and links to Google’s more in-depth documentation.
Campaign Names and Primary Keys
Stitch’s Google Analytics (AdWords) integration uses the campaign name (campaign
) as part of the Primary Key for both the adwords
and campaign
tables. Because of this, changing campaign names may lead to data discrepancies.
To account for the name change and resolve any data discrepancies, take the following steps:
- Delete the affected AdWords data from your destination. Feel free to delete the data back to the date of the earliest campaign which was renamed.
- Re-replicate your AdWords data by following these instructions, setting the start date back to the date of the earliest campaign which was renamed. This will reset the integration’s Replication Keys and re-replicate all data back to the integration’s defined Start Date.
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 the Loading Guide for your destination for more info.
adwords123456789_v2
Replication Method : |
Key-based Incremental |
Replication Key |
date |
Primary Key |
campaign : adwordsCampaignId : adGroup : adDestinationUrl : adContent : date : keyword |
Official docs : |
The adwords
table contains daily info about each of your active campaigns and the ads contained within those campaigns.
Note: Google AdWords data is paginated on a daily basis. This means that a single row in each of the tables pertains to a single day.
campaign
The campaign name (utm_campaign) |
adwordsCampaignId
The campaign ID. |
adGroup
The campaign’s ad group name. |
adDestinationUrl
The URL to which AdWords referred traffic. |
adContent
The content description (utm_content) |
date
The timestamp for the date the campaign ran. |
keyword
This column contains the keyword description (utm_term) |
accountId
Your Google Analytics account ID. |
adClicks
The number of clicks for the day. |
adCost
The total cost for the campaign for the day. |
impressions
The number of impressions for the day. |
profileId
Your Google Analytics profile ID. |
profileName
Your Google Analytics profile name. |
campaigns123456789_v2
Replication Method : |
Key-based Incremental |
Replication Key |
date |
Primary Key |
campaign : adwordsCampaignId : date |
Official docs : |
The campaigns
table contains daily info about your AdWords campaigns.
Note: Google AdWords data is paginated on a daily basis. This means that a single row in each of the tables pertains to a single day.
campaign
The name of the campaign (utm_campaign). |
adwordsCampaignId
The campaign ID. |
date
The timestamp for the date the campaign ran. |
accountId
Your Google Analytics account ID. |
adClicks
The number of clicks for the campaign for the day. |
adCost
The total cost for the campaign for the day. |
impressions
The number of impressions for the day. |
profileId
Your Google Analytics profile ID. |
profileName
Your Google Analytics profile name. |
Google Analytics (AdWords) & (not set) Values
According to Google’s documentation:
(not set)
is a placeholder name that Analytics uses when it hasn’t received any information for a dimension.
In general, if (not set)
appears in your Google AdWords reports, it means that the property being tracked in the Analytics account is receiving traffic from an AdWords account that isn’t linked to the reporting view. Follow the tips in the AdWords section of this Google article to troubleshoot and resolve the issue.
Related | Troubleshooting |
Questions? Feedback?
Did this article help? If you have questions or feedback, feel free to submit a pull request with your suggestions, open an issue on GitHub, or reach out to us.