DATALYR

Measure the funnel with deliberate data boundaries.

DATALYR provides measurement and redaction controls for health and wellness workflows. Start with a minimal event plan, inspect what is collected and sent, and measure appropriate business outcomes without assuming that a server-side connection makes sensitive data suitable for advertising.

Sensitive context can enter ordinary analytics fields.

A page path, product label or free-text response may reveal more than a generic conversion name suggests. Measurement teams need to review the actual payload, not just the integration’s name. The goal is useful funnel evidence with clear limits on the information collected and the destinations that receive it.

Health and Wellness Tracking

  • Minimal event design

    Choose operational milestones that support a real measurement decision. Avoid copying questionnaire answers or unnecessary personal details into analytics properties simply because the source system makes them available.

  • Redaction review

    Use the documented filtering and redaction controls, then verify their effect on representative records. Controls should be checked against actual URLs and payload fields rather than assumed to cover every possible sensitive value.

  • Destination boundaries

    Evaluate conversion delivery separately from internal reporting. Data suitable for a limited operational purpose is not automatically suitable for an advertising platform, even when it is hashed or transported by a server.

From setup to answer.

  1. Inventory the data path

    List the pages, forms and revenue sources involved in the funnel. Identify fields that may expose sensitive context before installing broad event collection or creating rules that forward events elsewhere.

  2. Configure and inspect

    Apply the relevant documented controls and inspect a controlled journey. Check URLs, labels, custom properties and any replay configuration, then remove fields that are unnecessary for the measurement question.

  3. Verify each destination

    Review the exact outcome and payload before enabling conversion delivery. Confirm that internal reports answer the intended business question while the external destination receives only data appropriate to that purpose.

Know what good looks like.

  • Representative event payloads exclude unnecessary sensitive information.
  • Redaction behavior is verified on actual routes and properties.
  • Each external destination has an independently reviewed payload.

Questions, answered.

Contact us
  • No. A technical control does not establish an organization’s compliance status. Your legal, contractual and operational requirements need their own review alongside the actual implementation and data use.

  • Do not assume that it is. Identifiers and contextual fields may still carry privacy implications. Minimize the data, review its permitted purpose and inspect the destination’s requirements before delivery.

  • Limits on the event data a health-related site or app can share with Meta. Core setup strips URLs and custom parameters, restricted events blocks specific lower-funnel events such as purchases, and a full restriction stops event sharing with Meta altogether.

  • Yes, for the events Meta permits. With health filtering on, DATALYR filters health-related fields from the conversions it sends and withholds whatever a recorded Meta notice restricts. Sending server-side does not make a restricted event permitted.

  • Measure revenue from your payment source and attribute it to the campaign and ad. First-party collection continues while restricted events are withheld from Meta.

Related workflows.

See what really drives revenue.

Real-time attribution, analytics and conversions for every channel, campaign and ad, ready for your team and your agents.

Get started