Google Sheets

Connect Google Sheets when the number you want to track lives in a spreadsheet, not a system.

What you can measure

Two shapes, and which one you pick decides how far back Jents can see.

One cell — the value as it stands right now (for example Sheet1!B2). A cell has no past, so Jents reads it once a day and builds the trend forward from the day you connect. Right for a figure you overwrite in place: current headcount, today's open-ticket count.

A column of history — a date column beside a number column (for example Metrics!A:C). Jents reads the rows dated inside each before/after window, so the comparison uses the history the sheet already holds instead of starting from zero on connection day. Right for anything you add a row to: a daily or weekly KPI log, a monthly scorecard.

If your sheet already has months of history, pick A column of history — it's the difference between measuring an agent from the day you set Jents up and measuring it from the day it went live.

Good things to measure: a KPI you maintain by hand, a rolled-up figure, a manual scorecard number.

Connect it

In Google Sheets, nothing to set up. You authorize read-only access in the next step. If you're using a column of history, check the date column is formatted as a date rather than typed as text (see below).

In Jents, Settings → Integrations → Google Sheets → Connect → authorize, then paste the spreadsheet link and pick the shape:

• One cell — the cell, for example Summary!B2.
• A column of history — the range, for example Metrics!A:C; then which column letter holds the dates (A) and which holds the numbers (C); then whether rows inside one period should be added up (revenue, signups) or averaged (headcount, a rate).

Two things to know about the range:

• Point at whole columns (A:C) rather than a row-bounded range (A1:C500). A bounded range that fills up would quietly start missing the newest rows; Jents refuses one that's full to its last row rather than under-report, so whole columns save you re-editing it as the sheet grows.
• Use column letters, not a named range. A named range doesn't tell us which column is which, and we won't guess which one holds your dates.

A header row is fine — the first row of the range is skipped.

Getting the date column right

Format the column as a date in Sheets. Google then sends us a real date, with no ambiguity about the order.

If the dates are text, Jents accepts them written year-first (2026-01-15) or with the month spelled out (15 Jan 2026, Jan 15, 2026). A bare 01/02/2026 is deliberately refused, because it means 1 February in London and 2 January in New York and nothing in the file says which. Guessing would move that row between the before and after window and the metric would still look fine — so Jents asks instead of guessing.

What Jents reads

One cell: only that cell's numeric value, nothing else in the sheet.

A column of history: only the two columns you name — the dates and the numbers — for the rows inside the period being measured. Not the rest of the row, not the other columns, not the tab's name or notes.

Either way, a value we can't read as a number unambiguously is rejected rather than guessed at, and a window with no rows in it refuses rather than reporting zero — "nothing to report" and "the number was zero" are different answers, and only one of them is true.

Specs

Privacy & security

Read-only, and only the cell — or the two columns — you specify, nothing else in the file. Every read goes through one audited, aggregate-only path and lands in your audit log. Credentials are encrypted at rest, we never train on or share your data, and you can disconnect anytime, see Privacy and Trust.

Helpful links

• Google Sheets API, values
• Google OAuth 2.0