Rolling Out the Extension to Your Team

The Chrome extension is what makes everything else work. Without it installed on your team's machines, no pulses fire, no data is collected, and your dashboard stays empty. Rollout isn't a nice-to-have — it's the single most important step in your first two weeks.

This article covers three rollout paths, from smallest team to largest:

The email path — 5-20 people, ~30 minutes
The Google Workspace path — 20-500 people, ~1 hour of IT time
The MDM path — 500+ people or regulated environments

Pick the one that fits your scale. For all three, the goal is the same: every person assigned to an AI tool has the extension installed within 7 days.

Before you start — three things to get right

1 · All your tools have complete website lists

The extension fires pulses when the user's browser URL matches one of your tools' registered domains. If you've set up Claude with just claude.ai and your team uses claude.com or the iOS desktop app wrapper, the pulse won't fire.

Go to AI Tools → each tool → Websites and add every subdomain your team actually visits. Comma-separated, wildcards not supported. Add more later as you learn.

2 · Your people are invited and have the right roles

Invited users get the extension sign-in flow. Un-invited users can install it, but it'll dead-end at a "you're not on any team yet" message. Invite first, then roll out.

3 · Tool assignments are set

Assignments decide which pulses fire for which users. Assign people to the tools you believe they use. Nothing breaks if an assignment's wrong — the worst case is a user sees an irrelevant pulse, and you can fix it later.

Path 1 · The email path (5-20 people)

Good for: small teams, founder-led orgs, pilots.

Send one email with a single purpose: get them to install the extension and sign in. Here's a template you can paste:

Subject: Two minutes to install — helps us pick which AI tools to keep paying for

Hi team,

We've just rolled out The GAiGE — a lightweight tool that lets us figure out, honestly and with real data, which of the AI tools we're paying for are actually useful. It's a 10-second pulse that pops up while you're using an AI tool. That's it.

What to do (takes 2 minutes):

Install the extension → [Chrome Web Store link]

Pin it to your toolbar (click the puzzle icon, then the pin next to The GAiGE)

Click the G icon, sign in with your work email

Once you've visited one of our AI tools, you'll start seeing short pulses. Answer honestly — nobody will see your individual answers, only the team's aggregated patterns.

Any trouble, reply to this email or see [help article link].

Thanks — this genuinely helps us make better decisions with your time and our budget.

What makes this email work:

Explains why before how
Links directly to install (no clicking through menus)
Explicit privacy reassurance up front
Gives them something to reply to if they hit trouble

Follow up 7 days later with the people who haven't installed. You can see who's active by looking at the Users page — the Active column tells you who's submitted a pulse.

Path 2 · The Google Workspace path (20-500 people)

Good for: mid-sized orgs with Google Workspace / Google-managed Chrome.

Force-install the extension via Google Workspace Admin Console so it appears automatically in everyone's Chrome with no install action required.

Steps

Sign into admin.google.com as a Workspace super-admin
Devices → Chrome → Apps & extensions → Users & browsers
Pick the organisational unit(s) you want to target (usually everyone)
Click the + button → Add Chrome app or extension by ID
Paste the extension ID (you can find this in the Chrome Web Store URL)
Set Installation policy to Force install
Save

Within minutes to hours, every Chrome browser managed by your Workspace account will have the extension pre-installed. Users can't remove it.

After force-install:

Users still need to click the extension and sign in once — the extension can't authenticate automatically. Send the team an email pointing this out (a shorter version of the email template above, just covering the sign-in step).
Users who sign in via Google SSO (if your org uses it) skip most of the friction here.

Combined with tool-URL policies

If you want maximum signal, also use Workspace's URL-based policies to enforce visiting tool sites only through managed Chrome profiles. That's beyond this article — talk to your IT team or see Google's Chrome enterprise docs.

Path 3 · The MDM path (500+ people or regulated environments)

Good for: large enterprises, healthcare, finance, government, anywhere with a managed-device policy.

The extension supports Chrome enterprise policies via any MDM that handles Chrome:

Microsoft Intune
Jamf (for managed Chromebooks)
Kandji
VMware Workspace ONE
SCCM / Configuration Manager

The manifest to push is a standard Chrome ExtensionInstallForcelist entry. Your Chrome enterprise team will know how to add it — just give them the extension ID.

One-liner for the ExtensionInstallForcelist policy

{
  "ExtensionInstallForcelist": [
    "<EXTENSION_ID>;https://clients2.google.com/service/update2/crx"
  ]
}

Replace <EXTENSION_ID> with the 32-character ID from the Chrome Web Store URL.

Security-sensitive environments

For environments that need to audit what data the extension handles before deploying:

The extension does not read or send the content of pages users visit. Only the URL (to determine the tool), and the user's answers to our pulse questions.
Data is sent over HTTPS to api.thegaige.com, hosted on AWS (ap-southeast-2 — Sydney).
See What data is collected and how it's used for the full enterprise-ready privacy brief.

Measuring rollout success

Two numbers to watch during the first two weeks, both on the Users page:

Install % — how many invited users have installed the extension (we detect this via sign-in events)
Active % — how many have submitted at least one pulse

A healthy rollout gets 80%+ installed and 60%+ active within 7 days. If you're below that by day 7:

Send a reminder email (most common fix)
Check that your Chrome Web Store link works from a clean profile
Check the Users page for users whose role is wrong or who aren't assigned to any tools

Anything under 50% active by day 14 usually means a communication gap, not a technical one. See Why is my response rate low?.

When a new person joins the org

Invite them on the Users page, then either:

If you're on Paths 2 or 3 — the extension auto-installs when their Workspace/MDM-managed Chrome profile first loads. They just need to sign in.
If you're on Path 1 — send them the email template above.

Assign them to tools as you would any other user.

Related: Installing the Chrome extension (admin guide) · Inviting users · User roles explained · Why is my response rate low?