Lead distribution without a developer.
pingtype captures leads from your traffic, filters out the bad ones and routes each one to the right buyer, with server-to-server tracking and publisher payouts built in. You set it all up by clicking.






Everything between a click and a payout.
Capture
Lead forms without code.
Build multi-step forms by clicking.
Filter
Keep bad leads away from your buyers.
Rules for duplicates, fake details and blocked sources.
Route
Choose who gets each lead.
Cascades, splits and ping/post bidding.
Deliver
Send every lead the way each buyer wants it.
Limit
Keep every buyer and publisher inside their numbers.
Caps on leads, clicks, sales or spend.
Track
Know where every lead came from.
Server-to-server click tracking and postbacks.
Pay
Know who is owed what.
Publisher payouts and buyer invoices.
Report
See what makes and loses money.
Eleven reports, with up to twelve custom columns.
Partners
Let publishers and buyers help themselves.
Self-service portals for both.
Brand
Your clients see your name.
A white-label console and portals.
Connect
Link your systems, or your AI assistant.
API access, and connection to assistants such as Claude and ChatGPT.
Records
Find any person, lead or click.
OpenRTB. Real-time auctions over OpenRTB are on the way.
Who it's for
Media buyers and affiliates
Capture leads from your traffic and sell them to more than one buyer.
Affiliate networks
Run offers, publishers and buyers in one place, with payouts and invoices.
Agencies
Give each client a separate space under your own brand.
Lead buyers
Receive leads the way you want them, inside the limits you set.
How it works
1
Capture
Leads arrive from your forms, links or API.
2
Filter and route
Rules clean the traffic, and cascades send each lead to the right buyer, within caps.
3
Track and pay
Every click and sale is tracked, and payouts and invoices follow.
Built to be run properly.
Details come from each product's own published pages, which remain the authority and may be more current.
- Each client has its own login, web address and data, with its own users, data and settings.
- Sign-in supports two-factor authentication.
- Every change is recorded in an audit log showing who changed what, and the previous value.
- API tokens can be read-only or read and write, and can be revoked at any time.
- Daily backups are kept for 30 days, then monthly backups for 12 months.
- A workspace can request a data export or a full erasure.
Get in touch.
Our own contact form is coming soon. Until then, you can reach each product's team through its own site.