|Google ECommerce Status Page
|Default Historical Sync
|Default Replication Frequency
|Full Table Endpoints
Connecting Google ECommerce
Connecting your Google ECcommerce data to Stitch is a three-step process:
- Add Google ECcommerce as a Stitch data source
- Authorize Stitch & select a Google Analytics profile
- Define the Replication Frequency
Before you get started, you should verify that:
The user creating the integration has at least Read & Analyze permissions and that there’s data in the account. If the profile you use to connect doesn’t have these permissions (or there’s no data in the account), you’ll receive an error message like this:
“Something went wrong. None of the Google Analytics profiles associated with the credentials you’ve supplied contain data that Stitch can access. Please make sure that the credentials you’ve supplied have appropriate access.”
- All ad-blocking software you are currently using is paused. Because Google authentication uses pop ups, you may encounter issues if ad blockers aren’t disabled during the setup.
- Your account has the Enable ECommerce setting turned on. If you have ECommerce data in your accuont, this setting is already enabled and you can move on.
Add Google ECommerce as a Stitch Data Source
- On the Stitch Dashboard page, click the Add an Integration button.
Click the Google ECommerce icon.
- Click Sign in with Google Analytics.
Authorizing Stitch & Selecting a Google Analytics Profile
- Next, you’ll be prompted to log into your Google account and to approve Stitch’s access to your Google ECommerce data. Note that we will only ever read your 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, we recommend that you double-check the permission settings.
- When finished, click Continue to save the integration and complete the setup.
Define the Replication Frequency
The Replication Frequency controls how often Stitch will attempt to replicate data from your Google ECommerce integration. By default the frequency is set to 30 minutes, but you can change it to better suit your needs.
Before setting the Replication Frequency, note that:
- The more often Google ECommerce is set to replicate, the higher the number of replicated rows.
The number of rows in the source may not equal the number of rows replicated by Stitch. Tables that use Full Table Replication will result in a higher number of replicated rows.
Some or all of the tables in Google ECommerce have an attribution window. This means that during every replication job, the past 15 days’ worth of data will be replicated. See the Replication section below for more details.
- If you’re using a data warehouses that doesn’t natively support nested structures, you’ll see a higher number of replicated rows due to the de-nesting Stitch performs.
To help prevent overages, we recommend setting the Replication Frequency to something less frequent - like 6 hours instead of 30 minutes. For tips on reducing your row count, check out the Reducing Your Row Count section of our Billing Guide.
After selecting a Replication Frequency, click Save Integration.
Google ECommerce’s Intial Sync
After you finish setting up Google ECommerce, you might see its Sync Status 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 sync for the integration. This may take some time to complete.
Replicating Google ECommerce Data
Every time Stitch runs a replication job for Google ECommerce, 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 ECommerce.
Setting the Replication Frequency to a higher frequency - like 30 minutes - can result in re-replicating recent data and contribute to high row counts. Syncing fewer tables or selecting a lower frequency can help prevent overages.
Google ECommerce Schema
After the first successful sync of your Google ECommerce data, you’ll see a single table in your data warehouse. The table follows this naming convention:
ecommerce[GA profile id]_integration version
Here’s an example:
ecommerce123456789_v2. In this case, the profile ID is
123456789 and the version of the ECommerce integration is
In the section below, you’ll find a list of the attributes in this table, a brief description, and links to Google’s more in-depth documentation.
Replication Method: Incremental
Contains Nested Structures?: No
ecommerce123456789_v2 table contains your Google ECommerce data.
Replication & Attribution Windows
Every time a replication job runs for Google ECommerce, the past 15 days' worth of data will be replicated for this table. As a result, you may see a higher number of replicated rows than what's being generated in Google ECommerce.
Stitch replicates data in this way to account for updates made to existing records within Google ECommerce's default attribution window, thus ensuring you won't make decisions based on stale (or false) data.
This table will contain the following attributes. For more info, click the links to check out Google’s documentation.
id) - This column is a unique identifier generated during replication.
accountid - This column contains the account ID associated with your Google Analytics ECommerce account.
profileid - This column contains your Google Analytics profile ID.
profilename - This column contains your Google Analytics profile name.
socialnetwork - This column contains the name of the social network (e.g. Facebook, YouTube, etc.)
transactionid - This column contains the order ID, which you can use to join the referral data back to your orders data. You can refer to Google’s documentation if you need some background on tracking setup and management.
transactions - This column contains the total number of transactions.
Did this article help? If you have questions or feedback, please reach out to us.