Switching From Elevar: A Guide for Telehealth Brands

A telehealth brand switches from Elevar by moving its ad platform feeds to Curve Compliance, which sends conversions to Meta, Google, TikTok, Microsoft and others server-side in place of pixels, signs a BAA on every plan, and has its own team do the HIPAA-compliant setup, usually in about a week. Because Elevar already runs server-side, the switch is mostly a handover: inventory your Elevar sources and destinations, let Curve's team rebuild the ad platform feeds with neutral event names and hashed identifiers, hand over one destination at a time so no event is sent twice, then clean up the paused tags Elevar leaves in Google Tag Manager.

Switching from Elevar? Curve's team rebuilds your ad platform feeds for a telehealth funnel, with neutral events, hashed identifiers and a BAA on every plan. Book a call.

Why telehealth tracking is different

Elevar compares its server-side tracking to "a delivery truck that sends data to your marketing channel" (Elevar docs). It receives data from your storefront, Shopify webhooks and other sources, then performs "session enrichment, deduplication, and identity stitching" before routing events to destinations such as GA4, Meta, TikTok, Pinterest and Klaviyo. For a telehealth brand, what travels in that truck is what matters.

Identity plus health context

Elevar's Session Enrichment uses "a 1-year server-set cookie to identify returning users" and connects email addresses and phone numbers to a user ID so later server events can carry them. On a telehealth site, the pages and products around those events can describe a condition or a prescription. Meta's help center lists medical conditions, treatments and prescription medications among the information businesses should not send, and warns that "UTM parameters in a URL string may contain prohibited data from the landing pages viewed."

HIPAA covers booking and intake

HHS guidance on online tracking says tracking on logged-in pages, such as a telehealth platform, generally has access to PHI, and that pages where people schedule appointments without logging in can too. A tracking vendor that receives PHI is expected to sign a business associate agreement. HHS notes that a federal court vacated one portion of the guidance in 2024, covering visits to public pages about health conditions. Curve Compliance signs a BAA on every plan.

Meta's health and wellness category

Meta may place a website in a health and wellness data source category, with a "telemedicine platform" and a "pharmacy" among its examples, and says such categories "may have additional data sharing restrictions." Curve sends neutral event names server-side, hashes contact identifiers with SHA-256 to each platform's requirements, and runs PHI-like pattern detection on what is sent.

What carries over from Elevar

• Your ad platform destinations. List every Elevar destination and the events each one receives. Curve's team rebuilds the ad platform feeds for Meta, Google, TikTok, Microsoft and others server-side.
• Order rules. If you use Elevar's option to block specific orders from being sent, note the rules so Curve's team knows which orders should not count as conversions.
• Consent. Elevar's destinations respect consent signals. Curve includes consent management, set up by Curve's team as part of the switch.
• Your data history. Elevar's docs explain that it is "not a data warehouse or business intelligence tool" and routes rather than stores collected data, so your history already lives in your destinations, and it stays there.
• Landing pages and subdomains. If you use Elevar's non-Shopify subdomain source for landing pages or a headless site, include those pages in the inventory. With Curve, attribution also carries through booking and intake tools via bridge tokens, webhooks and offline uploads.
• UTM conventions. Keep the same naming so reports line up, and check that no value names a condition or medication.

How to switch from Elevar, step by step

Curve's team does the setup. You provide access and confirm the event map.

1. Book a call and walk through your funnel. Store, landing pages, quiz or intake, booking tool, and where a patient becomes revenue.
2. Sign the BAA. Curve signs one on every plan, at the start of setup.
3. Inventory Elevar. Sources, destinations, the events switched on for each, purchase value settings, blocked orders and any custom events.
4. Curve's team rebuilds the events. Each conversion gets a neutral event name, and contact identifiers are SHA-256 hashed to each platform's requirements.
5. Curve's team installs server-side tracking in place of pixels. Conversions reach Meta, Google, TikTok, Microsoft and others from Curve's servers. Consent management and PHI-like pattern detection are set up at the same time.
6. Connect booking and intake. Bridge tokens, webhooks and offline uploads keep attribution when patients move into separate booking and intake tools.
7. Hand over one destination at a time. When Curve's feed for a platform goes live, switch off the matching Elevar destination the same day.
8. Clean up Google Tag Manager. Elevar's docs explain that disabled web events are uploaded as paused GTM tags, and that "you can delete these tags and there is no harm in doing so" (Elevar docs).

Curve's team usually completes the HIPAA-compliant setup in about a week.

Running Elevar and Curve side by side

• One server-side sender per conversion. Two server-side feeds sending the same purchase to the same Meta dataset or Google Ads conversion action can be counted twice. Hand over by destination and by event, never both tools at once for the same conversion.
• Check your browser tags too. Confirm which browser tags Elevar's web container runs in GTM for each destination, so nothing fires alongside Curve's server-side events.
• Agree the pages for the overlap. Decide with your compliance lead which pages Elevar's tracking stays on while you compare, and keep it off booking, intake and logged-in pages.
• Run at least one full purchase cycle. Cover the time from first click to completed consult or first order. For many telehealth funnels that means two to four weeks.

Which reports to compare

• Your own source of truth. Completed orders, consults or active subscriptions from your store, EHR or billing system, counted by week.
• Meta Events Manager. Events received for each conversion, event match quality and cost per result, before and after each destination moves.
• Google Ads and TikTok conversions. Conversions by action and date, with only one action per conversion set to count during the overlap.
• Elevar's delivery view. Use Elevar's Real-Time Activity Report before the handover to record what it was sending to each destination, so you compare like with like.
• Weekly results in your AI client. With Curve MCP, ask Claude, ChatGPT or another MCP client how each Meta and Google Ads campaign did over recent weeks, with spend next to the conversions Curve tracked.
• Recordings of converted visits. Session recordings and heatmaps run under the same BAA, so you can watch how visitors from each campaign move through product pages and intake.

Ready to switch from Elevar? Curve's team handles the HIPAA-compliant setup, usually in about a week, with a BAA on every plan. Bring your destination list and we will plan the handover with you. Book a call.

Frequently Asked Questions

How does a telehealth brand switch from Elevar to Curve Compliance?

Book a call, sign Curve's BAA and inventory your Elevar sources and destinations. Curve's team rebuilds your ad platform feeds under neutral event names, installs server-side tracking for Meta, Google, TikTok, Microsoft and others, and connects booking and intake tools. You then hand over one destination at a time and clean up the paused GTM tags.

Elevar is already server-side. What does Curve add for a telehealth brand?

A BAA on every plan, neutral event names, PHI-like pattern detection, SHA-256 hashing to each platform's requirements, consent management, attribution through booking and intake tools, session recordings and heatmaps under the same BAA, and setup done by Curve's team.

Can Elevar and Curve run at the same time?

Yes, during the handover. Move one destination at a time and switch off the matching Elevar destination as Curve's feed goes live, so no conversion is sent twice.

What should I do with the paused tags Elevar left in Google Tag Manager?

Elevar's docs say you can delete them and there is no harm in doing so.

How long does the switch take?

Curve's team usually completes the HIPAA-compliant setup in about a week. Plan the side-by-side period to cover at least one full purchase cycle.

Where does my historical data live after the switch?

Elevar's docs say it is not a data warehouse and does not store collected data beyond what routing needs, so your history stays in the destinations it fed, such as your ad platforms and analytics tools.