Come collegare Google Analytics a Excel - Interrogazione di Web Analytics con SQL

Connetti · GA4 a Excel

Ottieni i dati da GA4 in Excel

Importa i dati in tempo reale dal tuo account GA4 in Excel e aggiornali quando vuoi. Nessun driver ODBC, nessuna esportazione, nessuna macro. La prima volta bastano circa dieci minuti, ed è incluso nel piano gratuito.

Circa 10 minuti Non è necessaria alcuna programmazione. Le credenziali restano con te Eccelli ovunque, anche sul web.

Quello che otterrai alla fine

Un foglio di lavoro che mostra i risultati in tempo reale di una query SQL sul tuo account GA4, con un pulsante che visualizza le righe più recenti ogni volta che i dati cambiano. Ad esempio:

Vendite.xlsx — Excel

CasaInserisciDatiFlussi di query

	A	B	C	D	E
1	ID cliente	nome di battesimo	cognome	Paese	totale
2	1042	Maria	Alvarez	U.S.A.	1,284.50
3	1043	Daniel	Okafor	U.S.A.	612.00
4	1047	Priya	Nair	U.S.A.	2,090.75
5	1051	Tommaso	Berg	U.S.A.	338.20
6	1056	Lucia	Ferreira	U.S.A.	1,455.00
7	1060	Kenji	Sato	U.S.A.	874.10
8

Foglio1 In diretta da GA4

Google Analytics 4 protegge i tuoi dati tramite la sua API. Importarli in Excel solitamente significa esportare un file CSV dalla dashboard di GA4 ogni volta che hai bisogno di dati aggiornati. Query Streams elimina questo passaggio: un piccolo programma di supporto chiamato Agent esegue la query direttamente dove si trovano i tuoi dati e un componente aggiuntivo di Excel richiede le righe desiderate. Solo i risultati vengono trasmessi, tramite un collegamento crittografato, e Excel può trovarsi ovunque: sul tuo laptop a casa, sul computer di un collega dall'altra parte del paese o su Excel sul web.

Cosa ti servirà

Un account Query Streams

Il piano gratuito è sufficiente per questa guida. Registrati su my.querystreams.com.

L'agente su qualsiasi computer sempre acceso

Un piccolo programma che viene eseguito in background e richiama GA4 quando Excel lo richiede. Richiede solo una connessione a Internet.

Le tue credenziali di accesso GA4

Dovrai accedere a GA4 una sola volta e consentire l'accesso in lettura. Non è necessario inserire password in Query Streams.

Collegalo in cinque passaggi

1. Crea il tuo account

   Vai a my.querystreams.com e iscriviti. Scegli il Gratuito piano. Si tratta di un piano reale, non di una versione di prova, che include la connessione al tuo account GA4 e l'esecuzione di query da Excel.

2. Installa l'agente su qualsiasi computer sempre acceso.

   Accedi, apri Scaricamentoe installa l'agente su qualsiasi computer o server sempre acceso con accesso a Internet. L'operazione richiede un minuto e da quel momento in poi si avvia automaticamente.

   Perché un piccolo programma invece di un driver? L'Agent è un'unica installazione per Windows, Mac o Linux (circa 85 MB su Windows, poco più di 100 MB su Mac e Linux) che funziona silenziosamente in background. Stabilisce una connessione in uscita crittografata con Query Streams, nello stesso modo di un browser, quindi non è necessario aprire porte del firewall né configurare una VPN. Le chiavi rimangono sul computer e le righe vengono inviate ovunque vi troviate, anche tramite Internet se necessario. L'unico elemento che dovete gestire è il componente aggiuntivo.

   La pagina di download mostra La tua chiave di accesso. Incollalo nell'Agente quando richiesto e attendi che il badge venga letto Connesso ai flussi di queryQuesta è l'unica operazione che si esegue sull'agente stesso.

   Se volete, potete trovare le guide complete: Finestre, Mac, Linux.

3. Collegalo al tuo account GA4

   Torna al tuo browser, apri Agenti dati (Sotto Dati nel menu in alto). Il tuo agente è elencato lì. Fai clic Aggiungi connettore e scegliere Google Analytics 4. Need your GA4 credentials first? Open the walkthrough, then fill in:

   Create your GA4 credentials (about 15 minutes)

   Follow this with Google Analytics 4 open in another tab. Query Streams keeps what you create here so your Agent can use it, and only ever reads from Google Analytics 4.

   Who can do this

   Google Analytics: Administrator on the GA4 property or its account (needed to add the service account). Google Cloud: Owner of the project (you are Owner of any project you create), or the Create Service Accounts, Service Account Key Admin and Service Usage Admin roles on it.

   Raccomandato

   Google Cloud service account JSON key (a .json file of type service_account), with the service account added as Viewer on the GA4 property

   Prima di iniziare

   • A GA4 property. Its Property ID is a plain number. A UA- tracking ID means an old Universal Analytics property, which Google’s API can’t read.
   • A Google account with the Administrator role on that GA4 property. If you don’t have it, you can do the Google Cloud part (steps 1 to 13) and ask an Administrator to do steps 14 to 19.
   • A Google Cloud project you can manage, or permission to create one. If your company’s Google Cloud organization was created on or after May 3, 2024, Google blocks key downloads by default and your Google Cloud administrator may need to allow it (see Common problems).
   • The Query Streams wizard open in another tab (Data Agents → Add connector → Google Analytics 4) with your Agent online.

   Steps

   1. Open the New Project page in Google Cloud

      Sign in with your Google account and open the Google Cloud New Project page.

      Already have a Google Cloud project you want to use? Skip to step 3 and pick it there. The first time you open Google Cloud, Google may ask for your country and for you to accept its Terms of Service before it shows the page.

   2. Name and create the project

      In Project name, type a name such as Query Streams GA4. Leave the organization or location box as Google fills it in (No organization is fine). Click Create.

      Google does not need a billing account to create the project. Creating it takes a few seconds to a minute.

   3. Select the project

      Click the project picker at the top of the page, next to the Google Cloud logo, and click your project’s name. Every Google Cloud step below happens in this project.

      The most common mistake is enabling the API in one project and creating the key in another. Check the project name at the top of the page before each Google Cloud step.

   4. Enable the Google Analytics Data API

      Open the Google Analytics Data API page in the API Library. Check that your project’s name shows at the top, then click Enable.

      Pick Google Analytics Data API, not Google Analytics Reporting API, which only works with old Universal Analytics properties. If the button says Manage instead of Enable, the API is already on. This one API also serves GA4’s realtime report, so there is nothing extra to enable for the realtime_active_users table.

   5. Enable the Google Analytics Admin API (recommended)

      Open the Google Analytics Admin API page in the API Library and click Enable.

      Syncing doesn’t need this API. It powers the Detect button next to GA4 Property ID in the Query Streams wizard, which lists the properties the service account can see. Skip it if you will type the Property ID yourself.

   6. Start a service account

      Open the Service accounts page. From inside Google Cloud you can also open the Navigation menu (three lines, top left) and choose IAM & Admin → Service Accounts. Click + Create service account.

      Already made a service account for Query Streams’ Google Search Console connector? You can use it here too: do steps 4 and 5 in its project, then go to step 14 with its email and key.

   7. Name the service account

      In Service account name, type query-streams-ga4. Google fills in Service account ID from it. The description is optional. Click Create and continue.

      The ID can’t be changed later. It becomes the first part of the service account’s email address.

   8. Skip the project roles

      The next section offers roles on the project. Leave the role box empty and click Continue.

      Don’t give the service account Owner, Editor or Viewer here. Its access to Google Analytics is granted inside Google Analytics in step 18. A project role does nothing in Google Analytics and only widens what the key can do in Google Cloud.

   9. Finish creating the service account

      Leave the last section (people who can use or manage the service account) empty and click Done. You are back on the Service accounts list.

   10. Copy the service account email

       In the list, find the new account. Its email looks like [email protected]. Copy it and keep it for step 17.

       Copy the whole address, through .iam.gserviceaccount.com. A new service account can take a minute or more before it is usable.

   11. Open the Keys tab

       Click the service account’s email address, then click the Keys tab.

   12. Start a new key

       Click Add key, then choose Create new key.

       If Google says Service account key creation is disabled, your organization blocks key downloads. See Common problems.

   13. Download the JSON key

       Choose JSON as the key type and click Create. Your browser downloads a .json file named after your project, usually into your Downloads folder.

       This download happens once: Google keeps no copy, and you can’t download the file again. If you lose it, create a new key and delete the old one. Don’t choose P12. Keep the file private. Don’t email it or put it in a shared folder, because anyone who has it can read your Analytics data. Query Streams stores it for your Agent and only ever reads with it.

   14. Open Google Analytics Admin

       Open Google Analytics and click Admin (the gear icon at the bottom left). At the top of the page, check that the account and property picker shows the GA4 property you want to read.

       To add users you need the Administrator role on this property or its account. If you don’t have it, send the email from step 10 to someone who does and ask them to do steps 15 to 19.

   15. Open Property access management

       Under Property settings, in the Property group, click Property access management.

       Use Property access management, not Account access management. Access added at account level reaches every property in the account.

   16. Add a user

       Click the blue + button at the top right and choose Add users.

   17. Enter the service account email

       Paste the service account email from step 10 into the email box. Untick Notify new users by email.

       Nobody reads that address’s inbox, so there is no point notifying it. If GA4 answers This email doesn’t match a Google Account or Failed to add user: email not found, see Common problems. Google has had a known problem with newly created service accounts since April 2026, and waiting a few hours has fixed it for many people.

   18. Choose the Viewer role

       In the role list, choose Viewer. Leave the data restrictions No Cost Metrics and No Revenue Metrics unticked.

       Viewer is enough, because Query Streams only reads reports. With No Revenue Metrics ticked, Google returns 0 in every revenue column of the ecommerce_overview and transactions tables.

   19. Add the service account

       Click Add at the top right. The service account now appears in the property’s user list with the Viewer role.

       Some screens label this button Create.

   20. Copy the Property ID

       Go back to Admin. Under Property settings, in the Property group, click Property details. At the top right, PROPERTY ID shows a number such as 486480978. Click the copy icon next to it.

       Use this number, not the Measurement ID (which starts with G-) and not the Account ID. The same number appears in the GA4 address bar after the letter p, for example …/p486480978/….

   21. Copy the whole key file

       Open the .json file from step 13 in a plain text editor. On Windows, right-click the file and choose Open with → Notepad. On a Mac, Control-click it and choose Open With → TextEdit. Press Ctrl+A, then Ctrl+C (Cmd+A, then Cmd+C on a Mac).

       Copy everything from the first { to the last }. Don’t retype or tidy any part of it. The private_key line must stay exactly as Google wrote it.

   Permissions to grant

   Resource	Accesso	Used for
   Google Analytics property role: Viewer (Property access management)	Spettatore	Every ga4 table: traffic_overview, traffic_sources, geographic_data, page_views, user_engagement, events, ecommerce_overview, transactions and realtime_active_users. Test connection also reads the property’s field list with it.
   Data restriction: No Revenue Metrics	Unticked	Revenue columns in ecommerce_overview (purchase_revenue, total_revenue, average_purchase_revenue) and transactions (item_revenue). When ticked, Google returns 0 in them.
   Data restriction: No Cost Metrics	Unticked (recommended)	No current Query Streams table reads cost metrics, so this one does no harm today. Leaving it unticked keeps any cost data readable.
   Google Cloud API: Google Analytics Data API	Enabled	Every ga4 table and Test connection. The realtime report behind realtime_active_users is part of the same API.
   Google Cloud API: Google Analytics Admin API	Enabled (optional)	Only the Detect button next to GA4 Property ID, which lists the properties the service account can see. No table reads it.
   Google Cloud project role for the service account	Nessuno	Not needed for any table. Google Analytics access comes only from the Viewer role above.
   OAuth scope https://www.googleapis.com/auth/analytics.readonly	Requested by the Agent (nothing for you to set)	Every ga4 table, Test connection and Detect. It is Google’s read-only Analytics scope, so the key can’t change anything in Google Analytics.

   Paste into Query Streams

   Chiave JSON dell'account di servizio

   The whole contents of the .json file you copied in step 21, from the first { to the last }. When you edit a connector later, leave this box blank to keep the stored key, or paste a whole new file to replace it.

   ID proprietà GA4

   The number you copied in step 20, digits only (for example 486480978). Or click Detect next to the box and pick your property from the list. Detect needs the Admin API from step 5 and an Agent that is online.

   Common problems

   Test connection fails with Invalid key type. Expected ‘service_account’.

   Why: The pasted file is not a service account key. Usually it is an OAuth client file (named like client_secret_….json) or an API key from APIs & Services → Credentials.

   Fix: Create a JSON key on the service account (steps 11 to 13) and paste that file. A service account key contains the line “type”: “service_account”.

   Test connection fails with Invalid JSON format, or with Missing or empty ‘private_key’ field.

   Why: Only part of the file was copied, or the text was changed while copying.

   Fix: Open the file again in Notepad or TextEdit, press Ctrl+A (Cmd+A on a Mac), copy, and paste it into Service Account JSON Key with nothing before or after it.

   Test connection fails with Forbidden – User does not have sufficient permissions for this property.

   Why: The service account was not added to this property, was added to a different property, or the Property ID belongs to another property. It also happens for a few minutes right after you add the service account.

   Fix: Open the property whose Property details show the same Property ID and check that the service account email is listed in Property access management with Viewer (steps 14 to 19). Wait 5 to 10 minutes, then click Test again.

   Test connection fails with a Forbidden message saying Google Analytics Data API has not been used in project … before or it is disabled.

   Why: The Data API is not enabled in the Google Cloud project the key belongs to. The project is named in the key file’s project_id line.

   Fix: Select that project in Google Cloud, enable Google Analytics Data API (step 4), wait a few minutes, and click Test again.

   Test connection fails with Invalid Property ID format: ‘G-…’. Should be numeric, or with Property ‘…’ not found.

   Why: The Measurement ID (G-…), an old UA- tracking ID, or a mistyped number was entered instead of the Property ID.

   Fix: Copy the number shown under PROPERTY ID on the Property details page (step 20) and paste it into GA4 Property ID.

   Google Analytics won’t accept the service account email: This email doesn’t match a Google Account, or Failed to add user: email not found.

   Why: A known Google problem: since late April 2026, GA4 and Search Console sometimes don’t recognise newly created service accounts for a while. Reports continued into September 2026. A typo or a space in the address causes the same message.

   Fix: Paste the address again with no spaces. If it is still refused, wait a few hours and try again. A service account created earlier usually works, so if you have one, create a new key for it (steps 11 to 13) and add that email instead. An administrator who is comfortable with Google’s API Explorer can also add the service account with the Admin API’s accessBindings.create method and the role predefinedRoles/viewer.

   Google Cloud shows Service account key creation is disabled when you click Create new key.

   Why: Your organization enforces the policy iam.disableServiceAccountKeyCreation. Google turns it on by default for organizations created on or after May 3, 2024.

   Fix: Ask your Google Cloud administrator (someone with the Organization Policy Administrator role) to allow key creation for this project or service account. Google documents a tag-based exemption for one project or service account. Then repeat steps 12 and 13.

   Detect says No GA4 properties found, or reports that the Google Analytics Admin API has not been used in the project.

   Why: The Admin API is not enabled (step 5), or the service account has not been added to any property yet.

   Fix: Enable the Admin API and finish steps 14 to 19, then click Detect again. You can always type the Property ID yourself instead.

   The ecommerce_overview and transactions tables sync, but every revenue column is 0.

   Why: The service account was added with the No Revenue Metrics data restriction.

   Fix: In Property access management, open the service account’s entry, untick No Revenue Metrics and save. The next sync reads the real values.

   A connector that used to work stops syncing, with an error that mentions invalid_grant or Invalid JWT Signature.

   Why: The key was deleted or disabled in Google Cloud. Google also disables keys it finds exposed in public.

   Fix: Create a new key (steps 11 to 13). In Query Streams, open the connector in Data Agents, click Edit, paste the whole new file into Service Account JSON Key, click Test connection, then click Save changes. Delete the old key in Google Cloud.

   Syncs fail with 429 or RESOURCE_EXHAUSTED.

   Why: The property used up its Google Analytics API quota. Every app that reads this property through the API draws on the same per-property quota.

   Fix: Wait: hourly quota refills within an hour, and daily quota resets at midnight Pacific Time. Turn off tables you don’t use, or sync them less often.

   You want Query Streams to stop reading this property.

   Why: Deleting the connector does not remove Google’s access. The service account stays a Viewer and the key stays valid.

   Fix: In Property access management, remove the service account. In Google Cloud, open the service account’s Keys tab and delete the key. Then delete the connector in Data Agents.

   Limits to know

   • Data freshness: GA4 can take 24 to 48 hours to finish processing a day, and figures for recent days can change after that. Each sync of the daily tables re-reads the last 3 days, so late numbers fill in on their own. Realtime data arrives within minutes.
   • Realtime window: GA4’s realtime report covers only the last 30 minutes (60 minutes on Analytics 360). The realtime_active_users table is a snapshot that each refresh replaces (every 5 minutes by default), not a history. It uses the same API, key and Viewer access as the other tables, with its own separate Realtime quota.
   • API quota for a standard property: 200,000 tokens per day and 40,000 per hour for the whole property, 14,000 per hour from one Google Cloud project, and 10 requests at a time. Most requests cost 10 tokens or fewer. Analytics 360 properties get 10 times these limits. Daily quota resets at midnight Pacific Time.
   • History: the first sync asks for everything since October 2020, when GA4 launched. Google returns data only from when your property started collecting. Universal Analytics (UA-) properties can’t be read through this API.
   • One property per connector: the Property ID selects one GA4 property. To read another property, add the same service account to it as Viewer and create a second connector. The same key works for both.
   • Keys: a service account key never expires unless your organization sets a maximum lifetime. Each service account can have up to 10 keys, and the key file can be downloaded only once.
   • Data restrictions: if the service account has No Revenue Metrics or No Cost Metrics, Google returns 0 for those metrics instead of an error.

   Steps verified 8 October 2026. Sources: developers.google.com/analytics/devguides/reporting/data/v1, developers.google.com/analytics/devguides/reporting/data/…, developers.google.com/analytics/devguides/reporting/data/…, developers.google.com/analytics/devguides/reporting/data/…, developers.google.com/analytics/devguides/reporting/data/…, developers.google.com/analytics/devguides/reporting/data/…, developers.google.com/analytics/devguides/reporting/data/…, developers.google.com/analytics/devguides/reporting/data/…, developers.google.com/analytics/devguides/reporting/data/…, developers.google.com/analytics/devguides/config/admin/v1…, developers.google.com/analytics/devguides/config/admin/v1…, developers.google.com/analytics/devguides/config/admin/v1…, developers.google.com/workspace/guides/create-project, docs.cloud.google.com/resource-manager/docs/creating-mana…, docs.cloud.google.com/service-usage/docs/enable-disable, docs.cloud.google.com/iam/docs/service-accounts-create, docs.cloud.google.com/iam/docs/keys-create-delete, docs.cloud.google.com/iam/docs/service-account-creds, docs.cloud.google.com/iam/docs/troubleshoot-org-policies, docs.cloud.google.com/iam/docs/best-practices-for-managin…, support.google.com/googleapi/answer/6158841?hl=en, support.google.com/analytics/answer/9305788?hl=en, support.google.com/analytics/answer/9305587?hl=en, support.google.com/analytics/answer/9304776?hl=en, support.google.com/analytics/answer/11198161?hl=en, docs.ovhcloud.com/en/guides/public-cloud/data-platform/co…, windsor.ai/documentation/how-to-connect-ga4-to-windsor-ai…, seopress.org/support/guides/find-my-google-analytics-4-pr…, analytify.io/add-user-to-google-analytics, optimizesmart.com/blog/google-analytics-4-measurement-id-…, discuss.google.dev/t/problem-with-new-service-accounts/36…, piunikaweb.com/2026/05/01/google-service-account-email-no…, sanj.dev/post/google-analytics-search-console-service-acc…, oneuptime.com/blog/post/2026-01-24-gcp-service-account-ke…, help.genesys.cloud/articles/data-action-returns-a-400-error.

   Nome della società

   Un nome che riconoscerai in seguito, come ad esempio "Database delle vendite".

   Chiave JSON dell'account di servizio

   Incolla il contenuto del file chiave per un account di servizio Google che è stato aggiunto come visualizzatore sulla tua proprietà GA4.

   ID proprietà GA4

   Il numero che identifica la tua proprietà GA4, che si trova nell'area di amministrazione di GA4 alla voce Impostazioni proprietà, ad esempio 486480978.

   Cliccare Verifica la connessioneQuando legge Collegato, clicca RisparmiareLa connessione raggiunge il tuo agente in pochi secondi.

   Agenti di dati aperti

   Test fallito? Usually a missing permission, or a credential from the wrong GA4 account. The walkthrough above lists the common problems and their fixes.

4. Aggiungere flussi di query a Excel

   In Excel, vai a Inserisci → Ottieni componenti aggiuntivi, cerca Flussi di querye clicca AggiungiOppure aprilo direttamente da Query Streams su Microsoft AppSourceSul ripiano multifunzione compare il pulsante Query Streams. Accedi con lo stesso account.

   Funziona con Excel per Microsoft 365 su Windows e Mac, e con Excel sul web.

5. Porta il tuo primo tavolo

   Fai clic sul pulsante Query Streams, scegli Trasmetti una querye seleziona la connessione appena stabilita.

   Digita la query che vuoi eseguire. Questa estrae alcune colonne da un ga4_traffic_overview tavolo:

   Esempio · SQL

   SELECT date, sessions, total_users, screen_page_views FROM ga4.traffic_overview ORDER BY date DESC LIMIT 100;

   Sotto Scheda di destinazione scegliere Crea un nuovo foglioQuindi premi il pulsante di riproduzione (la freccia ▶). Le righe vengono importate in Excel in uno o due secondi. Premilo di nuovo ogni volta che i dati cambiano e il foglio si aggiornerà automaticamente.

   Non conosci SQL? Crea la query direttamente nel portale Query Streams. Generatore di query Mostra le tue tabelle e colonne in modo da poterle selezionare e cliccare. Con i piani Business puoi anche chiedere a Nova in linguaggio naturale ("mostrami i clienti negli Stati Uniti") e il sistema scriverà automaticamente la query SQL. Salva la query e sarà disponibile con un solo clic nel portale e nell'elenco delle query salvate del componente aggiuntivo, a partire dal piano Personal Core.

Buone mosse successive

• Salva la query nel portale, così puoi eseguirlo di nuovo con un solo clic, da Excel o Fogli Google.
• Aggiungi un filtro come ad esempio un intervallo di date, in modo che la stessa query possa rispondere "questo mese" senza modifiche.
• Condividi i risultati con un collega. Loro vedono le righe, non le tue credenziali.

Domande che le persone si pongono

Guide correlate

• Da Google Analytics 4 a Fogli Google
• Da Stripe a Microsoft Excel
• Da HubSpot a Microsoft Excel
• Da Shopify a Microsoft Excel
• Esecuzione di query SQL in Excel
• Tutte le guide