Can cookieless analytics attribute SaaS revenue?
Understand what cookieless analytics can measure, why anonymous payment attribution gets weaker, and how to evaluate the tradeoff for a SaaS product.
By Graytower team
TL;DR
Cookieless analytics can measure pageviews, events, and aggregate traffic without a persistent anonymous browser ID. It can still show imported Stripe revenue totals. Linking a later payment back to an earlier anonymous visit is much harder because the durable visitor connection is absent, so long-range source attribution has lower coverage.
What does “cookieless” change?
In Graytower's cookieless mode, the browser tracker does not set a persistent anonymous Graytower visitor cookie. It still sends pageviews and custom events, so you can measure aggregate traffic and on-site actions. Visitor counts use a Website-scoped daily pseudonymous key; sessions use fixed 30-minute windows. These are estimates, not durable people or inactivity-based sessions.
The default first-party identity mode uses a persistent _gt_id cookie to connect activity across visits. The tracking mode documentation describes how each mode works and which browser identity calls are available.
| Question | First-party identity | Cookieless mode |
|---|---|---|
| How many pageviews and events occurred? | Available | Available |
| Did an anonymous browser return next week? | Can be measured with the persistent ID | Cannot be reliably linked across days |
| How much eligible Stripe revenue imported? | Available | Available |
| Which earlier anonymous source led to a later payment? | Possible when matching evidence exists | Limited without durable browser identity |
Why is revenue attribution harder?
An acquisition report needs a chain from payment to visitor to recorded source. Cookieless mode intentionally avoids the persistent anonymous browser ID that can carry that chain across visits. Graytower disables browser identify, signup, and checkout_started calls in that mode. Anonymous visitor IDs supplied to certain server-side paths are not used for Stripe attribution.
This does not stop Stripe payment import. The payment remains in total revenue, but more of it may be unattributed. A separate application-supplied named customer identity may still be personal data and needs its own privacy review; it is not a way to claim anonymous tracking.
When is this tradeoff reasonable?
Cookieless mode can make sense when your main questions are aggregate traffic, campaign visits, page performance, and short-window actions. If the main question is which acquisition source produced a payment weeks later, expect weaker anonymous coverage and decide whether that limitation is acceptable.
Before switching, write down the decisions you need the data to support. Compare the effect on returning-visitor analysis, journeys, experiments, and revenue attribution. Then verify the deployed tracker matches the Website setting; changing a setting alone does not replace the script already on your site.
Cookieless is a technical tracking choice, not a legal compliance label. Whether notice, consent, or another legal basis is required depends on your implementation and jurisdiction. See the identity and cookies guide and consult appropriate counsel for legal questions.
For the broader measurement model, read how SaaS revenue attribution works.
Frequently asked questions
Can cookieless analytics track revenue?
Yes. Stripe payments can still be imported and included in total revenue. What becomes harder is connecting a later payment to an earlier anonymous visit and its acquisition source.
Does cookieless mean no personal data is processed?
No. Cookieless describes the absence of a persistent browser identifier in this tracking mode. Request metadata and application-supplied identity can still have privacy implications.
Are cookieless visitor and session counts exact?
No. Without a durable browser identity, Graytower uses daily visitor and fixed half-hour session estimates. Treat them as estimates rather than cross-day person counts.