Healthcare programmatic beyond pharma brands

Digital Health App Marketing: Acquisition Without Overstepping Privacy

How digital health apps can acquire users with paid media while respecting privacy: FTC enforcement lessons, tracking, consent, and claims.

Christian Guerrero Published 4 min read Part 10 of 10

The short answer

Digital health apps acquire users through app store, search, social, and programmatic campaigns, then focus on activation and retention. Their biggest marketing risk is privacy: the FTC has acted against health apps that shared sensitive data with advertising platforms without proper consent, and state laws add requirements. Apps should limit data sent to ad platforms, get clear consent, substantiate health claims, and measure on activated, retained users.

Health apps grow through performance marketing, the same playbook as other consumer apps. The difference is the data. Optimizing campaigns usually means sending in-app events back to ad platforms, and in health apps those events can reveal conditions. Several FTC actions have centered on exactly this.

Lessons from enforcement

The FTC has taken action against health services that shared users' sensitive health information with advertising platforms, including GoodRx and BetterHelp. The FTC also updated the Health Breach Notification Rule to clarify that it covers health apps. Common themes:

  • Health data sent through pixels and SDKs without adequate consent.
  • Privacy promises that did not match practice.
  • Data used for ad targeting or optimization.

Data rules for app marketing

Practice Safer approach
Conversion events Send generic events (install, sign-up) rather than health-specific events
SDKs Audit all third-party SDKs and what they collect
Custom audiences Avoid uploading user lists that reveal health status without consent
Consent Clear, specific, before data is shared
Privacy policy Accurate and matching practice

Acquisition channels

  • App stores: search ads and store optimization.
  • Search: symptom and solution queries, subject to platform health policies.
  • Social and programmatic: broad or contextual targeting rather than health-data audiences.
  • Partnerships: employers, health plans, providers.

Claims

Health and wellness claims must be truthful and substantiated. Apps that function as medical devices may be regulated by FDA. See the FTC health products guidance.

Measurement

  • Activation: users who complete the core setup.
  • Retention: active at 7, 30, and 90 days.
  • Feature engagement: use of the main health feature.
  • Incrementality: geographic or holdout tests where possible.

Privacy-safe measurement may mean less precise attribution. That is a tradeoff to accept.

Common mistakes

  • Default SDK settings sending detailed events.
  • Health-specific event names passed to ad platforms.
  • Uploading member lists to social platforms.
  • Optimizing to installs only.

A privacy-safe event plan

Hypothetical example for a sleep improvement app.

Event Sent to ad platforms? Notes
App install Yes Generic, low sensitivity
Account created Yes, as generic sign-up No health details
Completed sleep assessment No Reveals health information
Subscribed Yes, as generic purchase No product detail implying a condition
Daily use No Kept in internal analytics only

Optimization uses installs, sign-ups, and purchases. Health-specific engagement stays internal. Campaign performance can be judged on retention and engagement through internal analytics, joined to campaign identifiers without passing health data to ad platforms.

  • Ask for consent in plain language at the point it matters.
  • Separate consent for product use from consent for marketing.
  • Make withdrawal easy.
  • Match privacy policy wording to what the app actually does.

Measuring without detailed tracking

  • Geographic or time-based tests for paid channels.
  • Promo codes or landing pages by channel.
  • Cohort analysis of retention by acquisition source, using internal data only.

These methods are less precise than user-level tracking. They are also far less likely to create the kind of data sharing regulators have challenged.

Practical takeaway

Audit every event your app sends to advertising and analytics partners, and rename or remove any that reveal health information. Accept some loss of optimization precision in exchange for staying clear of the practices behind recent enforcement.

Frequently asked questions

Can health apps use ad platform pixels and SDKs?

With great care. Sending health information to ad platforms without clear consent has led to FTC enforcement. Limit what is shared and get proper consent.

Does the FTC Health Breach Notification Rule apply to apps?

It can apply to health apps and similar services not covered by HIPAA. Unauthorized disclosures of health data can count as breaches under the rule.

What should health apps measure?

Activated users, retention at set intervals, and engagement with the core health feature, not just installs.

Sources

External guidance and platform documentation change. Links were current at publication; check them again before relying on them for a decision.

Editorial note. Analysis and frameworks are the author's own and do not represent Acxiom or any current or former employer, client, or named platform. Examples labeled hypothetical or illustrative are not results from real campaigns. Nothing here is legal, regulatory, or medical advice.

Working through this decision on a real plan?

I work on health and pharma data, identity, and activation, after five years running HCP and DTC programmatic agency-side. Happy to talk through how this applies to your situation.