DATALYR
Health and wellness attribution

Review your conversion data. Control what you send.

Datalyr filters supported fields in server events. Review each destination’s requirements before enabling delivery: filtering alone does not make a sensitive conversion permitted.

Health and wellness brands need accurate conversion data, but product names and categories can reveal more than an ad platform should receive.

Review every source and channel, including Shopify, Stripe, Whop, web tracking, and mobile apps. A different payment source does not remove an ad platform’s data requirements.

The problem

Standard commerce events can carry sensitive catalog details

A normal purchase payload may include fields such as product name, content category, or item description. Those fields are useful for retail reporting, but they can be inappropriate for a sensitive product catalog.

An event can disclose sensitive information through its meaning, identifiers, or URL as well as its product fields. Some conversions must be withheld entirely.

How it works

Redact the sensitive fields before the event leaves Datalyr

Datalyr applies configured filtering to supported server fields and URLs before delivery. Keyword filtering is not a complete sensitive-data classifier and does not remove information already collected or stored.

Browser pixels, mobile SDKs, and tags installed outside Datalyr need separate review. Server filtering does not stop scripts already running in a browser.

Setup

Review before enabling delivery

01

Review the destination’s requirements

Record any platform notice and identify the affected events, pixels, apps, and regions. Do not infer permission from the absence of a warning.
02

Configure the relevant controls

Review field filtering and restrictions before enabling rules. Follow the privacy controls guide for available settings and release status.
03

Verify the intended outcome

Review delivery diagnostics and browser behavior. Use only authorized, non-sensitive data for permitted provider tests. An accepted API request does not establish campaign eligibility.

Common questions

Does Datalyr decide which fields are sensitive?

Your team chooses the setting based on its data review. The filter removes configured fields and scans supported fields for health terms; it cannot determine every sensitive meaning or whether your business is eligible to send a conversion.

Will reporting still include revenue?

Outbound filtering does not rewrite stored source events. Ad-platform reporting depends on permitted delivery and the platform’s own processing; matching, attribution, and revenue recovery are not guaranteed by turning on a filter.

Is this legal or compliance advice?

No. Datalyr provides technical controls. Your legal or privacy team should decide which data your business may send to each platform.

Review your measurement setup

Review your data and destination requirements before enabling conversion delivery.

7-day trial · No credit card