Skip to main content
Telara

Integrations / Grammarly Business

Grammarly Business logo

Grammarly Business

Grammarly Business — Analytics API exposing per-user writing + Grammarly-AI usage statistics, plus License Management for seats. Spend connector for the AI Platform Spend Governance feature.

OAuth 2.0
Spend

What Telara does

Capability matrix

Indexes NoTracks spend YesDiscovers shadow AI NoRuns actions NoReal-time events No

Before you connect

Prerequisites

A Grammarly Business or Enterprise subscription. Individual and Pro plans have no analytics API.
Subscription admin. Members cannot provision the analytics connection.

Vendor setup

Get the credential

1
Click Connect in Telara
Settings → Integrations → Grammarly Business. Telara sends you to Grammarly. You do not create a Grammarly OAuth app.
2
Approve as subscription admin
Sign in as the admin. On the consent screen, allow analytics access. Click Allow.
3
Return to Telara
Grammarly redirects you back. Finish Connect under Settings → Integrations if it is not already marked connected.

In Telara

Connect in Telara

OAuth 2.0

Grammarly Business OAuth2 token with the analytics-api:read scope, provisioned by a subscription admin. Business/Enterprise plan only.

In Telara, open Settings → Integrations, choose this connector, and click Connect. Telara sends you to the vendor to approve access, then returns you here. You do not create an OAuth app or paste a client secret.

Spend

What gets measured

Resolution: Per user per day.

Attribution: Matched to people by email.

How far back vendor history goes is not published uniformly for this connector.

  • grammarly_ai_prompts
    count
  • sessions
    count
  • days_active
    count
  • sessions_improved_percent
    ratio

Sync

Freshness & sync

Spend connectors refresh on the vendor pull cadence declared in the catalog. Indexing lag is not published for this connector.

Data handling

Permissions & data handling

Telara has not published a permission list for this connector yet. Treat the vendor consent screen as the source of truth until this page lists scopes.

This catalog entry does not declare extra semantic-search exclusions.

After connect

Verify it worked

After you save, Telara runs a read-only check against the account. The integration shows as connected when that check succeeds.

Honesty

Known limitations

Analytics data lags about two days. Same-day zeros are usually Grammarly delay.
A personal Grammarly account will not complete this Connect flow.