Signal Tracker · Layer 1 of Mediaura Signal
The Tracking Layer Your Marketing Stack Was Supposed to Have All Along
Signal Tracker is the first-party signal capture infrastructure that powers Mediaura Signal. It runs on your domain, captures the events your off-the-shelf pixels miss, keeps the form fields it recognizes as sensitive from ever leaving the browser, and bridges the systems that have spent the last decade refusing to talk to each other.
Live in production today. Built for HIPAA-regulated organizations. Business Associate Agreement included.
Your Tracking Isn't a System. It's a Pile.
Walk into any mid-market marketing operation and look at the tracking stack. There's a Tag Manager container with eighteen tags, half of them owned by people who don't work there anymore. There's a Meta pixel that fires twice on the thank-you page and not at all on mobile Safari. There's a CallRail account that knows which calls came from which keywords but has no idea those calls turned into $400K of closed business in the CRM. There's a Leadfeeder subscription that identifies anonymous visitors by company but can't tell HubSpot what campaign brought them. There's a Zapier account holding it all together with seventeen zaps and a prayer.
This is not a tracking strategy. This is sediment.
And the cost isn't just messy data. Every layer of the marketing intelligence stack above it inherits the mess. Better dashboards on broken inputs just produce prettier wrong answers. Smarter attribution models on fragmented identity just give the wrong channel credit more confidently. AI assistants on top of all of it just hallucinate with style.
The only fix is to replace the foundation.
The Infrastructure
Purpose-Built First-Party Infrastructure
Signal Tracker is more than a tag. It is not a wrapper around someone else's pixel. It is a tag plus a dedicated collection service and privacy layer that we deploy on your domain, configure to your specific stack, and operate as a managed service underneath everything else Mediaura Signal does.
It ships today as either a standalone script or a Tag Manager custom HTML tag, so clients with existing GTM investments don't have to rip anything out to deploy it.
What It Captures, Out of the Box
Pageviews and Form Submissions
Auto-captured on load, with password and hidden fields automatically excluded from form data.
Five Ad Platform Click IDs
Google (gclid), Meta (fbclid), Microsoft (msclkid), LinkedIn (li_fat_id), and TikTok (ttclid), captured the moment a visitor lands on your site.
Full UTM Parameter Capture
Every UTM, persisted to first-touch attribution that survives subsequent sessions.
First-Touch Attribution
Preserved across the entire customer journey, including across the handoff to call tracking.
Session-Scoped Identity
Tab-aware, persistent across page navigations.
Native Call Tracking Handoff
For retail, restaurant, and B2B clients, first-touch attribution is pushed directly into CallTrackingMetrics so the call you receive carries the campaign that earned it. In healthcare deployments, this path is off.
What Makes It Different
First-Party by Default
Runs on your domain, not ours, so browser privacy defenses, ad blockers, and iOS tracking restrictions are less likely to block it than a third-party pixel. No tracker captures every event.
Resilient by Design
Events ship fire-and-forget with a built-in retry policy. If our core services are unreachable, the collection service holds events briefly and delivers them when service resumes.
Survives the Cookie Apocalypse
Built for a world where third-party cookies are gone and signed-in identity is the new floor.
Continuously Monitored
When a tag breaks, a property duplicates, or a conversion stops firing, it shows up in the platform, not at the next quarterly review.
Managed, Not Handed Off
Operated as a service. You don't get a config file and a wiki page. You get an engineering team that owns the layer.
Production-Proven
Deployed today across healthcare, restaurant, and B2B clients. Not aspirational.
Compliance
Built for the Regulated Industries Other Tools Won't Touch
Most tracking infrastructure was built assuming a low-stakes, ecommerce-style use case. Signal Tracker was built assuming the opposite: the customer might be a behavioral health treatment center, the data might include PHI, and the consequences of a leaked event might be a HIPAA violation.
Privacy filtering is not a setting in Signal Tracker. It is the pipeline.
Signal's tag refuses to read password, payment card, and health-related form fields, so their contents never leave the visitor's browser. Whatever it does send travels over TLS to a dedicated collection service, where identifiers are hashed with a key unique to your organization before anything reaches the analytics platform. In healthcare deployments, all of it is handled as PHI under our BAA.
Four Layers of Filtering in Healthcare Deployments
Field Rules
Known fields like names, emails, and SSNs are matched against an explicit policy and either hashed or redacted before the event is even queued. No guessing.
Pattern Detection
Every field value is scanned against regex patterns for SSNs, email addresses, phone numbers, medical record numbers, and dates of birth. Anything that matches gets caught even if the field wasn't explicitly named.
Medical Keyword Detection
A maintained library of ~150 medical terms (conditions, treatments, medications, diagnoses) is matched against every value via fast set lookup and substring detection. A field that says "diabetes consultation" gets flagged regardless of what the form called it.
Default-Hash Safety Net
Anything not on an explicit allowlist is hashed by default. The pipeline is biased toward catching too much, not too little.
Per-Site Cryptographic Isolation
Every Signal Tracker deployment gets its own 256-bit HMAC key, generated from a cryptographic random source. Each organization's identifiers are hashed with a separate key, so records can't be matched across clients.
Every Event Ships With a Scrub Audit Report
When a compliance officer asks "show me what was scrubbed from this event and which rule caught it," the answer is already in the event. Every event Signal Tracker processes carries a complete audit trail: which fields were scrubbed, which rules matched, and which policy version was active at the time.
You don't reconstruct compliance after the fact. You ship it inline.
What That Adds Up To
Built for HIPAA-Regulated Organizations
Events travel over TLS to a dedicated collection service. In healthcare deployments, everything Signal collects is handled as PHI under our BAA.
BAA Included as Standard
For all healthcare engagements.
SOC 2 Type 2 in progress
SOC 2 Type 2 examination in progress.
U.S. Organizations, U.S. Processing
Signal is offered to U.S. organizations, and data is processed in the United States. Consent state can be captured with every event.
Fail-Closed Audit Logging
Administrative actions and cross-tenant access are written to a dedicated audit log. If the audit write fails, the access fails.
Integrations
The Integrations No One Else Has Built
Almost every system in your marketing stack does one job well and refuses to do anything else. Signal Tracker is the layer that closes those gaps, and it's doing it in production for clients today.
For retail, restaurant, and B2B clients, Signal can send verified conversions back to your ad platforms and write attribution into your CRM. In healthcare deployments, those paths are off by design, and no Order Form can turn them on.
Visitor Identification → CRM
Live today Non-healthcareLive: Leadfeeder → HubSpot, Salesforce · On request: ZoomInfo, Clearbit Reveal, 6sense → Pipedrive, Microsoft Dynamics
When an anonymous visitor is identified to a company, Signal Tracker doesn't just log it. The pixel data fills in the gaps, attaching the originating campaign, the channel, the keyword, and every touchpoint in the session, and pushes a fully-formed contact or lead into your CRM with attribution intact. Sales gets a lead that already knows where it came from. Marketing gets credit for the pipeline.
Call Tracking → CRM
Live today Non-healthcareLive: CallRail, CallTrackingMetrics → HubSpot, Salesforce
This is the integration most high-consideration operators have given up on. The call tracker knows the keyword. The CRM knows the deal. Nobody connects them. For retail, restaurant, and B2B clients, Signal Tracker matches the inbound call back to the originating session (keyword, creative, landing page, device, prior touchpoints) and pushes the enriched call event into your CRM. When the deal closes, the revenue flows back to the campaign that earned it.
In healthcare deployments, Signal reads your intake or admissions system to reconcile calls to admissions. It doesn't write into it.
POS and Transaction Systems → Marketing Intelligence
Live today Non-healthcareLive: Toast, Olo, Thanx → Mediaura Signal and the ad platforms
For restaurant and retail clients, closed transactions are reconciled against the marketing journey that produced them, then fed back into Google and Meta as a server-side conversion event so the platforms optimize toward your real revenue.
Foot Traffic and Trade Area Intelligence
Live todayLive: Placer.ai → Mediaura Signal
For multi-location restaurants and B2B operations with physical locations, Signal Tracker integrates Placer.ai foot traffic and trade-area data into the same attribution model as your digital signals. Click → visit → transaction, in one connected story.
Server-Side Conversion APIs (CAPI)
Native integration Non-healthcareLive: Google Ads, Meta CAPI, TikTok Events API, LinkedIn CAPI
The conversions ad platforms actually trust: first-party, server-side, deduped against client-side events, with the full customer journey context attached. No third-party tools in between. Native, direct, and built into the pipeline, so the platforms have cleaner data to optimize against. Available to retail, restaurant, and B2B clients. In healthcare deployments, this path is off by design, and no Order Form can turn it on.
Forms, Chat, and Scheduling → Everything
Live todayLive: Native HTML forms, HubSpot forms, Calendly, Acuity, most major chat and scheduling tools
Every lead capture surface, regardless of vendor, unified under one event stream and one identity model. No more reconciling four different "lead" definitions across four different vendor dashboards.
Signal Tracker vs. Everything Else
vs. Freshpaint
Freshpaint is a strong product for healthcare event collection. It solves part of Layer 1. It does not solve the bridging problem: the connections from call tracking and intake records to attribution, and, for non-healthcare clients, from visitor identification to CRM and from POS to ad platforms. It is also a self-serve product, which means your team is responsible for configuring, monitoring, and maintaining it. Signal Tracker is operated as a managed service by the engineering team that built it.
vs. Segment
Segment is a customer data platform designed for product analytics and downstream tool routing. It assumes you already have clean events to send it. Signal Tracker is the layer that produces the clean events in the first place; the layer that sits below where Segment expects its inputs to come from. They're not really competitors; they're at different altitudes of the stack.
vs. Google Tag Manager + a Pile of Pixels
This is what most mid-market operators are running today. It's free, it's familiar, and it's the source of the problem. Tags accumulate, ownership decays, monitoring is nonexistent, PHI handling is your problem, and the bridge integrations don't exist at all. GTM is a tool. Signal Tracker is infrastructure. (And if you're committed to GTM, Signal Tracker ships as a custom HTML tag, no rip-and-replace required.)
vs. the DIY Duct-Tape Stack
Every mid-market marketing operation has tried this and every mid-market marketing operation has discovered the same thing: it works until it doesn't, it breaks silently, and the person who built it is no longer at the company. Signal Tracker is what you build when you decide to stop rebuilding it every eighteen months.
vs. Building It In-House
You can. We did. It took years, a dedicated engineering team, a layered privacy filter, an independent SOC 2 Type 2 examination now underway, native integrations with the major conversion APIs, and a deep understanding of every quirk in every ad platform's conversion API. If your business is marketing intelligence, that investment makes sense. If your business is anything else, it doesn't.
Layer 1 of a Four-Layer System
Signal Tracker is the foundation. The rest of Mediaura Signal is built on top of it.
Signal Tracker
Captures, filters, and bridges the signals
Identity Resolution
Stitches them into a single customer record
Revenue Mapping
Ties that customer to actual booked dollars
The Mediaura Causal Engine (M-CE)
Runs the causal models that explain what happened and forecast what's next
And on top of all of it, Aura, the agentic AI analyst that doesn't do the math, but uses these tools to answer the questions that matter in plain English.
Without Layer 1, none of the layers above it can be trusted. With Layer 1 done right, every layer above it gets dramatically better, because every layer above it is finally working with data that reflects reality.
Learn about Mediaura Signal →Start With the Fit Check
Free and honest, with no obligation on your side. If your data can support causal conclusions, you'll get a written fixed-fee quote and timeline. If it can't, you'll know that too.
Start the Fit Check →