APAS® AnalyticsGenerally Available

Behavioral analytics that doesn't lose 40% of your visitors to ad blockers.

A full Enterprise PostHog project per client, ingested first-party through your own domain, identity-resolved on the immutable APAS® ID, and mirrored into your own BigQuery.

Funnels, cohorts, retention, session recordings, heatmaps, feature flags, and a full CDP — plus attributed conversion analytics tied to the red → green revenue ladder. Same-origin, consent-aware, owned by you.

apas-cloud-analytics / yoursiteFIRST-PARTY ON
INGEST PROXY
BROWSER → SAME-ORIGINwwv.yoursite.com/apas/e/
FORWARDED →app.posthog.com/capture
Captured
100%
Blocked
0%
Avg p99
32ms
Identity
APAS ID
PROJECT + MIRRORS
P
Enterprise PostHog · yoursite-proddedicated project · funnels · CDP · replays
OWNED
B
BigQuery · yoursite_apas.posthoghourly mirror · 7d retention configurable
STREAMING
GPC honored · anonymous never profiled · identity at consented conversion
0 third-party scripts · 0 cross-site cookiesYours. Not rented.
What it does

Two layers — how visitors behave, and what actually drove revenue — both first-party, both yours.

Standard analytics loads a third-party script that ad blockers, ITP, and privacy modes silently drop — so 40–60% of your visitors never appear in your funnels, and the ones who do are anonymous strangers you can’t connect to revenue. APAS® Analytics is built the opposite way. Every client gets their own full Enterprise PostHog project, but the browser never loads PostHog directly. A first-party init.js served from your own wwv. subdomain bootstraps the immutable APAS® ID before anything else fires, then proxies every analytics request — events, feature-flag decisions, session-replay payloads — same-origin on your visitor-facing hostnames. Ad blockers see first-party traffic to your site and let it through. Because the APAS® ID is registered on every event, behavior is identity-resolved end to end: the same person’s anonymous first session, their form fill, their booked call, and their closed deal are one connected story. Events mirror hourly into your own BigQuery alongside the attribution chain, so you can join behavior to ad spend and revenue.

APAS® Analytics · First-Party

Same-origin analytics that is complete & useful. Finally.

Most businesses still rely on third-party analytics — blocked the moment the browser loads, exactly like the stream below. The more advanced orgs have migrated to server-side tagging to recover some of what's lost. APAS® Cloud moves capture all the way to the network edge: served as native traffic on your own hostname, so blockers can't tell it from your own site; captured before the browser can interfere; streamed raw into your own BigQuery.

STANDARD · 3rd-party scriptGET www.google-analytics.com
0%reached BigQuery
3rd-party domain → blocked / DNS-stripped0 click IDs lost · identity broken
APAS® Cloud · runs on your hostnamesGET *.yoursite.com/apas/e/
0%reached BigQuery
served from your hostnames → delivered in true same-originclick IDs intact · identity resolved
Delta · per 100 visitors+0more sessions with click IDs and attribution captured
simulated stream
APAS® Click ID & APAS® ID threading the entire journey
apasclid = 1747…7e9fapasid = a8f1…2c34
Day 0 · 10:32
1Anonymous pageview
Google Ads · pmax_q2_us
$pageviewanon → identify on next step
Day 3 · 10:42
2Form submission
/consultation
form_submittedidentified ✓
Day 8 · 14:18
3Phone call
(415) 555-0123
phone_callaliased ✓
Day 87 · 09:00
4Revenue
Salesforce · Closed/Won
greengoal hit · ledger ✓
Same person, multiple touchpoints to revenueFrom anonymous click to closed revenue, every touchpoint lands in your BigQuery against the same person — one queryable story, not disconnected events.
Capability pillars

Ten reasons your analytics finally sees everyone.

Same-origin ingest. Identity on every event. Your project. Your warehouse.

First-party, ad-blocker-immune ingest

Analytics is proxied same-origin through your own wwv. subdomain. No third-party script loads; ad blockers and ITP see first-party traffic and let it through. The visitors other tools lose, you keep.

Your own Enterprise PostHog

A dedicated PostHog project per client — not a shared tenant — with the full product-analytics suite: funnels, cohorts, retention, paths, trends, and dashboards.

Identity resolution on APAS® ID

The immutable ID is registered on every event, so anonymous-to-known is one continuous identity. First touch to closed deal is a single connected journey, not disjoint sessions.

Session recordings & heatmaps

Watch real sessions and see where attention and friction actually are — captured first-party, replay payloads proxied through your domain.

Feature flags & experimentation

Roll out features by cohort, gate behavior, and flag-target — decisions served same-origin so they can’t be blocked.

Full CDP engine

Identity stitching, person properties, and behavioral segments — a customer-data platform, not just pageview counts.

Attributed conversion analytics

The in-app surface rolls the pipeline into summary metrics, daily trends, and attribution breakdowns scored on the red → green conversion ladder — spend tied to real outcomes, not vanity sessions.

Mirrored to your BigQuery

Events sync hourly into your own posthog dataset, so you can join behavior to ad spend, the attribution chain, and revenue in one warehouse.

Consent- & privacy-aware

GPC honored; anonymous visitors are never profiled; identification only at consented conversion. Privacy compliance is built into ingest, not bolted on.

Owned, not rented

The PostHog project and the mirrored BigQuery events are yours. Query, export, and keep them — no vendor lock-in, no aggregate-only dashboard.

Two layers, one identity

How visitors behave. What actually drove revenue.

Both keyed to the same APAS® ID, so a behavioral cohort in PostHog and a revenue outcome in the conversion ladder describe the same people — not two disconnected datasets.

Layer 1 · Behavioral + CDP

Your own Enterprise PostHog.

How visitors actually behave — funnels, cohorts, retention, paths, session recordings, heatmaps, feature flags, and CDP identity stitching. A dedicated project per client, not a shared tenant.

Funnels
Cohorts
Retention
Paths
Recordings
Heatmaps
Feature flags
CDP / identity
Layer 2 · Attributed conversions

In-app, scored on the red → green ladder.

What actually drove revenue — period summaries, daily trend lines, and attribution breakdown by source and campaign. The same attributed events the rest of the platform uses.

New lead412
Qualified247
Consult booked138
Closed · revenue62
First-party ingest, explained

Four moves. Result: visitors others lose, you keep.

1
Bootstrap

init.js from your own wwv. subdomain generates/reads the immutable APAS® ID before anything else fires.

2
Proxy

PostHog’s api_host is rewritten to your wwv. hostname; every event, decide call, and replay payload is same-origin to your site.

3
Register

APAS® ID is attached to every capture (register, $set, etc.), so identity travels with every event.

4
Mirror

Events are mirrored hourly into your BigQuery posthog dataset for cross-source joins with ad spend and conversions.

Trust & compliance

Same-origin ingest. Per-client projects. Your warehouse.

The same hardening that powers the rest of APAS® Cloud — applied to every event that lands.

  • HIPAA-compliant infrastructure end-to-end, under the same BAA chain as the rest of APAS® Cloud.
  • First-party / same-origin ingest — no third-party script, no cross-site cookie, ad-blocker- and ITP-resilient by construction.
  • GPC honored; anonymous visitors are never profiled; identification occurs only at consented conversion.
  • A dedicated PostHog project per client — behavioral data isolated by client, never commingled.
  • Events owned in the client’s own PostHog project and mirrored to the client’s own BigQuery — full ownership, no lock-in.
Generally Available

APAS® Analytics is GA to every APAS® Cloud client. Dedicated Enterprise PostHog project, first-party same-origin ingest via the client’s wwv. subdomain, identity resolution on APAS® ID, session recordings, heatmaps, feature flags, CDP, hourly BigQuery mirroring, plus in-app attributed conversion analytics (summary, daily trend, attribution breakdown) on the red → green ladder.

FAQ

Frequently asked

Both load a third-party script that ad blockers strip, losing 40–60% of visitors and leaving the rest anonymous. APAS® proxies analytics first-party through your own domain, registers the immutable APAS® ID on every event, and mirrors to your own warehouse — so you keep the visitors others lose and can tie behavior to revenue.

Keep the visitors everyone else loses.

Request an invitation to APAS® Cloud and get Analytics on day one — your own Enterprise PostHog, first-party ingest, identity-resolved to revenue, mirrored to a warehouse you own.