Built for one job, done properly
Every feature here exists because a business running Meta Ads needed it. There is no module you'll never open and no tier that hides the useful parts.
Meta CAPI integration
Map any pipeline stage to any Meta event. Reaching it fires the signal server-side — no developer, no tag manager, no browser dependency.
Connect any lead source
Meta Instant Forms in real time, website forms, and anything that can send a webhook — Zapier, Pabbly, Make. All into one pipeline.
Auto-captured form fields
Your form's questions become CRM columns on their own. Add a question in Meta and it just appears here, filterable, with no field setup.
Full marketing attribution
Campaign, ad set and ad name on every lead, plus UTMs, GCLID, click IDs, landing page and referrer. Know what the spend actually bought.
Automatic lead assignment
Round-robin, load-balance to whoever is free, or route by source, city or campaign. No lead sits unclaimed while the team argues.
Analytics that change spend
Conversion rate per campaign, ad set and ad — not just lead counts. Plus a team leaderboard and time-to-first-call.
Custom pipeline stages
Name your stages after how you actually sell. Mark which count as won and lost, and which send a signal back to Meta.
Call and note tracking
Log outcomes in seconds. Every call, note, stage move and Meta signal on one timeline the whole team can read.
Tasks, callbacks and reminders
Due-dated follow-ups with email reminders, plus a going-cold report that surfaces open leads nobody has touched in days.
Duplicate detection
The same person filling three ads is one lead, flagged and routed to whoever already owns them — not three reps cold-calling one number.
Roles your team can trust
Admins see everything. Sales reps only see leads assigned to them — enforced in the database queries, not hidden in the interface.
Import, export, bulk actions
Bring history in from any CRM by CSV — unrecognised columns become custom fields. Export any filtered view. Your data stays yours.
Map a stage. Meta learns.
Pick a pipeline stage, pick a Meta event from a dropdown, save. From then on every lead that reaches that stage sends the signal server-side, with hashed identifiers, the click ID captured at intake, and a deduplication key.
The usual setup: your qualified stage sends Lead, your closed-won stage
sends Purchase or CompleteRegistration. Early stages send
nothing — telling Meta about raw enquiries is what caused the problem.
Every payload is stored with Meta's exact response, so when a client asks whether the signal really went out, you show them rather than reassure them. Failed events retry on a backoff automatically.
{
"event_name": "Lead",
"event_time": 1755835200,
"event_id": "3f9a…",
"action_source": "system_generated",
"user_data": {
"em": ["sha256 of email"],
"ph": ["sha256 of phone"],
"fbc": "fb.1.1755…",
"lead_id": "1204…"
}
}
What it deliberately doesn't do
Every product page lists strengths. Here is the other half, so you can rule us out fast if we're wrong for you.
No email marketing
Transactional notifications only — assignment alerts, reminders, a daily digest. For campaigns, keep your existing tool.
No quotes or invoicing
You can record a deal value. Generating documents or collecting payment is somebody else's job.
Telephony is an add-on
Click-to-call needs a provider account billed per minute. Logging calls manually is built in and free.
Google Ads is capture-only
GCLID is captured on every lead, but offline conversion upload to Google isn't built yet. Meta is the deep integration.
Watch it work on your own account
Twenty minutes, your Meta setup, the full lead-to-CAPI flow. No obligation.