Location: Buyers, organization member invites, Targets, RTBs, and RTB groups
Use case: Create a buyer record, give the buyer portal access, and have an admin stop or restore traffic to that buyer without deleting the setup
Creating a buyer record, inviting a user, and sending live traffic are three separate steps. A buyer record does not receive calls until it is attached to a live routing path.
Before you start
This is an administrator workflow. Buyer users can view their buyer-facing information, but they cannot currently pause or resume their own Targets or RTB routes from the buyer portal.
For an urgent pause, contact a Moja organization admin. Do not share an organization API key with a buyer as a workaround.
Create the buyer record
Go to Buyers.
Select Create New.
Enter the buyer's name and the email address that should be associated with their portal access.
Complete any routing or integration details required for your setup.
Save the buyer.
Use a buyer record for the destination business or buying partner, not for each individual campaign. Keep campaign- or route-specific configuration on the Target, RTB, or RTB group that sends traffic to that buyer.
Attach the buyer to a routing path
The buyer record alone does not receive traffic. An administrator must attach it to the applicable route:
Static routing: configure the Target that sends calls to the buyer.
Outbound RTB: configure the buyer's RTB formula and endpoint.
RTB group or routing plan: add the appropriate RTB formula to the route that should offer traffic to the buyer.
Invite the buyer to the portal
Confirm that the email on the buyer record is correct.
Invite that same email address to your Moja organization with the buyer role.
The buyer accepts the invitation and creates or signs in to their Moja account.
The login email must match the email on the buyer record. If the email addresses do not match, the user may be able to sign in but will not see the buyer-level information you expect.
If the buyer cannot access the portal, first confirm that they accepted the invitation and that the same email appears on both the invite and buyer record.
Pause traffic without deleting the setup
Buyer portal access does not control traffic. Use the Target or RTB configuration that sends traffic to the buyer.
Control | Where | What it does |
Target active / pause | Targets → that buyer’s destination | Stops that static path. Configuration stays. |
RTB formula active | RTBs → that formula | Stops that outbound bid path. Endpoint stays. |
Formula in an RTB group | RTB group or routing plan | Disable or remove that formula so the rest of the group can still bid. |
Buyer record / login | Buyers + invite | Does not stop traffic. |
There is no buyer equivalent of Publisher Is Active. To stop everything, disable every Target and RTB formula that can send traffic to that buyer.
Resume traffic
Re-enable the Target or RTB formula.
Confirm it is active in every RTB group or routing path where it should participate.
Verify any schedules, caps, filters, payout rules, and destination settings still match the buyer's agreement.
Run a controlled test or monitor the next eligible call or RTB request.
Verify the setup
The buyer record has the correct name and login email.
The buyer accepted the invitation with the buyer role.
The intended Target or RTB formula is enabled.
Schedules, caps, geographic rules, payout, and duration requirements are correct for the route.
Reporting, Call Logs, or RTB request activity shows the expected delivery behavior after a controlled test.
Need to stop traffic immediately?
An organization admin should pause or disable the relevant Target or RTB formula first, then review any additional routes that can reach the buyer. This preserves the buyer record and configuration for a clean restart later.