Switching From Northbeam: A Guide for Telehealth Brands

A telehealth brand switches from Northbeam by moving its conversion tracking 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. You inventory what the Northbeam pixel, your order feed and any Apex connection send today, let Curve's team rebuild your conversions under neutral event names, run both tools side by side for at least one full customer journey, and compare results against your own count of completed consults or orders.

Moving from Northbeam? Curve's team rebuilds your conversions for a telehealth funnel and keeps attribution through your booking and intake tools, under a BAA. Book a call.

Why telehealth tracking is different

Northbeam describes itself as "a data company" built on first-party data (Northbeam docs). Its pixel collects "Marketing touchpoints & Pages visited" and feeds a device graph, using first-party cookies on a subdomain of your site, while server-side order data, from Shopify or its Orders API, serves as the source of truth. That design suits a store. A telehealth funnel adds three considerations.

Pages visited can be health information

On a telehealth site, the pages a visitor sees name conditions, treatments and medications. Meta's help center lists these 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." Northbeam's own terms address health data as well: "Customer shall not store, or process Sensitive Personal Information in the Company Solution, including but not limited to Personal Health Information, as defined by the Health Insurance Portability and Accountability Act."

HIPAA covers booking and logged-in pages

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

Meta's health and wellness category

Meta may assign a website to 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 Northbeam

• Ad accounts and campaigns. Nothing is rebuilt. Curve's team connects the Meta, Google, TikTok and Microsoft accounts you already run.
• UTM discipline. Northbeam records a visit when "the pixel fires on a page load, and UTMs are intact" (Northbeam docs). Keep the same naming through the switch so reports line up, and check that no value names a condition or medication.
• Outcomes beyond the website. Northbeam treats server-side order data as the source of truth, including offline orders and recurring subscriptions. With Curve, outcomes that happen after the website, such as completed consults and renewals, come back through webhooks and offline uploads, and bridge tokens keep attribution through booking and intake tools.
• The conversions you optimize toward. Curve's team re-creates each one under a neutral event name, so a platform learns that a conversion happened without learning what it was for.
• Apex, if you use it. List Northbeam Apex separately. Northbeam describes it as additive: it "does not replace your existing pixel or CAPI connections," and turning it on "starts sending Northbeam's order-level MTA data to the platform." Plan with Curve's team when to switch it off.
• Your history. Save the Northbeam views you plan to compare against before you close the account.

How to switch from Northbeam, step by step

Curve's team does the setup. You provide access and confirm what counts as a conversion.

1. Book a call and walk through your funnel. Ad platforms, 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 what Northbeam touches. Pages with the pixel, the purchase and custom conversion scripts, the order feed, the tracking subdomain, and any Apex connection.
4. Curve's team rebuilds the events. Neutral event names for every conversion, with contact identifiers SHA-256 hashed to each platform's requirements.
5. Curve's team installs server-side tracking in place of pixels. Meta, Google, TikTok, Microsoft and others receive conversions from Curve's servers. Consent management and PHI-like pattern detection are set up at the same time.
6. Connect booking, intake and outcomes. Bridge tokens, webhooks and offline uploads keep attribution from the ad click through to the consult or order.
7. Retire Northbeam cleanly. After the comparison, remove the pixel and conversion scripts, switch off Apex, and remove the tracking subdomain record.

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

Running Northbeam and Curve side by side

• Watch your other senders. Northbeam describes Apex as a parallel signal next to your pixel and CAPI connections, so the overlap to manage is usually between Curve and any existing pixel or Conversions API sends. Once Curve sends a conversion to a platform, remove the other sender for that same conversion.
• Agree the pages for the overlap. Decide with your compliance lead which pages the Northbeam pixel stays on while you compare, and keep it off booking, intake and logged-in pages.
• Run at least one full customer journey. Cover the time from first click to completed consult or first order. For many telehealth funnels that means two to four weeks.
• Change one platform at a time. Moving Meta first and Google second makes any shift in reported results easy to trace.

Which reports to compare

• Your own source of truth. Completed consults, prescriptions or orders from your booking, EHR or billing system, counted by week.
• Northbeam's Last Non-Direct Touch model. Northbeam's attribution model docs say this "is the default model used by most in-platform reporting," which makes it the closest match to what Meta and Google report under Curve.
• The right accounting mode. Accrual Performance credits the day of the marketing interaction and Cash Snapshot credits the day of the transaction. Platform reports generally credit the day of the ad interaction, so Accrual Performance is usually the closer comparison.
• Clicks-Only as a separate lens. Northbeam's default model splits credit across touchpoints, and its docs note that revenue "will always look lower in Northbeam because credit is split across touchpoints." Read it alongside, not against, platform totals.
• Platform-reported conversions. Meta Events Manager and Ads Manager, Google Ads and TikTok, before and after each platform moves, including cost per result.
• Weekly results in your AI client. With Curve MCP, ask Claude, ChatGPT or another MCP client how each Meta and Google Ads campaign did, with spend next to the conversions Curve tracked. Session recordings and heatmaps under the same BAA show how visitors from each campaign use your pages.

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

Frequently Asked Questions

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

Book a call, sign Curve's BAA and inventory what Northbeam touches today. Curve's team rebuilds your conversions under neutral event names, installs server-side tracking for Meta, Google, TikTok, Microsoft and others, and connects booking and intake tools. You compare reports for at least one customer journey, then retire the Northbeam pixel, scripts and Apex connection.

What do Northbeam's terms say about health information?

Northbeam's terms of service state: "Customer shall not store, or process Sensitive Personal Information in the Company Solution, including but not limited to Personal Health Information, as defined by the Health Insurance Portability and Accountability Act." Curve Compliance signs a BAA on every plan.

What happens to Northbeam Apex when I switch?

Northbeam describes Apex as additive to your pixel and CAPI connections. List it in your inventory and switch it off when you retire Northbeam, on a date you agree with Curve's team.

Which Northbeam report should I compare against?

Last Non-Direct Touch in Accrual Performance mode. Northbeam's docs call Last Non-Direct Touch the default model used by most in-platform reporting.

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 customer journey.

How does Curve handle outcomes that happen after the website?

Webhooks and offline uploads bring completed consults, orders and renewals back as conversions, and bridge tokens keep attribution through separate booking and intake tools.