Skip to main content
When you finish, outgoing conversions carry the revenue and matching signals but not the product names, categories, or URL paths that trigger an ad-platform restriction. Use it for supplements, vitamins, telehealth, pharmacy, sexual wellness, and any catalog whose product names name a condition or an ingredient.

​
Before you start

  • You must have the owner or admin role.
  • One CAPI connection must be active in Sources: Meta, TikTok, Google Ads, OpenAI, or Snapchat. The toggle stays disabled until then.
  • Work in Settings → Privacy & redaction. Every instruction below uses that nav label.

​
Turn it on

  1. Open Sources and confirm one CAPI connection reads active.
  2. Open Settings → Privacy & redaction.
  3. Turn on Strip health-vertical fields.
The change takes effect on the next conversion, within 5 minutes. Turning it on also sets the workspace to a sensitive vertical, which defaults Auto-capture email and Stamp cart attributes to off in Settings → Identity & Attribution.

​
What is removed

​
What survives

​
How matching works

We scan each of those fields against three keyword groups plus a dosage pattern. Matching is case-insensitive and matches inside a word, not only on a whole word.
Matching is deliberately over-broad. A product named “Iron Gummies Belt” matches on both gummies and iron-adjacent tokens and loses its content fields. Inspect a real test payload before you rely on this in production.

​
Scope

Redaction runs as the last step before the outgoing request, on every conversion rule for Meta, TikTok, Google, OpenAI, and Snapchat. There is no per-rule toggle in the interface. Redaction isn’t retroactive. It never rewrites a payload we already delivered, and it never changes a stored event.

​
Verify

  1. Find a recent purchase whose product name contains a health term.
  2. Open Conversions and find the delivered row.
  3. Open the request payload.
  4. Confirm content_name and content_category are absent.
  5. Confirm value, currency, and order_id are present.
  6. Open the destination’s test-events view and confirm it accepted the event.

​
When it does not work

​
Next