Provena tracks every click, call, booking and sale back to the ad that earned it, then sends better signals to Google, Meta and TikTok. Built from day one for HIPAA and GDPR, so clinics, health brands and EU shops can finally use real attribution.
Classic attribution tools fingerprint visitors, store full URLs, and push names, emails and pages straight to ad platforms. On a clinic site that is a HIPAA breach: US regulators have said that tracking tech on health pages discloses PHI, and hospitals have paid out millions over the Meta pixel. In the EU the same setup breaks GDPR and ePrivacy unless the visitor said yes first. So the businesses that spend the most per customer often fly blind.
Each platform claims the same sale. Without your own source of truth you scale the wrong campaigns.
A URL like /conditions/hiv?email=... tied to an IP address is protected health information. Most tags send it anyway.
When half your visitors say no, naive tools lose them. Provena still counts them, anonymously, in cookieless mode.
A 3 KB first-party script. Nothing is stored on the device until the visitor chooses. Without consent it runs cookieless with a salt that rotates every 24 hours.
Every event is cleaned before it touches disk: emails, phones, CPR and SSN, record ids, card numbers and health topics are removed from URLs. IPs are cut to /24.
Six models side by side: first click, last click, linear, time decay, position based and Provena data-driven, which weights each channel by its measured lift.
Conversions go back to Google, Meta and TikTok only for visitors who said yes, as SHA-256 hashes. In HIPAA mode nothing identifying leaves Provena.
See the full path, for example TikTok, then Google search, then email, then booking, with time between steps.
Ad spend next to attributed revenue, compared with what last click would have claimed.
Phone calls, flyers and QR codes are channels too. Tag them with utm_medium=call, print or qr.
Every choice is stored with time, policy version and a hash of the exact banner text, which is the proof GDPR Article 7 asks for.
Type an email to export or erase everything about a person. We only keep a keyed hash of it, never the email itself.
Logins, exports, setting changes and data requests sit in a hash chain. Change one row and the chain breaks.
Set 30 days to 3 years per workspace. Older events are purged every hour and the purge is logged.
Data stays in the EU. No US sub-processors for event data, no third-party scripts on any Provena page.
Send offline sales, CRM deals and phone bookings from your backend with the same privacy rules.
This calls the real redaction code that runs on every event.
| Requirement | Typical attribution tracker | Provena |
|---|---|---|
| HIPAA: no PHI to vendors without a BAA | Sends URLs, IP and email to ad platforms | PHI stripped before storage, no identifiers to ad platforms in HIPAA mode, BAA available |
| HIPAA Security Rule: audit controls | Rarely | Hash-chained audit log of every access and export |
| GDPR Art. 6 + ePrivacy: lawful basis, prior consent | Fires on page load | Consent-first, cookieless fallback with daily rotating salt |
| GDPR Art. 7: proof of consent | No | Ledger with policy version and banner text hash |
| GDPR Art. 5(1)(c): data minimisation | Full URLs, fingerprinting | Allowlisted params, truncated IP, browser family only |
| GDPR Art. 5(1)(e): storage limitation | Forever | Retention per workspace, hourly purge |
| GDPR Art. 15 + 17: access and erasure | Support ticket | One click, logged |
| GDPR Chapter V: transfers | US servers | EU hosting, DPA included |
Provena is a demo product by Full Stack Partner. Compliance always also depends on how you configure it and on your own policies; this page is not legal advice.
You lose the long journey, not the visit. Declined visitors are counted cookieless for one day at a time, so traffic, conversions and same-day sources stay accurate, while nobody can be followed across days.
Yes, for visitors who gave marketing consent: Provena sends the conversion with a SHA-256 hashed email and Limited Data Use on. Everyone else stays inside Provena. In HIPAA mode only de-identified events are sent unless a BAA covers the receiver.
Analytics tells you about traffic. Provena ties revenue to the ads that caused it, compares six attribution models, and comes with the consent ledger, data request tools and audit trail a regulated business needs.
Add one script tag with your site key, then call provena.track('purchase', {value: 99}) where a sale happens. A server-side API covers phone and offline sales.
Two demo workspaces: a dermatology clinic in HIPAA mode and an outdoor shop in GDPR mode.
Provena