Skip to main content
Pick this if you sell supplements, wellness, or telehealth, and an ad platform’s health policy limits what you can send. When you finish, your ad platforms receive the revenue and matching fields they need, and none of the product names or URLs that could trigger a restriction.
Redaction is a technical control, not legal review and not a consent interface. Turning it on does not make an ad platform’s health policy stop applying to you.

Before you start

  • A working install and one connected revenue source. Verify a test purchase first.
  • One active CAPI connection in Sources: Meta, TikTok, Google Ads, OpenAI, or Snapchat.

The path

Build the normal flow before you turn on redaction. Otherwise a missing field could be the privacy filter working, or the install broken, and you won’t know which.

What changes when redaction is on

Turning it on also flags the workspace as a sensitive vertical, which defaults Auto-capture email and Stamp cart attributes to off in Settings → Identity & Attribution. Turn either back on only if you have consent.

Do not collect what you cannot send

Redaction runs on the way out, so it never removes sensitive text from your stored events. Keep it out of the payload in the first place.
  1. Mask URL paths that name a condition, under Settings → Filters.
  2. Keep the diagnosis, the symptom, and the prescription out of event properties.
  3. Keep product names out of custom properties you invent.

Verify

  1. Find a real product whose name contains a health term.
  2. Complete a test purchase of that product.
  3. Open Conversions and open the delivered payload.
  4. Confirm content_name and content_category are absent.
  5. Confirm value, currency, and order_id are present.
  6. Open the ad platform’s test-events view and confirm it accepted the event.
Repeat this test after a catalog change, a theme change, or a URL change.

When it doesn’t work

Next