Getting started as a buyer or network

Who this is for: buyers and networks who purchase inbound calls and route them to advertisers, call centres, or their own agents. What you’ll need: a Moja account, a destination number or SIP endpoint for at least one buyer, and the payout terms you have agreed with your traffic source. Time: about 45 minutes to a first test call. The whole track, done properly, is a few days of real traffic.

Moja models a call as a chain: a publisher sends traffic, a campaign receives it on a tracking number, a routing plan decides where it goes, and a target — or an RTB partner — answers. Build them in that order and nothing dangles.

Tip

Build one static campaign end to end before you add RTB, caps, or QAI. When something breaks later you want exactly one new thing to suspect.

Stage 1 — One call, end to end

Time: about 45 minutes. Goal: a test call that appears in your call log with the right publisher, campaign, target, and payout.

1. Create the publisher record. The source that will send you calls — an affiliate, a media buyer, or your own marketing. Their payout amount and payout rule are set here.

2. Create the buyer and the target. The buyer is who you are selling the call to. The target is the concrete destination: a phone number or SIP endpoint, plus the concurrency and hours it accepts. Set the buyer payout amount and the conversion rule that decides when a call counts.

3. Create the routing plan. The ordered list of targets the call is offered to. Start with one. Add priority and weighting after the single-target case works.

4. Create the campaign and attach the routing plan. Recording, duplicate handling, TCPA scrubbing, caps, and webhooks all live here. Leave them off for now.

5. Buy a tracking number, attach it to the campaign, and set the publisher payout on it. → Purchase a phone number

6. Place a test call. Stay on the line past your conversion threshold — a 30-second call against a 90-second rule proves nothing about payouts. Expected result: within a few seconds, a row appears in your call log with publisher, campaign, target, and duration filled in.

7. Read the call log. Confirm payout, revenue, and conversion match what you configured. This is the step people skip, and it is where mismatched conversion rules surface. → How to read call logs

The full walkthrough, every field, is Create your first campaign.

Stage 1 is done when: one test call routes to your target, connects, and produces the payout you expected on both the buyer and the publisher side.

Stage 2 — Make it safe to leave running

Time: about an hour. Goal: the campaign cannot quietly overspend or double-pay while you are not watching.

1. Set caps. Volume and spend guardrails at the target and publisher level, so a bad day costs a bounded amount. → Advanced caps: volume and spend guardrails

2. Decide duplicate handling. Whether a repeat caller can convert again, and inside what window. Duplicate rules withhold payouts on calls that route perfectly, so set them deliberately rather than discovering them. → Configuring sticky caller and duplicate call routing

3. Turn on compliance scrubbing if your vertical requires it, and use Test Connection before relying on it. → TCPA compliance: default and Blacklist Alliance

4. Block what you never want. Known nuisance callers, or a country code that only ever sends you noise. → Block unwanted callers

Stage 2 is done when: you can state the maximum this campaign can spend in a day, and you have tested that a capped target actually stops taking calls.

Stage 3 — Buy more volume

Time: varies. Goal: more calls than one publisher can send you.

Buy calls over RTBInbound RTB: a publisher pings your campaign, you bid, and the winning bid returns a number they send the call to.

Onboard a publisher onto RTBWhat to hand a new publisher so their first request works.

Targets vs RTB vs RTB groupsWhich of the three you actually want, and when.

Attribute website callsDNI and number pools, so calls from your own landing pages carry their session and ad click.

Send new publishers the publisher getting-started track — it is written to be forwarded.

Stage 3 is done when: a second source of calls is live and attributed correctly in reporting.

Stage 4 — Shape the call before it connects

Time: about 30 minutes per flow. Goal: stop paying for calls that were never going to convert.

1. Move from a routing plan to a call flow when the call needs input collection, branching, or a lookup before routing. → Build a call flow

2. Add a pre-bridge check when the decision has to happen after a buyer is selected but before the call is bridged. → Run a pre-bridge check before the call connects

3. Add an agent availability check so calls are not offered to a buyer with nobody on the floor. → Agent availability check

4. Keep the fields you care about on the call with custom tags, so they are filterable and reportable afterwards. → Keep ping and publisher fields on the call with custom tags

Stage 4 is done when: every branch of the flow has been tested, including blank input, no bid, failed route, and timeout.

Stage 5 — Find out what is actually happening on the calls

Time: about 30 minutes to first results. Goal: outcomes you can act on, not just durations.

1. Turn on QAI — transcripts and dispositions on the traffic you choose, at the sample rate you choose. → QAI quick start

2. Learn your columns. Which number is billable, which is talk time, what an empty buyer field means. → Call log column dictionary

3. Ask questions in plain language rather than building a report for every one-off. → Ask AI reporting

Stage 5 is done when: you can say why your worst publisher is your worst publisher.

Stage 6 — Connect it to your own systems

Outbound webhooksPush call events into your CRM or data warehouse as they happen.

Revenue postbacksSend a confirmed sale amount back against the call after it closes.

Google Ads conversionsUpload eligible call conversions against the original ad click.

Developer referenceRequest and response formats for RTB, webhooks, postbacks, and DNI.

If the first call does not work

Symptom	Likely cause	Fix
Call rings then drops	No target accepted it — hours, concurrency cap, or a failed pre-bridge check	Why are my calls not connecting?
Call connects but no revenue	Conversion rule not met, or buyer payout unset	Why am I getting calls but no revenue?
RTB rows appear but no calls	Bids are returned but the publisher is not dialling the returned number	Why are there many RTB requests but no calls?
No rows at all in the call log	The tracking number is not attached to the campaign	Re-check stage 1, step 5
Calls fail only at certain hours	Campaign and target timezones disagree	How to read call logs

Last reviewed: August 2026.