SignalTrueHow SignalTrue works

Launch lead, call, and conversion campaigns from one hub

SignalTrue takes in your leads and calls, checks them for compliance, routes them to the right buyers, tracks the conversions, and shows you exactly where the money goes — with every money-relevant step recorded in an append-only ledger.

Lead campaigns
Self-serve: add a source, add buyers, test, go live.

Publishers post leads against a per-source key; SignalTrue validates, filters, dedups, and routes each one to the buyer who should get it — then records what they paid.

Call campaigns
Engine live: we configure routing and payouts with you.

Tracking numbers attribute every inbound call to its campaign and source, with call states, dispositions, talk time, and billable status tracked end-to-end.

Conversion tracking
Enabled on request, then self-serve links and postbacks.

Tracked links and postbacks tie downstream outcomes — sales, sign-ups, funded deals — back to the click and partner that produced them.

Watch how it works

Narrated walkthroughs recorded from the real product. The full nine-part series lives in the app next to the screens it explains; these three cover the tour, a complete lead campaign launch, and conversion tracking.

How SignalTrue Works: Campaigns, Buyers & the Money Spine3 min
Lead Campaign Setup, End to End4 min
Conversion Tracking & Postbacks3 min

The model: one campaign, everything attached

Everything in SignalTrue hangs off the campaign — the operational hub that connects your supply, your demand, and your rules:

SourceComplianceRoutingBuyersRevenue
Sources — the publishers sending traffic, each with its own posting key and auto-generated posting docs.
Fields — the lead schema, validated at the door, with PII flagged and masked.
Buyers — each with its own delivery method, pricing, caps, schedule, and filters.
Compliance — policies (like TrustedForm proof) that gate the routing path before anything is delivered.

How routing works

You pick a strategy per campaign; SignalTrue handles eligibility, failover, and retries:

Waterfall

Buyers in priority order — best buyer first, automatic fall-through when one rejects.

Round robin & weighted

Spread volume evenly, or proportionally to the split you set.

Highest bid

Ping buyers for a bid on each lead and sell to the best offer.

Ping/Post

Decisions before PII moves: publishers ping you for a real routing decision; you ping buyers and only post when the bid clears your floor.

Two principles keep routing honest. Outcomes are read from the buyer’s response body, never the HTTP status — a “200 OK” rejection is still a rejection. And errors retry while rejections fail over: a flaky buyer endpoint gets retries and a circuit breaker; a genuine “no” moves the lead to the next buyer immediately. Pay-per-call works the same way, with billable status attaching to what actually happened on the phone.

What setup looks like

Create the campaign Name, offer, vertical — campaigns start in draft, test-only.
Add your traffic Add each publisher as a source; share the auto-generated posting docs.
Add your buyers Endpoint, field mapping, response parsing, pricing, caps, schedules.
Pick the routing Waterfall, round robin, weighted, or highest bid — plus compliance gates.
Test it Run test leads and see every buyer attempt — payload, response, and outcome — before money moves.
Go live A launch-readiness checklist gates the switch; the ledger takes it from there.

Draft and paused campaigns only ever accept test traffic, so you can build, break, and rehearse safely — nothing touches billing until you flip a campaign live. Publishers get a public posting-docs page generated from your live field schema, so their integration instructions can never drift from what validation actually enforces.

Built for performance-marketing operations

See it with your own campaigns

Operators: the full step-by-step setup guide lives in the app, right next to the screens it explains.