Pull from Google Analytics

Google Analytics is an events- and session-based analytics service that collects data from websites and apps. Google Analytics 4 properties support privacy controls, such as cookieless measurement, and can be integrated directly on websites and apps to help your brand better understand the customer journey.

Amperity can be configured to pull Google Analytics 4 (GA4) property reports using the batchRunReports endpoint.


Use this data source to build acquisition channel reports.

This topic describes the steps that are required to pull data from websites and apps to Amperity from Google Analytics:

  1. Get details

  2. Configure OAuth for Google Analytics

  3. Add courier

  4. Review feed and domain table

  5. Run courier

  6. Add to courier group

Get details

  1. An account with permission to log in to Google Analytics as a standard administrator. This step is required to configure OAuth.

  2. Your Google Analytics Account ID and Property ID.


    These ID values are available from a dropdown menu in the configuration for this data source after it has been configured to use OAuth.

Configure OAuth

OAuth is an open standard for access delegation, commonly used to grant websites or applications access to information on other websites.

To configure OAuth

  1. Select the    menu next to your tenant name in the top navigation, and then select Credentials.

  2. On the Credentials page, click Add credential. This opens the Create New Credential page.

  3. From the Plugin dropdown, select Google Analytics 4, and then enter a name and description for this connector.

  4. Generate an authorization link, and then visit the URL that was generated to complete the authorization process.

Add courier

A courier brings data from an external system to Amperity.

To add a courier

  1. From the Sources page, click Add Courier. The Add Source page opens.

  2. Find, and then click the icon for Google Analytics 4. The Add Courier page opens.

    Select google-analytics-4 as the Credential Type.

  3. Select the user account you added when configuring OAuth. The Refresh token should populate automatically.

  4. Click Continue.

  5. Under Google Analytics 4 Settings, select the Account ID, and then the Property ID.

  6. Under Select Data to Ingest select Transactional Analytics 4.

  7. Click Create.

Review feed and domain table

After creating the Google Analytics courier it will create a source named Google Analytics and a feed named Transactional Analytics that contains the fields that Amperity pulls from the configured Google Analytics 4 property.

The following fields will be available:

  • itemRevenue

  • transactionId (assigned the pk semantic tag)

  • browser

  • sessionCampaignName

  • sessionSource

  • sessionGoogleAdsAdGroupName

  • date

  • deviceCategory

  • operatingSystem

  • sessionGoogleAdsQuery

  • operatingSystemVersion

  • sessionMedium

  • sessionGoogleAdsAdGroupId


The Transactional Analytics feed for Google Analytics cannot be edited and should not be made available to Stitch.

Run courier manually

Run the courier again. This time, because the load operations are present and the feeds are configured, the courier will pull data from Google Analytics.

To run the courier manually

  1. From the Sources tab, open the    menu for the courier with updated load operations that is configured for Google Analytics, and then select Run. The Run Courier dialog box opens.

  2. Select the load option, either for a specific time period or all available data. Actual data will be loaded to a domain table because the feed is configured.

  3. Click Run.

    This time the notification will return a message similar to:

    Completed in 5 minutes 12 seconds

Add to courier group

A courier group is a list of one (or more) couriers that are run as a group, either ad hoc or as part of an automated schedule. A courier group can be configured to act as a constraint on downstream workflows.

To add the courier to a courier group

  1. From the Sources tab, click Add Courier Group. This opens the Create Courier Group dialog box.

  2. Enter the name of the courier. For example: “Google Analytics”.

  3. Add a cron string to the Schedule field to define a schedule for the orchestration group.

    A schedule defines the frequency at which a courier group runs. All couriers in the same courier group run as a unit and all tasks must complete before a downstream process can be started. The schedule is defined using cron.

    Cron syntax specifies the fixed time, date, or interval at which cron will run. Each line represents a job, and is defined like this:

    ┌───────── minute (0 - 59)
    │ ┌─────────── hour (0 - 23)
    │ │ ┌───────────── day of the month (1 - 31)
    │ │ │ ┌────────────── month (1 - 12)
    │ │ │ │ ┌─────────────── day of the week (0 - 6) (Sunday to Saturday)
    │ │ │ │ │
    │ │ │ │ │
    │ │ │ │ │
    * * * * * command to execute

    For example, 30 8 * * * represents “run at 8:30 AM every day” and 30 8 * * 0 represents “run at 8:30 AM every Sunday”. Amperity validates your cron syntax and shows you the results. You may also use crontab guru to validate cron syntax.

  4. Set Status to Enabled.

  5. Specify a time zone.

    A courier group schedule is associated with a time zone. The time zone determines the point at which a courier group’s scheduled start time begins. A time zone should be aligned with the time zone of system from which the data is being pulled.


    The time zone that is chosen for an courier group schedule should consider every downstream business processes that requires the data and also the time zone(s) in which the consumers of that data will operate.

  6. Add at least one courier to the courier group. Select the name of the courier from the Courier drop-down. Click + Add Courier to add more couriers.

  7. Click Add a courier group constraint, and then select a courier group from the drop-down list.

    A wait time is a constraint placed on a courier group that defines an extended time window for data to be made available at the source location.

    A courier group typically runs on an automated schedule that expects customer data to be available at the source location within a defined time window. However, in some cases, the customer data may be delayed and isn’t made available within that time window.

  8. For each courier group constraint, apply any offsets.

    An offset is a constraint placed on a courier group that defines a range of time that is older than the scheduled time, within which a courier group will accept customer data as valid for the current job. Offset times are in UTC.

    A courier group offset is typically set to be 24 hours. For example, it’s possible for customer data to be generated with a correct file name and datestamp appended to it, but for that datestamp to represent the previous day because of the customer’s own workflow. An offset ensures that the data at the source location is recognized by the courier as the correct data source.


    An offset affects couriers in a courier group whether or not they run on a schedule. Manually run courier groups will not take their schedule into consideration when determining the date range; only the provided input day(s) to load data from are used as inputs.

  9. Click Save.