💡 Overview
This guide explains how a Moja tracking customer can integrate with publishers and sellers of RTB phone calls that send inbound RTB bid requests into a Moja customer’s inbound-RTB-enabled campaign.

Each publisher receives one unique inbound RTB endpoint per campaign, supplied by the Moja customer.

You must create a separate inbound RTB endpoint for each publisher inside the campaign.

ℹ️ Why one per publisher?
This ensures clean attribution, routing control, and flexible passthrough.

Publishers commonly send inbound RTB bid requests using HTTP(S) GET requests with query-string parameters. GET is the recommended default because it is easiest to inspect, share, and troubleshoot. Moja can also accept POST requests, including JSON payloads, when a publisher integration requires it.

Use CALLER_ID as the standard caller ID parameter. CID is also supported. Use one of those consistently unless your Moja team confirms another alias for the campaign.

✔️ Correct
• First parameter begins with ?
• Additional parameters begin with &
• Use tag=value formatting

❌ Incorrect
• Do not use brackets in inbound RTB requests
• Do not send malformed or unencoded parameters

Use the full endpoint URL, including https://. Replace the sample caller ID value with the caller ID value or variable from the sending platform.

Moja automatically derives key system values:

Outbound RTB uses bracket syntax:

⚠️ Important
Brackets are used only for outbound RTB, never inbound.
​

Moja captures all inbound RTB parameters, no matter the naming.

💡 Recommendation
Publishers should send any metadata they need passed to buyers for outbound RTB requests or used for supported buyer/target filtering.

Examples include:

🚫 Current Limitation
​Moja currently supports target/RTB filtering ONLY on:
• ZIP
• State
• Caller ID

Custom-value filtering is not supported yet.

Inbound request parameters can also be captured as Custom Tags. If you want to filter or route on publisher-supplied values such as sub_id, lead_type, traffic_source, vertical, or other custom fields, define them as Custom Tags in Moja first. Once defined, those tags can be used in Advanced Filtering on Targets and RTB endpoints.

✔️ Send these for optimal routing
• CALLER_ID
• ZIP_CODE or State

• Traffic source
• Lead/session ID
• Internal identifiers
• Buyer-required metadata

🧭 How the full inbound → outbound RTB process works:

A Moja customer creates one unique inbound endpoint per publisher.

Publisher submits requests using GET with query-string parameters, or POST requests including JSON payloads when required by the publisher integration. Requests should include CALLER_ID or CID, ZIP/state when available, and other agreed metadata.

Moja derives ZIP/state when needed and stores all inbound parameters.

Routing may depend on caller ID, ZIP, state, routing plans, and campaign logic.

Moja prepares an outbound RTB request using:

Moja dials out and connects the call to the winning buyer target.
​
​
​
​
​
​
​Additional Information:
​
What does the "Duration Add (seconds)" setting mean for the inbound RTB?:
​
Duration Add (seconds) - it adds time to the buyers offer when you’re doing dynamic bidding. In another words, if your buyer offers a conversion at 30 seconds, you can add two seconds so that you present 32 seconds to your publisher. This helps deal with discrepancies between platforms and minimizes conversion disputes with your publisher. 

What is Phone Number Allocation Time for inbound RTB?:
​

Phone Number Allocation Time - this is how long the publisher has to send the call to you if they accept your bid. RTB works by allocating a dynamic telephone number that is available for the duration that you said here. If the call does not make it in that time that number goes away 
​
​

If you or your publishers need help sending inbound RTB requests, mapping fields, or configuring buyers, reach out to Moja Support — we're here to help!