First-party click linking, campaign identifiers, qualified leads, revenue and payout when those values are provided.
Attribution & outcomes ↗Platform for marketing agencies, affiliates & lead-gen teams
Capture leads from forms and APIs, track campaign clicks, and deliver submissions to the tools your team already uses.
02 / PROTECT
ValidationRequired fields & typesTurnstileBrowser verificationSpam checksHoneypot & abuse signalsQuarantineReview before delivery
Review suspected leads ↗PANTHER HOOKCORE
*Performance requires an eligible planSEPARATE SIGNALClicks are tracked independently, then linked to accepted leads by ID
04 / CLICK CONTEXTTracked click → linked leadOptional tracking · UTM / click IDsAttribution vs. click tracking ↗
05 / RECORDED OUTCOMESQualified · Rejected · SaleRevenue / payout when recorded
06 / AD FEEDBACK
Submission protection is distinct from optional click tracking.Performance and ad feedback depend on plan, configuration and provider acceptance.
01 / CAPTURE & PROTECT
Find the leads worth paying for.
Capture campaign context with each lead, verify submissions server-side and hold suspicious traffic for review. Stop guessing which source sent what.
✓ UTM & click-ID attribution
✓ Validation, Turnstile & deduplication
✓ Quarantine without losing reviewable leads
Explore attribution ↗ LIVE CONTEXT EXPLORERILLUSTRATIVE DATA
VISITGoogle Ads
SUBMITForm endpoint
STOREAccepted lead
utm_source / mediumgoogle / cpc
utm_campaignspring_launch
possible click ID keysgclid · gbraid · wbraid
consentWhen supplied
02 / DELIVERY & RECOVERY
A failed integration shouldn't cost you a lead.
Accepted submissions are persisted first. Every configured destination gets observable delivery state, retries and replay instead of a best-effort request that simply disappears.
DELIVERY TRACEINTERACTIVE EXAMPLE
01Lead acceptedPersisted before outbound deliverySTORED
02Destination queuedIndependent job & delivery snapshotQUEUED
03Webhook requestDestination responds with HTTP 200DELIVERED
04Result observedStatus retained in delivery historyRECORDED
NO FIRE-AND-FORGETStore first.
Deliver second.
Deliver second.
Accepted data stays in your inbox even when an outbound service has a bad day.
Accepted leadIndependent jobs
OBSERVABLE BY DEFAULTInspect. Retry. Recover.
See per-destination attempts, failure reasons and retry state from one workspace.
RETRY / REPLAY CONTROLS
03 / ROUTING & TRANSFORMATION
Decide what happens to each lead.
Send the right payload to the right destination. Combine lead-quality decisions, conditional routes and bounded field mapping, without maintaining another custom integration service.
✓ Conditional destinations per form
✓ Field mapping and safe transforms
✓ Quarantine and deliberate release
Explore routing and integrations ↗ ROUTING WORKBENCHILLUSTRATIVE RULES
01 · CLASSIFYAcceptedForm validation & lead decision
02 · TRANSFORMcontact.emailemail → contact.email
03 · ROUTESend to matching destinationsMapped payload, independent attempts
SUPPORTED NATIVE DESTINATIONSPlus Slack, Telegram and HTTPS webhooks shown above
Google Sheets
Zapier
Make
Discord04 / ATTRIBUTION → OUTCOME
Know what worked. Not just what arrived.
Connect clicks, campaign attribution, lead quality and recorded outcomes. Make smarter budget decisions and send eligible conversion feedback to configured destinations.
CLOSED-LOOP EXPLORERPRO / AGENCY · ILLUSTRATIVE
FIRST-PARTY EVENT TRAIL sample identifiers
01
Click recordedclick_id: clk_•••9f2a
CAPTURED02
Lead linkedutm_source: google · gclid saved
MATCHED03
Outcome updatedSale · recorded by your workflow
SALEOUTCOME ECONOMICS illustrative record
RECORDED STATUSSale
Revenue$240.00
Payout$85.00
CHANGE EXAMPLE OUTCOME
Record revenue and payout for an actual lead conversion.
RECORDED STATESale
NEXT STEPEligible conversion feedback
SUPPORTED CONFIGURATION PATHS
Google Ads Meta Microsoft↗ Postbacks
05 / OPERATE IN ONE PLACE
An organized operation, not another collection of tabs.
Bring clients, projects, forms, lead activity and delivery status together. Keep workflows traceable with access controls, structured triage and a server-to-server API.
✓ Workspace → Client → Project → Form
✓ Notes, tags, filters & saved views
✓ Private files & scoped API tokens
Explore workspaces ↗ WORKSPACE PREVIEWILLUSTRATIVE DATA
AGENCY / DEMO WORKSPACE
Separate every account.
Group campaigns and forms by customer. Roles and scoped tokens keep unrelated clients apart.
Acme / product enquiries01
Orbit / campaign leads02
Nova / contact forms03
Your plan and total metered allowances are shared across workspaces owned by the same billing account.
WHAT THIS CHANGES FOR YOUR TEAM
Better decisions. Less operational waste.
Paid traffic, delivery, and lead operations belong to the same working process. Give your team the missing evidence instead of asking them to reconcile six disconnected tools.
Track webhook and integration attempts, inspect recoverable failures and replay according to your plan.
Webhooks & recovery ↗Keep forms, client hierarchy, inbox triage and access scoped, with shared billing-owner plan limits.
Workspaces & teams ↗START WITH ONE TEST SUBMISSIONYour forms already work.
Your forms already work.
Make every lead work harder.
Connect an existing form, verify the capture path, then add routing, protection, attribution and measurement when your team needs them.
Free sandbox for testing. Production features depend on the plan and configured destinations.curl -i -X POST \
'https://pantherhook.com/f/YOUR_PUBLIC_FORM_KEY?test=true' \
-H 'Content-Type: application/json' \
-d '{"email":"lead@example.com"}'Test safely before enabling production routing.Read setup guide ↗