Once a request has passed the lead quality checks, the question is where it goes. Markmatix will work as lead distribution software built around a cascade of rules: the lead will run through them in order and go to the first partner that accepts it. Before every transfer, the system will check that the consent covers that recipient. There will be two ways out: a click through to the partner, or a transfer of the data.
Lead distribution software, rule by rule
Rules will be ranked by priority. Each one will be able to look at:
- the industry;
- the area;
- the quality score;
- the partner's daily and monthly caps;
- the hours in which the partner takes leads.
The lead will go to the first partner that accepts it. If nobody does, it will stay unsold, under the rules described further down.
Note An example with made-up data: the rule "loans, north, score at least 70" sends leads to partner B until its daily cap is reached. Above the cap, or outside its hours, the lead drops to the next rule.
The same engine will serve loan leads, insurance leads, energy leads and telecom leads. The fields will change; the engine will not.
Consent before any rule
One check will sit above every rule: the consent must cover the recipient. When the lead is captured, the request will save a snapshot of the consent, and routing will compare it with each partner. If a partner is not covered, the transfer will be blocked. How consent is recorded is explained on the proof of consent page.
A lead will be sold either exclusively, to one partner, or shared between several. That choice will be made per industry and per partner.
Two ways out: click or data transfer
The first way out is the click. The person reaches the partner through an outbound link that follows the same rules as a transfer. The link will carry the identifier the publisher has chosen: the contact's, the campaign's, or none at all.
The second way out is a transfer of the data. The lead then travels to the partner through one of the delivery channels.
Delivery to partners
| Channel | What it will be for |
|---|---|
| Dedicated connectors | The APIs of the main partners, each connector written once for every publisher |
| Signed webhook | Receiving the lead in a partner's own system, such as its CRM |
| Encrypted email | Partners who take leads by email |
| SFTP file | Partners who prefer to receive files |
Everything will go through a queue with retries, and every delivery will be logged. If a partner stops responding, a Telegram alert will go out, and that alert will stay on whatever your settings.
For a partner's CRM, the signed webhook will be the most direct route: the partner receives the lead in its own system, and the signature lets it check that the lead really came from Markmatix.
Unsold leads
A lead nobody accepts will not be lost, but it will not stay on sale for ever:
- it will remain with the publisher for its own communications, if the consent allows;
- it will be possible to offer it to partners again within a configurable window, 7 days by default;
- after the window it will not be passed on, and the request will move to the "expired" status.
Ping post as a paid plugin
The real-time auction, ping post, will arrive as a paid plugin on the same rules engine. In a ping post auction, partners usually see a description of the lead without contact details first and place a bid; the full lead goes to the winner. In the auction too, the consent will have to cover the recipient.
The partner portal, in a later phase
The partner portal will be part of the core and will come in a later phase. There, partners will see the leads they received, record outcomes, dispute a lead with a reason, and download the proof of consent. Outcomes will flow back to the request and into the accounts, as described on the revenue tracking page.
To hear when you can try it, join the waitlist.
Updated 3 November 2026