This integration is certified by Stitch. For support, contact Stitch support.
Google Analytics (AdWords) integration summary
Note: This guide describes how to replicate Google AdWords data using Stitch’s Google Analytics integration. Additionally, this approach replaces the deprecated 15-10-2015 version of Stitch’s Google Analytics (AdWords) integration.
As this approach uses the Analytics API, there may be some differences in the data when compared between AdWords and Analytics. You can find out more about these differences in Google’s documentation.
If you want to use the AdWords API, use Stitch’s Google AdWords integration.
Google Analytics (AdWords) feature snapshot
A high-level look at Stitch's Google Analytics (AdWords) (v05-12-2017) integration, including release status, useful links, and the features supported in Stitch.
Released on December 5, 2017
|Singer GitHub repository||
|Configurable Replication Methods||
Connecting Google Analytics (AdWords)
Google Analytics (AdWords) setup requirements
To set up Google Analytics (AdWords) in Stitch, you need:
At least Read & Analyze permissions in the account you want to connect to Stitch. See Google’s documentation for more info.
To have recent data in the account you want to connect to Stitch. Verify that there is data from the past 30 days in the account before continuing.
To link your AdWords and Google Analytics profiles. See Google’s documentation for instructions.
To pause any ad-blocking software. Ad blockers can interfere with pop-ups, which are used in Google authorization and may prevent authorization from successfully completing.
Step 1: Add Google Analytics (AdWords) as a Stitch data source
- Sign into your Stitch account.
On the Stitch Dashboard page, click the Add Integration button.
Click the Google Analytics icon.
Enter a name for the integration. This is the name that will display on the Stitch Dashboard for the integration; it’ll also be used to create the schema in your destination.
For example, the name “Stitch Google Analytics AdWords” would create a schema called
stitch_google_analytics_adwordsin the destination. Note: Schema names cannot be changed after you save the integration.
Step 2: Define the historical replication start date
The Sync Historical Data setting defines the starting date for your Google Analytics (AdWords) integration. This means that data equal to or newer than this date will be replicated to your data warehouse.
Change this setting if you want to replicate data beyond Google Analytics (AdWords)’s default setting of 30 days. For a detailed look at historical replication jobs, check out the Syncing Historical SaaS Data guide.
Step 3: Create a replication schedule
In the Replication Frequency section, you’ll create the integration’s replication schedule. An integration’s replication schedule determines how often Stitch runs a replication job, and the time that job begins.
Google Analytics (AdWords) integrations support the following replication scheduling methods:
To keep your row usage low, consider setting the integration to replicate less frequently. See the Understanding and Reducing Your Row Usage guide for tips on reducing your usage.
Step 4: Authorize Stitch and select a Google Analytics (AdWords) profile
- Next, you’ll be prompted to log into your Google account and to approve Stitch’s access to your Google AdWords data.
- Click Allow to continue.
After your credentials are validated, you’ll be prompted to select the Google Analytics profile you want to connect to Stitch:
Remember: Profiles need to have Read & Analyze permissions to be detected by Stitch. If you don’t see the profile you want in this list, double-check the permission settings of the profile.
- When finished, click Continue to save the integration.
Step 5: Select Metrics and Dimensions
After you grant Stitch access to your Google Analytics profile, you can select Google Analytics (AdWords) Metrics and Dimensions you want to replicate to your destination.
Before you make your selections, note that:
The following instructions use the Metrics and Dimensions that a deprecated version of Stitch’s Google AdWords integration replicated. You can select other Metrics or Dimensions, but we’re listing them here for those who may want to mimic the old integration.
Metric/Dimension combinations must comply with Google’s compatibility rules before the integration can be saved. Stitch will check the validity of your selections as you go and notify you if something isn’t allowed. Google’s Dimensions & Metrics Explorer can be used to validate different combinations before you enter them in Stitch.
Google limits the number of Metrics and Dimensions you can select. You can select up to 10 Metrics and seven Dimensions per integration. Refer to Google’s documentation for more info on these limits.
Metric/Dimension combinations can’t be changed after the integration is saved. The Primary Key Stitch will create is a composite key composed of the Dimensions selected during this step.
Refer to Google’s documentation for more info about Google AdWords Metrics and Dimensions.
Choose your data
To complete the setup, you’ll select the Metrics and Dimensions you want to replicate.
In the Choose Metrics field, select up to 10 Metrics to replicate.
If you want to replicate the same Metrics as Stitch’s old Google AdWords integration, select the following:
In the Choose Dimensions field, select up to seven Dimensions to replicate.
If you want to replicate the same Dimensions as Stitch’s old Google AdWords integration, select the following:
- As you add Metrics and Dimensions, Stitch will check them for recent data and compatibility according to Google’s compatibility rules. To be considered recent, data must be from the past 30 days.
- Review your selections. Remember: Metrics/Dimensions cannot be added or removed after the integration is saved.
- When finished, click Save Integration.
Initial and historical replication jobs
After you finish setting up Google Analytics (AdWords), its Sync Status may show as Pending on either the Stitch Dashboard or in the Integration Details page.
For a new integration, a Pending status indicates that Stitch is in the process of scheduling the initial replication job for the integration. This may take some time to complete.
Initial replication jobs with Anchor Scheduling
If using Anchor Scheduling, an initial replication job may not kick off immediately. This depends on the selected Replication Frequency and Anchor Time. Refer to the Anchor Scheduling documentation for more information.
Free historical data loads
The first seven days of replication, beginning when data is first replicated, are free. Rows replicated from the new integration during this time won’t count towards your quota. Stitch offers this as a way of testing new integrations, measuring usage, and ensuring historical data volumes don’t quickly consume your quota.
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 05-12-2017 of this integration.
This is the latest version of the Google Analytics (AdWords) integration.
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), while case is maintained in PostgreSQL destinations (
CusTomERs). Refer to the Loading Guide for your destination for more info.
|Replication Method :||
|Replication Key :||
|Primary Key :||
adContent : adDestinationUrl : adGroup : adwordsCampaignId : campaign : date : start_date : end_date : keyword
|Official docs :|
report table contains info about your active campaigns and the ads contained within those campaigns.
Note: The attributes in this table are dependent upon the Metrics and Dimensions selected during setup. The schema shown below uses the Metrics and Dimensions from an older version of Stitch’s Google AdWords integration.
Table Rows and Data Pagination
Google AdWords data is paginated on a daily basis. This means a single row in the table pertains to a specific day. The
end_date columns, which will contain identical values, indicate the day the row is for.
For example: If
end_date contain the value
2017-12-12 00:00:00, the row contains data for December 12, 2017.
The content description (utm_content).
The URL to which AdWords referred traffic.
The campaign’s ad group name.
The campaign ID.
The campaign name (utm_campaign).
The date the campaign ran.
The date the data in the row pertains to.
The date the data in the row pertains to.
The keyword description (utm_term).
The number of clicks for the campaign for the day.
The total cost for the campaign for the day.
The number of impressions for the day.
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.