Atribu
Healthcare & HIPAA

Support Runbook

Troubleshooting guide for healthcare account issues and blocked exports

Healthcare Support Runbook

"Why is my export blocked?"

This is the most common question from healthcare accounts. Here's how to diagnose it.

Check the Conversion Sync feed

Go to Conversion Sync > Deliveries and find the blocked event. The status column shows skipped and the detail panel shows the skip reason.

Read the skip reason

Skip ReasonWhat It MeansFix
healthcare_allowlist_blockedEvent type not on HIPAA allowlistAdd it to the allowlist in Privacy & Compliance, or explain why it should stay blocked
healthcare_stage_transition_blockedPipeline stages can't be exported in HIPAA modeBy design — use conversion events instead
healthcare_missing_conversion_keySignal rule missing a valid conversion definitionRe-create the rule with a proper conversion definition source
legal_gate_blockedBAA/legal requirements not metComplete legal setup: BAA Approved + HIPAA Eligible
legal_compliance_missingNo legal record existsCustomer needs to accept the DPA/BAA
hipaa_baa_unsignedBAA approved but not signedComplete the signature workflow

Verify the setup

Confirm these three things:

  1. Privacy mode is hipaa (not standard with blocklists)
  2. Legal panel shows BAA Approved, HIPAA Eligible, all acknowledgements checked
  3. Allowlist has the expected event types checked

Common mistakes

Customer switched back to standard mode

If a healthcare customer accidentally switches from HIPAA to standard mode:

  • Blocklist fields reappear, allowlist disappears
  • No event-type gating occurs
  • PII may be sent unfiltered

Fix: Switch back to HIPAA in Privacy & Compliance. The allowlist configuration is preserved.

Rules created before HIPAA mode was enabled

Signal rules created in standard mode are not retroactively blocked. After enabling HIPAA mode:

  • Existing rules are subject to the allowlist gate on the next export cycle
  • No action needed — the pipeline checks the allowlist at export time, not rule creation time

Verifying privacy filters

  1. Go to Conversion Sync > Deliveries and click on a sent event
  2. In the detail panel, check:
    • filters_applied should include: ip_removed, user_agent_removed, url_sanitized, external_id_removed:fbc, etc.
    • privacy_mode_snapshot.mode should be "hipaa"
    • legal_gate_snapshot should show allowed: true
  3. If payload_redacted shows { redacted: true, hipaa_mode: true } — this confirms raw PHI was not stored in the audit log

What gets stripped in HIPAA mode

FieldStripped?Notes
Client IPYesRemoved from Meta user_data
User agentYesRemoved from Meta user_data
HTTP referrerYesRemoved from custom_data
Page titleYesRemoved from custom_data
External IDs (fbclid, gclid, fbc, fbp)YesRemoved from Meta user_data
URL pathYesReduced to origin only
Hashed email (Meta)SentFor ad matching — hashed, not plaintext
Hashed phone (Meta)SentFor ad matching — hashed, not plaintext
Hashed email (Google)StrippedWhen strip_external_ids is active
Hashed phone (Google)StrippedWhen strip_external_ids is active
Meta LDU flagsInjectedAlways in HIPAA mode

Escalation matrix

SeverityTriggerResponse
P1PHI confirmed sent to Meta/GoogleDisable exports immediately. See incident response
P2Healthcare account in standard mode with active exportsSwitch to HIPAA. Audit recent exports
P3Legal setup incomplete, exports blockedGuide through onboarding
P4Allowlist configuration questionExplain the allowlist

On this page