PLG Analytics Without Consent Banners: Trial-to-Paid Measurement in 2026

If you run growth at a European SaaS company, you have one version of this conversation every quarter. Finance asks what the CAC is. You quote a number from GA4. They ask how confident you are. You shrug. You know that 40–60% of European visitors reject cookies, that your Google Ads spend converts to signups the attribution model can't see, and that the number you just quoted is optimistic by some unknown factor.

Product-led growth depends on a measurement stack that works. When the marketing-site layer is broken, every downstream CAC calculation, every paid-channel ROI decision is made on partial data. Cookieless analytics fixes the top of the funnel — not by tracking harder, but by counting events anonymously and attributing each signup last-click at channel level.

Why the SaaS measurement stack breaks at the top

A standard PLG measurement stack has three layers:

1. Marketing-site attribution (typically GA4): traffic source → landing page → signup.
2. Product event analytics (typically Mixpanel or Amplitude): in-product actions → activation → retention cohorts.
3. Warehouse / revenue (typically BigQuery or Snowflake): subscription tables, MRR, churn.

The top layer is the one that breaks. GA4 sees 13–40% of real EU traffic after consent rejection and ad blockers. Even the signups it sees are attributed poorly, because the cookie that would have preserved the source was rejected or expired. The in-product analytics (Mixpanel/Amplitude) work fine — the user has authenticated, cookies are not the problem, and user-level tracking is compliant on explicit consent inside the product. But the marketing-to-signup layer is unreliable.

What cookieless analytics replaces (and doesn't)

Cookieless analytics for SaaS replaces GA4 at the marketing-site layer. It does not replace Mixpanel or Amplitude anywhere. The two systems have different jobs:

• Cookieless analytics (marketing site, anonymous). Counts visits and signups by channel, campaign and landing page. No user identification, no per-visitor journey.
• Mixpanel / Amplitude (authenticated product, user-level). Tracks what each logged-in user does inside the app. Retention cohorts, feature adoption, in-product funnels.

What cookieless analytics covers:

• Marketing-site visit counts by source
• Campaign-level signup conversion counts
• Landing-page test measurement without sampling
• Paid-channel ROI at the trial-signup event
• BigQuery / Snowflake export for joining against in-product data

What it does not cover:

• In-product feature adoption
• Retention cohort analysis
• Per-user behavior inside the app
• Session replay

The PQL measurement pattern

A working PQL definition for European PLG SaaS requires joining three datasets in the warehouse:

1. Aggregate marketing attribution from cookieless analytics: acquisition channel, campaign, UTM — stored anonymously with signup event metadata.
2. Trial signup records from the product database: email, signup timestamp, plan selected (user-level once authenticated).
3. In-product activation from Mixpanel/Amplitude or your own event log: activation event, time-to-value (user-level).

The join happens at the warehouse, not in the marketing tracker. Because cookieless analytics exports signup attribution to BigQuery or Snowflake at full resolution (no sampling), you get clean channel metadata on every signup. You then join on your own user/email column to add the activation side. A PQL definition like “signed up from paid search + activated within 7 days” becomes a single SQL query.

Implementation for a European PLG SaaS

The setup that works for most teams:

1. Install cookieless analytics on the marketing site only. Leave Mixpanel/Amplitude alone in the app.
2. Configure BigQuery / Snowflake export.
3. Run side-by-side with GA4 on the marketing site for 30 days.
4. Write the join query (channel attribution + signup + product activation).
5. Switch channel-level CAC reporting to the new numbers when the side-by-side comparison stabilises.

No cookie banner for the marketing-site analytics itself (keep the banner for advertising pixels if needed). No migration for in-product analytics. No change to the product team's workflow.

Questions SaaS teams ask