Health and wellness attribution

Keep useful conversion signals. Remove sensitive product data.

Datalyr redacts sensitive catalog fields before server-side events reach Meta, while preserving the identifiers and revenue data used for matching and measurement.

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

Datalyr gives you a clear control point between your store and the platforms you advertise on.

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.

Turning off server-side tracking removes the risky fields, but it also removes the confirmed conversion signal your campaigns need.

Purchase event

content_name: "Vitamin D"

Account flagged

only signal: semantic content

Lookalikes

matched

OFF

lost

Sending everything and sending nothing are not the only choices.

How it works

Redact the sensitive fields before the event leaves Datalyr

Datalyr receives the confirmed commerce event, removes the fields covered by your redaction settings, and forwards the remaining conversion data to the connected platform.

Event ingested

Purchase from your Shopify store

server-side, before the POST

Redactor runs

content_name, content_category, URL paths stripped

Identity Bridge

Meta still matches & attributes

Clean payload sent

Hashed em/ph + click IDs + value preserved

Enriched identity

{hashed email,hashed phone,fbc / fbp,value,order_id}

Apply the policy once, before events are sent downstream.

Setup

Turn it on in three steps

Connect your store and ad accounts

Bring the purchase, refund, and subscription events into Datalyr.

Enable sensitive-field redaction

Choose which catalog fields should be removed from outbound Meta events.

Inspect a test event

Confirm the redacted payload and matching fields before you rely on it for live campaigns.

Keep the data that still matters

Confirmed purchase value and currency
Click and campaign context used for attribution
Permitted customer identifiers used for event matching
Renewals, refunds, and cancellations from your source system
A visible event trail your team can inspect

Common questions

Does Datalyr decide which fields are sensitive?

Your team controls the redaction setting. Datalyr applies that policy consistently to the outbound events it sends.

Will reporting still include revenue?

Yes. Redaction is designed to remove sensitive catalog detail while keeping the permitted conversion and revenue fields your reporting uses.

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.

Send cleaner conversion data

Connect your sources, set the redaction policy, and inspect the first event.

7-day trial · No credit card