Resources · Make integration

Google Analytics Make integrationAutomate Google Analytics with Make.

Need your Google Analytics numbers somewhere other than the Analytics dashboard? The Google Analytics Make integration gives you 2 modules: one fetches a report, the other reaches any endpoint of the API. This page shows how to link your account and build a first scenario.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Google Analytics Make integration do for you?

The Google Analytics Make integration lets a Make scenario (the automation you build, a chain of steps) read reports from your Google Analytics property without any code. Each step is a module, one brick of the scenario, and this app offers two of them: a report module and an open door to the rest of the API.

A report that travels on its own. Get Analytics Report retrieves a report from a property you already own, and the next module you add can send those results wherever your team works. The report data flows as bundles, one item passed from a module to the next, so any app among the 3,000+ standard ones in Make can receive it.

A request the listed modules do not cover. Make an API Call reuses your Google Analytics connection to reach any endpoint of the Google Analytics API. It is the way forward when the single report module is not enough.

A report started by another app. Since Google Analytics has no trigger in Make, the scenario starts on its own schedule or on an event in another tool, then asks Analytics for the report.

What Make does not do here: watch your property and react to a new visit. There is no trigger, so nothing fires from inside Analytics. Also keep in mind that data received from Google APIs follows the Google API Services User Data Policy when Make passes it to another app.

Google Analytics also has a node in n8n: see the Google Analytics n8n integration and the n8n vs Make comparison. To check plans before you start, read Make pricing.

Connect

How do you connect Google Analytics to Make?

  1. 01

    Open the connection window

    Inside a scenario, add any Google Analytics module and click Create a connection. The connection is your Google account linked to Make once, then reused by both modules of the app.

  2. 02

    Name it and pick your credentials

    The Connection name field is optional, but a clear name helps when several accounts live in the same Make team. If your company uses its own Google Cloud Platform project, switch on Show advanced settings and paste its client credentials.

  3. 03

    Sign in and approve access

    Click Sign in with Google, choose the account that owns the Analytics property, and confirm the access Google asks for. Back in Make, the new connection appears in the module and stays available.

First scenario

Your first scenario with Google Analytics

GoalWhen the scenario runs on its schedule, Make pulls a Google Analytics report, then queries a second endpoint of the API with the same connection.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the big + in the middle of the editor to add the first module.

  2. 02

    Add Get Analytics Report

    Type Google Analytics in the search box, pick Get Analytics Report and select the connection you created earlier, or click Create a connection if this is your first time.

  3. 03

    Point it at your property

    Fill the module fields with your View ID ready. Once the connection works, Make lists what it can read from your account, so there is no need to type every value by hand.

  4. 04

    Chain Make an API Call

    Click the + on the right of the report module, choose Make an API Call and map values from the report into the request. Same Google Analytics connection, nothing new to authorize.

  5. 05

    Test with Run once

    Click Run once. Make executes the scenario a single time and shows the bundles each module received, which is the easiest place to check the report looks right.

  6. 06

    Set the clock and switch on

    Open the clock on the first module: a new scenario runs every 15 minutes by default, and the Free plan cannot go below that. Adjust it, then switch the scenario on.

Modules

What the Google Analytics modules do

Google Analytics gives you 2 modules in 2 groups. For each one: what it does for you, when to reach for it, and what to watch out for.

Actions

1 module
Google Analytics1

Make an API Call

ActionIn the docs only

This module opens the whole Google Analytics API to your scenario, using the connection you already set up, so you reach an endpoint that no ready-made module covers.

When to use it
Get Analytics Report does not return what you need and the Google Analytics API documentation lists an endpoint that does.
Watch out
you write the request yourself, so keep the API documentation open next to the editor and test it with Run once.

Searches

1 module

Note: You must have an existing property in your Google Analytics account to use this module. This module requires a View ID. Follow the steps below to locate it in your Google Analytics property.

Google Analytics2

Get Analytics Report

ActionIn the docs only

Here you get a report from your Google Analytics property handed to the rest of the scenario as bundles, ready to be mapped into a sheet, a message or a CRM record.

When to use it
the figures already exist in Analytics and a colleague keeps asking for them outside the dashboard.
Watch out
the module requires an existing property and its View ID, so find that identifier in the property before building.
Need help

Need help automating Google Analytics with Make?

A person reads every message.

FAQ

Questions about the Google Analytics Make integration

01Is the Google Analytics Make integration free?
Yes. Google Analytics is a standard app, so both modules work from the Make Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams, Enterprise) bring the interval down to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Make counts usage in operations, one execution of one module on one bundle.
02What do you need to connect Google Analytics to Make?
A Google account with access to Google Analytics, and a property that already exists in it. The report module also asks for the View ID of that property, so locate it first. The connection itself runs through the Sign in with Google button. Teams that manage their own Google Cloud Platform project can enter its client credentials under Show advanced settings, but that part is optional. Without it, the standard Google sign-in is all it takes.
03Can Google Analytics trigger a Make scenario in real time?
No. The app has no trigger module in Make, scheduled or instant, so nothing inside Analytics can start a scenario. The usual way is to start the scenario on its own schedule: the clock on the first module runs every 15 minutes by default, with 1 minute as the floor on paid plans. The other option is to open the scenario with a trigger from another app and add Get Analytics Report right after it.
04What if the Google Analytics module you need is missing in Make?
Use Make an API Call. It reuses the same Google Analytics connection and can reach any endpoint of the Google Analytics API, which covers what Get Analytics Report does not. Check the API documentation for the endpoint and test the request with Run once. One limit stays in place whatever the module: data received from Google APIs follows the Google API Services User Data Policy when Make hands it to another app.
05Should you use Make or n8n for Google Analytics?
It depends on the tool your team already runs. Google Analytics exists on both sides: Make offers Get Analytics Report and Make an API Call, and n8n has its own Google Analytics node. Neither choice changes what Google lets you read, since both go through the same API and the same property. This site has a dedicated n8n page for the app and a full comparison of the two tools, both linked earlier on this page.