LeadsPedia + VICIdial: leads, calls, affiliates

When teams ask us for this

You buy leads and calls from one platform

Two delivery mechanisms into one dialer, plus the affiliate data that identifies which partner produced each.

You want to judge affiliates on your own outcomes

With the affiliate identifier on the lead, your dispositions tell you what converts rather than the platform reporting telling you.

You run ping-post through LeadsPedia

Only the post reaches add_lead. The ping is a bid and carries nothing dialable.

You also sell transfers

The dialer can call their API at the qualification point and hand the consumer over on an accept.

LeadsPedia describes itself as a platform bringing affiliate management, lead distribution and call tracking and routing into one system. That breadth is the useful part and the awkward part: one account can be sending you web leads, routing you calls, and tracking which affiliate produced each, and those are three different integrations wearing one login.

Integrations on demand. We are not a LeadsPedia partner and there is no connector to enable. Our team wires your account to your server as scoped work, quoted per setup.

The lead path

A delivery posts the record to a URL you nominate. Your endpoint translates it into VICIdial's non-agent API:

non_agent_api.php?function=add_lead
  &phone_number=&phone_code=1&list_id=
  &vendor_lead_code=<leadspedia lead id>
  &source=leadspedia
  &dnc_check=Y&campaign_dnc_check=Y

If LeadsPedia is running ping-post for you, only the post reaches add_lead. The ping is a bid and carries nothing dialable.

The call path

Calls route to a destination on your box - a SIP address or a DID terminating on your carrier - and land in a VICIdial in-group. Take the SIP route if you want the campaign and affiliate values on the agent screen, because only a SIP delivery can carry them as headers for the dialplan to read with PJSIP_HEADER(read,...).

Keep the affiliate identifier

This is the field that makes a LeadsPedia integration worth more than a generic one. Because the platform is doing affiliate management as well as distribution, every lead and every call carries which affiliate produced it.

Write that identifier into VICIdial alongside the lead ID. Once it is on the record, your own dispositions tell you which affiliate produces contacts that convert and which produces noise - measured on your outcomes rather than on the platform's reporting. That is the difference between buying traffic and managing it.

It also runs the other way

The dialer can call LeadsPedia as well. Where you are selling rather than buying, VICIdial fires their API at the qualification point and transfers the consumer live on an accept. See live transfer on a buyer API response for the hooks and the failure modes.

Gotchas

Three integrations, three tests. A working lead delivery says nothing about whether calls route or whether affiliate data survives. Test each independently.

Affiliate identifiers change shape. Sub-IDs and affiliate IDs are different fields and sellers use them inconsistently. Agree which one you are storing before the mapping is built.

Deduplicate at your endpoint. Retries and re-sends are normal on any distribution platform.

Phone formatting. VICIdial wants phone_number and phone_code separately. A post carrying +1 in one field produces a lead the dialer silently never calls.

Questions we get asked

Are you a LeadsPedia partner?

No. There is no certified connector. We wire your account to your server as scoped work, quoted per setup.

Is this one integration or three?

Effectively three. Lead delivery, call routing and affiliate data share a login and nothing else. Each is tested on its own.

Why does the affiliate identifier matter so much?

Because it lets your own dispositions rank affiliates. Without it on the record you are judging traffic quality using the seller reporting rather than your outcomes.

Affiliate ID or sub-ID?

They are different fields and are used inconsistently across sellers. Agree which one you are storing before the mapping is built.

Can calls carry data to the agent screen?

Over SIP, yes. The values travel as headers and are read in the dialplan. A plain DID delivery carries the caller ID and nothing else.