# Google ECommerce Information note **Google ECommerce extraction is supported by Stitch** This integration is certified by Stitch. For support, contact [Support](https://community.qlik.com/t5/Support/ct-p/qlikSupport). ## Google ECommerce integration summary Stitch’s Google ECommerce integration replicates data using the [Google Analytics Reporting API v4](https://developers.google.com/analytics/devguides/reporting/core/v4/). Refer to the [Schema](https://help.qlik.com/en-US/stitch/integrations/saas/google-ecommerce#schema) section for a list of objects available for replication. ## Google ECommerce feature snapshot A high-level look at Stitch's Google ECommerce (v15-10-2015) integration, including release status, useful links, and the features supported in Stitch. | **STITCH** | | | | | --- | --- | --- | --- | | **[Release status](https://help.qlik.com/en-US/stitch/integrations/identify-an-integration-version)** | Released on October 15, 2015 | **Supported by**

the Info icon

Indicates if the integration is supported by Stitch or the Singer community. | [Stitch](https://community.qlik.com/t5/Support/ct-p/qlikSupport) | | **Stitch plan**

the Info icon

The type of Stitch plan required to use the integration. | Standard | **[API availability](https://help.qlik.com/en-US/stitch/developers/stitch-connect/guides/source-destination-reference)**

the Info icon

Indicates if the integration is available as a source in Stitch Connect. | the Remove icon

This version of the integration isn't available via the API.


Not available | | **Singer GitHub repository** | Not applicable | | | | **REPLICATION SETTINGS** | | | | | **[Anchor Scheduling](https://help.qlik.com/en-US/stitch/replication/replication-scheduling/anchor-scheduling)**

the Info icon

A type of replication scheduling where an integration's Replication Frequency is anchored to a time you select. | the Success icon

This feature is supported for this version of the integration.


Supported | **[Advanced Scheduling](https://help.qlik.com/en-US/stitch/replication/replication-scheduling/advanced-scheduling)**

the Info icon

A type of replication scheduling that allows you to specify granular start times for data extraction using cron expressions. | the Remove icon

Advanced Scheduling is not supported for this integration.


Unsupported | | **Table-level reset**

the Info icon

Indicates if data can be reset at the table level. If unsupported, data can only be reset at the integration level. | the Remove icon

Table-level resets are not supported for this integration. Resets are only supported at the integration level.


Unsupported | **[Configurable Replication Methods](https://help.qlik.com/en-US/stitch/replication/replication-methods)**

the Info icon

Indicates if Replication Methods can be defined by you for tables in the integration. | the Remove icon

Configurable Replication Methods are not supported for this integration. Stitch will use pre-defined replication methods for tables you set to replicate.


Unsupported | | **DATA SELECTION** | | | | | **Table selection**

the Info icon

The ability to select individual tables for replication in the Stitch interface. If table selection is unavailable, all tables and all the columns they contain will be set to replicate by default. | the Remove icon

Table selection is not supported for this integration. All available table and fields will be automatically selected for replication.


Unsupported | **Column selection**

the Info icon

The ability to select individual columns for replication in the Stitch interface. If column selection is unavailable, all columns will be set to replicate by default. | the Remove icon

Column selection is not supported for this integration. All available columns in tables set to replicate will be selected.


Unsupported | | **Select all**

the Info icon

Indicates if the integration supports selecting all available tables and columns. | the Remove icon

As this integration doesn't support table or column selection, all available tables and columns are automatically replicated.


Unsupported | | | | **TRANSPARENCY** | | | | | **[Extraction Logs](https://help.qlik.com/en-US/stitch/replication/extractions/integration-extraction-logs)**

the Info icon

Logs detailing the Extraction phase of the replication process for a given integration. Includes error info, should an error occur. | the Remove icon

This feature is not supported for this version of the integration.


Unsupported | **[Loading Reports](https://help.qlik.com/en-US/stitch/replication/integration-loading-reports)**

the Info icon

Reports detailing the Loading phase of the replication process for a given integration. Includes the number of rows loaded for each table and error info, should an error occur. | the Success icon

This feature is supported for this version of the integration.


Supported | ## Connecting Google ECommerce ### Google ECommerce setup requirements To set up Google ECommerce 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](https://support.google.com/analytics/answer/2884495?hl=en). * **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 pause all ad-blocking software**. Because Google authentication uses pop ups, you may encounter issues if ad blockers aren’t disabled during the setup. * **To enable the [Enable ECommerce](https://support.google.com/analytics/answer/1009612?hl=en) setting in your Google Analytics account.** If you have ECommerce data in your account, this setting is already enabled and you can move on. ### Step 1: Add Google ECommerce as a Stitch data source 1. [Sign into your Stitch account](https://app.stitchdata.com/). 2. On the Stitch Dashboard page, click the **Add Integration** button. 3. Click the **Google ECommerce** icon. 4. Click **Sign in with Google Analytics.** ### Step 2: Authorize Stitch and select a Google Analytics profile 1. 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.** 2. Click **Allow** to continue. 3. After your credentials are validated, you’ll be prompted to select the Google Analytics profile you want to connect to Stitch: ![Selecting a Google Analytics profile.](https://help.qlik.com/en-US/stitch/images/integrations/ga-select-profiles.png)Selecting a Google Analytics profile.Selecting a Google Analytics profile. **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. 4. When finished, click **Continue** to save the integration and complete the setup. ### Step 3: Create a replication schedule Information note Replication schedules affect the time Extraction begins, not the time to data loaded. Refer to the [Replication Scheduling](https://help.qlik.com/en-US/stitch/replication/replication-scheduling) documentation for more information. In the **Replication Frequency** section, you’ll create the integration’s [replication schedule](https://help.qlik.com/en-US/stitch/replication/replication-scheduling). An integration’s replication schedule determines how often Stitch runs a replication job, and the time that job begins. Google ECommerce integrations support the following replication scheduling methods: * [Replication Frequency](https://help.qlik.com/en-US/stitch/replication/replication-scheduling/replication-frequency) * [Anchor Scheduling](https://help.qlik.com/en-US/stitch/replication/replication-scheduling/anchor-scheduling) To keep your row usage low, consider setting the integration to replicate less frequently. See the [Understanding and Reducing Your Row Usage guide](https://help.qlik.com/en-US/stitch/getting-started/understanding-stitch-usage) for tips on reducing your usage. ### Initial and historical replication jobs After you finish setting up Google ECommerce, 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.** Information note **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](https://help.qlik.com/en-US/stitch/replication/replication-scheduling#job-scheduling-and-anchor-times) 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. Information note **Replication will continue after the seven days are over**. If you’re no longer interested in this source, be sure to **pause** or **delete** the integration to prevent unwanted usage. ## Google ECommerce replication 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 greater row usage. Selecting a lower frequency can help keep your row count low. ## Google ECommerce table reference Information note **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. This is the latest version of the Google ECommerce integration. 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` For example: `ecommerce123456789_v2`. In this case, the profile ID is `123456789` and the version of the ECommerce integration is `2`. Information note **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](https://help.qlik.com/en-US/stitch/replication/loading/destination-guides) for your destination for more info. ### ecommerce\_v2 The `ecommerce_v2` table contains ECommerce data from your Google Analytics account. Refer to the table schema for the metrics and dimensions that are included. | **Replication Method [](https://help.qlik.com/en-US/stitch/replication/replication-methods)[the Info icon](https://help.qlik.com/en-US/stitch/replication/replication-methods)[](https://help.qlik.com/en-US/stitch/replication/replication-methods)** | Key-based Incremental | | --- | --- | | **Primary Keys ![](https://help.qlik.com/en-US/stitch/images/replication/primary-key-icon.svg)** | id | | **Replication Key ![](https://help.qlik.com/en-US/stitch/images/replication/replication-key-icon.svg)** | start-date | ecommerce\_v2 table schema | **accountid**


STRING | | --- | | **campaign**


STRING | | **id**


STRING | | **keyword**


STRING | | **medium**


STRING | | **profileid**


STRING | | **profilename**


STRING | | **socialnetwork**


STRING | | **source**


STRING | | **transactionid**


STRING | | **transactions**


INTEGER |