Is patient data handled in a HIPAA-compliant way?

Yes. Events run with PHI-safe defaults, and name, email, DOB, and phone are hashed or redacted before data reaches any third-party tool. PathwAI meets HIPAA and PIPEDA with protections on par with GDPR.

Do you use cookies or a tracking pixel?

No. The data platform is server-side. Events are captured first-party and synced to ad platforms through their conversion APIs using hashed identifiers, so matching keeps working without cookies or a client-side pixel.

Which ad platforms can I sync audiences to?

Meta (Conversions API), Google Ads (Enhanced Conversions and Customer Match), and TikTok (Events API) today, plus any custom destination through HMAC-signed webhooks to your CRM or warehouse.

How is PHI kept out of my analytics and ad tools?

Raw PII is captured only in your environment. Identifiers are hashed before they leave, the analytics tier receives fully redacted records, and ad platforms only ever receive hashes for matching.

Can I backfill a new integration with past events?

Yes. Time Machine replays historical events into any new destination, scoped by date range, event type, and segment, so a fresh integration starts with months of data instead of zero.

Data platform

Know which ads
bring you patients.

A HIPAA-native data platform that captures every patient event, resolves identity across sessions, and syncs compliant audiences to every ad platform. No cookies, no PHI leaving your walls.

Book a Demo View pricing

One pipeline, from click to synced audience.

Four capabilities that work as one platform.

Ad tracking that never leaks PHI

Every conversion is scrubbed before it leaves your walls: safe fields pass through, email is hashed, and PHI like date of birth and condition is stripped. Meta and Google get the signal they need to optimize, never a byte of protected health information.

See how PHI stays safe

event stream HIPAA

Acquisition page_viewutm_attributed

Engagement step_completeanswer_saved

Conversion checkout_completesub_started

Compliance consent_grantedphi_hashed

Every event, captured automatically

The moment a patient lands on your flow, PathwAI tracks it: page views, answers, consent, and checkout, structured and stored with PHI-safe defaults. No tag manager, no custom JavaScript.

See integrations

High-intent GLP-1 leads 1,204

WHERE event is step_complete

AND flow.name has "GLP-1"

AND checkout not in 24h

Updated 2 min ago Activate

Segments built on real behavior

Build audiences from what patients actually did: flow completions, drop-offs, product interest, consent status. No SQL, no warehouse, and they stay up to date on their own.

See it live

Audience sync 94% match

Meta CAPI Conversions API Live

Google Ads Enhanced Conversions Live

TikTok Events API Live

First-party audiences to every ad platform

Segments sync to Meta, Google, and TikTok through server-side APIs. Hashed identifiers only, so match rates climb while raw PII never leaves your infrastructure.

See destinations

patient · p_hash_3e7c

page_view
Day 0 form_complete
Day 0 checkout
Day 2 sub_started
Day 2

7Events

2Flows

$149LTV

3Devices

One profile across every session

PathwAI resolves identity deterministically across flows, devices, and time. Returning patients are recognized instantly and their answers pre-fill, so you never re-collect the same data twice.

See a walkthrough

Activate anywhere you spend.

Every ad platform and destination, synced server-side.

Meta CAPI Server-side conversions matched to Meta audiences by hashed email and phone. No pixel, no cookie dependency.

Google Ads Enhanced Conversions and Customer Match sent first-party to Google, so match rates hold without third-party cookies.

TikTok Events Server-to-server delivery to TikTok's Events API with hashed identifiers only. No raw PII ever transmitted.

Webhooks Push any segment change or event to your CRM, warehouse, or internal tooling with an HMAC-signed endpoint.

Attribution Tie every conversion back to the ad, campaign, and keyword that drove it. See which spend actually makes patients.

Time Machine Replay months of historical events into any new integration on day one, all through the same PHI-safe pipeline.

PHI-safe by
default

Most health brands leak PHI the moment they add a marketing pixel, because the pixel was never built for regulated data.

PathwAI hashes and redacts before anything leaves your walls, so you can measure and activate on real patient behavior without ever exposing protected data.

Capture Hash Redact Match

Capture

Raw PII stays in your environment

A patient submits intake and the raw record is captured only inside your HIPAA-aligned environment. Nothing leaves yet.

Hash

Identifiers are hashed before they move

Name, email, DOB, and phone are SHA-256 hashed before a single byte crosses your infrastructure boundary.

Redact

Analytics only ever see redacted records

The event and analytics tiers receive fully redacted payloads. There is zero PHI in the layer your team queries.

Match

Ad platforms get hashes, never PII

Hashed identifiers are sent to ad platforms server-to-server for matching. The raw values are never transmitted.

Why it beats a bolted-on pixel.

Analytics tools and ad pixels were designed to track anonymous shoppers. Patient data is regulated: it has to be captured, hashed, and activated without ever putting PHI where it doesn't belong. Force a generic pixel into that shape and you get brittle tracking and compliance risk.

First-party by design

Every click, answer, and payment is collected on infrastructure you control, not scraped back from a third-party pixel you cannot audit.

PHI never leaves

Hashing and redaction happen before data reaches any external tool, so you activate audiences without ever exposing protected health information.

No cookies, no pixels

Server-side APIs keep conversion matching accurate through iOS privacy changes and cookie deprecation, without client-side tracking that breaks.

Built into the funnel

The same platform that builds your funnel captures its data, so there is no tag manager to wire up and no schema drift between tools.

The data starts in the funnel.

Every event the platform captures comes from a flow you built in PathwAI: landing, eligibility, intake, consent, and checkout in one canvas. The funnel and its data are one product, so there is nothing to wire together.

Explore the funnel builder

A patient funnel on the PathwAI canvas: landing, screening, branching content, and checkout, all connected

Common questions

Ready to own your patient data?

Book a technical walkthrough. We'll show you the live event stream, build a segment together, and walk through an ad platform sync, with real data.

Book a technical demo View pricing

Or explore the funnel builder

Know which adsbring you patients.