> For the complete documentation index, see [llms.txt](https://docs.adalysis.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.adalysis.com/integrations/google-chat.md).

# Google Chat

Receive alert notifications in the Google Chat spaces of your choice

Alerts are only useful if someone sees them in time. Connect Google Chat, and Adalysis posts your notifications to a Chat space as cards. Each card has a title, a short summary, a line naming the platform, ad account, and login, the notification's rows (up to 25, then "and N more"), and an **Open in Adalysis** button that opens the right screen.

Google Chat works alongside email and Slack. You decide which notifications go to Google Chat, which go to email, which go to both, and which go nowhere.

**What you can send to Google Chat**

* Performance monitor alerts (on Meta logins these include rule findings)
* Performance goal alerts
* Critical alerts (issues stopping your ads from running), for Google Ads and Microsoft Ads logins
* Routine tasks reminder, for Google Ads and Microsoft Ads logins
* Health alerts, for Meta logins
* Budget spend alerts
* Budget pacing alerts
* Budget rollover

Google Chat also receives the notices Adalysis always sends, whatever is ticked: when it couldn't do something it was asked to do (for example, campaigns that couldn't be paused, budget changes that failed, or budget automation turned off because Google refused its changes), conversion set alerts, and connection alerts when a login loses access to its ad platform.

**Why this is useful**

* Critical alerts and budget pacing issues reach the whole team at once, so problems get fixed faster.
* The team shares one view of what needs attention, instead of each person forwarding emails.
* Personal inboxes stay quiet: send team-wide alerts to Google Chat and keep email for the things only you need.

***

**Before you connect**

* The **Owner and Admins** can add and remove Google Chat spaces and choose which space each login uses. An Admin can only choose spaces for the logins they can open, and can't remove, test, or change a space that also serves logins they don't manage.
* You'll need a **Google Workspace** account, and your Workspace admin must allow incoming webhooks in Google Chat.
* Each login sends to one space, so you can, for example, give each client their own. An Adalysis account can have **up to 20 notification destinations** in all (Zapier hooks, Microsoft Teams workflows, webhooks, and Google Chat spaces together; Slack channels don't count).

***

**Setting it up**

1. In Google Chat, open the space you want notifications posted to. Click the space's name at the top, then **Apps & integrations** > **Webhooks** > **Add webhook**.
2. Name it *Adalysis*, save it, and copy the webhook URL. It starts with `https://chat.googleapis.com/v1/spaces/`.
3. Open your **Adalysis account** (the tile at the top of the rail on the left) and go to **Notifications**. On the **Notification destinations** card, click **Add a Google Chat webhook**.

   ![Open your Adalysis account (1), Notifications (2), then Add a Google Chat webhook (3)](https://3203600314-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGlXujWJyreRidNjZDCw2%2Fuploads%2Fr4SV3QmR3NnYQJ2KPNbc%2FGC-01.png?alt=media)
4. Give it a name (for example, the name of its space), paste the **Webhook URL** and click **Add**.

   ![Add a Google Chat webhook: a name (1), the webhook URL (2), then Add (3)](https://3203600314-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGlXujWJyreRidNjZDCw2%2Fuploads%2FzDXnh0v0z6R2wawQxdfd%2FGC-02.png?alt=media)
5. Adalysis sends a test first. If Google Chat refuses it, the space isn't added and you'll see why. If Google Chat can't be reached at that moment, the space is added anyway, and you'll be asked to send it a test event later. Repeat for any other spaces you want.
6. Under **Ad platform logins**, the new space is already chosen in the **Google Chat** column for every login that didn't have one. To change a login's space, or turn it off with **No Google Chat**, choose it and click the **Save** next to it.
7. Open each login in the app, go to **Settings** > **Notifications** and tick the **Google Chat** column for each notification you want sent there, then click **Save**. On a team, only the login's main user can change this column; other team members see it read-only.

Scheduled notifications arrive at the delivery time and time zone set in the login's **Settings** > **Notifications**. Budget alerts are sent as soon as they happen.

Google Chat accepts about one message per second in a space, so when there are many alerts at once they arrive over a few seconds.

***

**Changing or removing a space**

To send a login to a different space, choose the new space for that login under **Ad platform logins** and click **Save**. To stop using a space, click **Remove** next to it.

If the webhook or its space is deleted in Google Chat, Google stops accepting messages and the space shows **Google Chat stopped accepting it: send a test event once it is fixed** on the **Notification destinations** card. The account's owner gets an email about it. Add a new webhook in the space's **Apps & integrations**, then add it in Adalysis.

For everything else, such as delivery time, email address, and which accounts you get notified about, see [Notifications](https://docs.adalysis.com/onboarding/getting-started/core-account-settings/notifications).
