Continuous monitoring without handing over your stack

Automating ingestion means granting a third party standing access to your accounts, which is a different commitment from uploading a file. Four questions settle whether that trade is worth making.

The four

The fourth is the one worth having in reserve. A tool that only works through a live connection is a tool you cannot use to check a past window after you leave. A tool that also accepts a file gives you a manual fallback that never expires.

Scope, concretely

An ingestion integration needs to read the acquisition and order data for the properties you name. It does not need write access, it does not need admin, and it does not need other properties. If the only available grant is broader than that, the breadth is a design decision you inherit.

Note which accounts are connected and where that is recorded. Standing access that nobody remembers granting is the thing that surfaces awkwardly at an audit.

Revocation you can verify

Ask how to revoke, and then check that revoking actually stops the ingestion rather than merely stopping the reporting. Those are different, and the difference matters if the reason you are revoking is that something went wrong.

The general vendor-exit questions are in what you keep when you take the refund and you do not own your attribution data.

Why the file fallback matters

Because the source of truth stays your own Google Analytics account either way. A window you can export is a window you can re-read through any method, now or in three years, connection or not. That property is what makes an export-based approach durable rather than convenient.

It is also why the €99 one-time read is a manual upload by design: it is the version of the product with no standing access at all, refundable within 30 days, no questions asked.

The sequencing that keeps optionality

Start with the upload. Prove the output is worth having on a window you already understand. Only then connect anything, and connect the minimum. That order means you never grant access to a tool you have not already validated.

The one-line rule

Grant the narrowest access that makes the job work, record it somewhere you will find it, and keep a manual path that does not depend on the grant.

Related answers

• The recurring channel read a team comes to rely on
• What continuous monitoring catches early
• What continuous channel monitoring is actually for
• Owning your numbers without a data team
• Machine-readable attribution keeps you portable