Google Analytics setup guide

Agents read your numbers and run reports.

Ways to connect

Company admins connect apps, on the Integrations page in Everdeck: open Google Analytics, choose one of the ways below, follow its steps and fill in its fields. Everdeck checks what you enter before it saves anything, and asks you to confirm it’s you (your second factor) before you type any secret. How connecting works.

Google Analytics can be connected 2 ways. Where there’s a key or token to paste, that’s usually the quickest.

Google service account

Service account.

1. In Google Cloud console (https://console.cloud.google.com), create or pick a project, open APIs & Services > Library and enable both the Google Analytics Data API and the Google Analytics Admin API.
2. Open IAM & Admin > Service Accounts, create a service account, and on its Keys tab choose Add key > Create new key > JSON. Organizations created on or after May 3, 2024 block key creation by default; an organization admin has to allow it for this project, or use the OAuth option instead.
3. In Google Analytics, open Admin, and under Property click Access management. Click + > Add users, enter the service account's email (client_email in the JSON file) and give it the Viewer role, or Analyst if agents should add annotations.
4. Copy the property ID from Admin > Property details and paste it here with the contents of the JSON file.

Field	What to enter
Service account key (JSON file contents)	A secret: Everdeck saves it encrypted and never shows it again. Where to find it.
GA4 property ID (numbers only)	Text. For example 123456789. Where to find it.

The scopes Everdeck asks for:

• https://www.googleapis.com/auth/analytics.readonly
• https://www.googleapis.com/auth/analytics.edit

Disconnecting deletes the credentials Everdeck saved, but Everdeck can't revoke them: the key, token or password itself keeps working at Google Analytics until you delete or rotate it there.

Your Google OAuth app

Your OAuth app.

This way signs in with an OAuth app you create for Google Analytics, as its steps describe: Everdeck never uses an app of its own. Register this redirect URI with your app:

https://everdeck.io/api/oauth/callback

Then save the app’s client ID and secret in Everdeck, on the connect page or under OAuth apps, and sign in.

1. In Google Cloud console (https://console.cloud.google.com), create or pick a project, open APIs & Services > Library and enable both the Google Analytics Data API and the Google Analytics Admin API.
2. Open Google Auth platform > Branding and fill in the app name and support email. Under Audience, choose Internal if you use Google Workspace. An External app left in Testing gets refresh tokens that expire after 7 days.
3. Under Data Access, add the two scopes listed below.
4. Under Clients, choose Create Client > Web application and add the authorized redirect URI https://everdeck.io/api/oauth/callback.
5. Copy the Client ID and Client secret into the form, enter the property ID (Admin > Property details in Google Analytics), then sign in with a Google account that has at least the Viewer role on the property (Analyst to add annotations).

Field	What to enter
GA4 property ID (numbers only)	Text. For example 123456789. Where to find it.

The scopes Everdeck asks for:

• https://www.googleapis.com/auth/analytics.readonly
• https://www.googleapis.com/auth/analytics.edit

When you disconnect, Everdeck asks Google Analytics to revoke the sign-in, then deletes the tokens it saved.

What agents can do

An agent uses an action only when its charter grants it, on the agent’s Tools tab, where you choose whether each one runs by itself (Auto), asks first or never runs. Each action has a risk tier: tier 3 actions, which customers or the public see, ask first unless you choose otherwise, and tier 4 actions (money, deleting things, access) always need a person. How tools and tiers work.

Actions marked Reads outside content return things people outside your company may have written. Agents treat what they read as information, never as instructions, and their riskier actions later in the same session need approval.

• List accounts and propertiesTier 0 · ReadReads outside contentgoogle_analytics_list_properties

  List the Google Analytics accounts and GA4 properties these credentials can read, with each property's ID (properties/123456789) and name. Use the number as property_id in other actions.

• List dimensions and metricsTier 0 · ReadReads outside contentgoogle_analytics_list_dimensions_and_metrics

  List the dimension and metric names this property supports, including its custom definitions (customEvent:..., customUser:...). Use the apiName values in run_report.

• Run a reportTier 0 · ReadReads outside contentgoogle_analytics_run_report

  Run a custom report with up to 9 dimensions, 10 metrics and 4 date ranges, optional filters and sorting. Dates are YYYY-MM-DD or relative (today, yesterday, 28daysAgo) in the property's time zone. Each row lists dimensionValues and metricValues in the order requested. Common names: dimensions date, pagePath, landingPage, sessionDefaultChannelGroup, sessionSourceMedium, sessionCampaignName, country, deviceCategory, eventName; metrics activeUsers, newUsers, sessions, engagedSessions, engagementRate, screenPageViews, eventCount, keyEvents, totalRevenue.

• Traffic overview by dayTier 0 · ReadReads outside contentgoogle_analytics_get_traffic_overview

  Day by day: active users, new users, sessions, engaged sessions, engagement rate, average session duration (seconds), views, key events and total revenue, oldest day first.

• Top pagesTier 0 · ReadReads outside contentgoogle_analytics_get_top_pages

  Pages and screens ranked by views for a date range, with active users, total engagement time (seconds) and key events. Path and title come first in each row.

• Traffic sourcesTier 0 · ReadReads outside contentgoogle_analytics_get_traffic_sources

  Sessions by default channel group and source / medium (for example Organic Search, google / organic) with active users, engaged sessions, engagement rate, key events and revenue, largest first.

• Real-time activityTier 0 · ReadReads outside contentgoogle_analytics_run_realtime_report

  What is happening now: the last 30 minutes (60 on Analytics 360). Default is active users by country and device. Realtime dimensions: unifiedScreenName, country, city, deviceCategory, platform, eventName, minutesAgo, streamName, appVersion. Metrics: activeUsers, eventCount, keyEvents, screenPageViews.

• List key eventsTier 0 · ReadReads outside contentgoogle_analytics_list_key_events

  The events this property counts as key events (formerly called conversions), with the counting method and any default value. Use keyEvents as a metric to count them.

• List annotationsTier 0 · ReadReads outside contentgoogle_analytics_list_annotations

  Notes on the property's charts (launches, campaigns, outages) with their dates. Use it to explain a jump or drop in traffic.

• Annotate a dateTier 2 · ReversibleReads outside contentgoogle_analytics_create_annotation

  Add a note to a date on the property's report charts, for example "Spring sale email sent" or "Checkout outage". Everyone with access to the property sees it.

What can start work

These events from Google Analytics can become tasks for your agents through Intake. How Intake works.

Once a day, the last 28 days of traffic by day, so an agent can report trends and flag sudden drops.

Connect Google Analytics first. Then, on the Intake page, open Webhooks and sources, find it under Connector triggers and select Start watching. Then, on the Rules tab, select New rule to say which requests become tasks and who gets them.

Testing, problems and disconnecting

Everdeck checks the connection when you save it. On the connection’s page in Integrations, Test checks it again at any time.

If Google Analytics later refuses the connection, for example because a key was deleted or a sign-in expired, the connection shows Needs attention on the Integrations page and the people who manage connections are told. Agents can’t use it until a company admin fixes it with Edit or Reconnect.

To stop agents using Google Analytics, open the connection and select Disconnect. Agents stop using it at once and its saved credentials are deleted. What else happens depends on how it was connected: each way above says.