February 2026

Release Notes: 2026-02-03 — Webhooks — Revenue Postback Endpoint

Revenue Postback Endpoint

Why This Matters

Closing the revenue loop has been a top customer request. Until now, you could track calls but had no native way to attribute revenue back to those calls within MojaAI.

This release enables you to:

Link revenue from your CRM or order system directly to calls
See true ROI by campaign, source, and publisher
Update call tags mid-call or post-call for flexible workflow integration
Automate revenue attribution without manual data entry

What’s Included

Update Revenue Webhook – POST revenue amount to associate with a call
Update Tags Webhook – POST tag updates to modify call metadata
Flexible Call Matching – Match by exact call ID or by phone number within a 7-day window
Mid-Call & Post-Call Support – Submit data while call is active or after it ends
Idempotency – Duplicate submissions handled via transaction ID
Call Log Timeline – All webhook actions logged in call timeline

Key Features

Revenue Attribution

When a sale is made, send the revenue amount to MojaAI. The platform matches it to the originating call automatically, giving you clear visibility into which calls generate revenue and what your true cost per acquisition looks like.

Exact Match - Include the call ID for precise attribution
Time-Window Match - Provide the phone number and MojaAI matches to recent calls within the last 7 days

Tag Updates

Update call tags via webhook—useful for marking calls as “converted,” “qualified,” or any custom status your team defines.

Mid-Call Updates - Submit data while a call is still in progress
Post-Call Updates - Submit data after the call ends
Timeline Logging - All updates are logged in the call timeline for operational clarity

Example Use Cases

Sales Team Closes a Deal

Your sales rep closes a deal in your CRM. Your backend automatically POSTs the revenue amount to MojaAI, linking the sale to the originating call. Now your marketing team can see which campaigns drive actual revenue, not just call volume.

Lead Qualification Workflow

An agent qualifies a lead during a call. Your system POSTs a tag update marking the call as “qualified.” Later, when the deal closes, another POST adds the revenue. You now have a complete picture from first call to closed sale.

Multi-Touch Attribution

A customer calls multiple times before converting. Revenue Postback matches by phone number within a 7-day window, so you can attribute revenue to the most recent call or track the full journey.

How It Works

Example: Post Revenue

POST /api/v1/webhooks/incoming/{webhook-id}/update-revenue{ “phone_number”: “+15555551234”, “revenue_amount”: 2500.00, “transaction_id”: “order-12345”}

Example: Update Tags

POST /api/v1/webhooks/incoming/{webhook-id}/update-tags{ “call_id”: “abc123”, “tags”: { “conversion_status”: “qualified”, “sale_amount”: “2500” }}

Configuration Options


Field	Required	Description


`phone_number`	Yes (if no call_id)	Caller phone number for matching
`call_id`	No	Exact call ID for precise matching
`revenue_amount`	Yes (for revenue)	Revenue value to attribute
`tags`	Yes (for tags)	Key-value pairs to update
`transaction_id`	No	For idempotency/deduplication
`currency`	No	Default: USD

How to Get Started

Navigate to Campaigns > Incoming Webhooks in the portal
Create a new webhook and select event type: Update Revenue or Update Tags
Associate the webhook with your campaign(s)
POST revenue data from your backend when a sale is recorded

Questions?

Contact your account manager or reach out to support for help getting started.

Originally published at https://help.mojaai.com/en/articles/13613574-release-notes-2026-02-03-webhooks-revenue-postback-endpoint

Release Notes: 2026-02-05 — Platform — Moja Magic - Pay Once for Every Call

When calls stay on the Moja network, billing consolidates at the final destination.

Release Announcement - Moja Magic

Release Date: February 4, 2026

Location: Targets configuration (magic wand icon indicates Moja Magic eligibility)

Pay Once for Every Call

Moja Magic is a network-level capability that consolidates billing at the final destination when calls stay on the Moja network. Intermediate participants no longer incur per-leg usage charges. Your routing, campaigns, and buyers remain unchanged.

What’s New

Consolidated Billing

When calls traverse multiple participants on Moja’s network, usage charges are consolidated at the final destination. No more paying multiple times for the same call as it moves through different platforms.

Visual Indicators

The platform now shows when Moja Magic routing is active:

Magic wand icon in your targets list for Moja-internal numbers
“Moja Magic” badge when editing target phone numbers

How It Works

A publisher assigns their campaign to a target
The target’s phone number belongs to another Moja customer (indicated by magic wand icon)
Moja Magic applies automatically
The call stays on-network; billing consolidates at the destination
No per-leg usage charges for intermediate participants

Example

A debt publisher generating 500 daily calls switches from an external call tracking platform to Moja. Their network partner is already on Moja. Previously, the publisher paid $0.03/min and the network paid $0.02/min — two charges for the same call. With Moja Magic, the call stays on-network and billing consolidates at the destination. The publisher stops paying per-leg tracking fees; the network pays once when the call lands.

Getting Started

For Publishers

Run your traffic on Moja. Your routing, campaigns, and buyers stay the same — the economics change automatically when calls remain on-network.

For Networks and Brands

Your partners save money on every call that stays on-network. As they learn about the cost savings, they’re more likely to work with you as a preferred partner — a win-win as you gain more buyers. Routing stays the same.

Questions? Contact your account manager or reach out to support.

Originally published at https://help.mojaai.com/en/articles/13639087-release-notes-2026-02-05-platform-moja-magic-pay-once-for-every-call

Release Notes: 2026-02-06 — Platform — Moja Magic

Release notes for Moja Magic

Release Announcement - Moja Magic

Release Date: February 4, 2026

Location: Targets configuration (magic wand icon indicates Moja Magic eligibility)

Pay Once for Every Call

What’s New

Consolidated Billing

Visual Indicators

The platform now shows when Moja Magic routing is active:

Magic wand icon in your targets list for Moja-internal numbers
“Moja Magic” badge when editing target phone numbers

How It Works

A publisher assigns their campaign to a target
The target’s phone number belongs to another Moja customer (indicated by magic wand icon)
Moja Magic applies automatically
The call stays on-network; billing consolidates at the destination
No per-leg usage charges for intermediate participants

Example

Getting Started

For Publishers

Run your traffic on Moja. Your routing, campaigns, and buyers stay the same — the economics change automatically when calls remain on-network.

For Networks and Brands

Questions? Contact your account manager or reach out to support.

Originally published at https://help.mojaai.com/en/articles/13643349-release-notes-2026-02-06-platform-moja-magic

Release Notes: 2026-02-06 — QAI — QAI Call Analytics

Release notes for QAI Call Analytics

Release Announcement — QAI Call Analytics: Redesigned Reporting Experience

Release Date: February 5, 2026

Location: Data > QAI Analysis > Reports

Complete Call Intelligence — From Summary to Single-Call Detail

QAI Call Analytics delivers a full reporting experience built around the way you work. The call-first reporting view gives you immediate access to your call data with disposition, category, and sentiment columns visible right in the call log. When you need deeper insight, drill into any call for a complete analysis view — questions, dispositions, transcriptions, and sentiment — all in one place.

This release includes a comprehensive reporting experience, call-level summary statistics, new filtering capabilities, and streamlined tools for managing dispositions and exporting your data.

What’s New

Call-First Reporting View

QAI reports open with a call-level view. Your call data loads immediately with disposition, category, and sentiment columns displayed directly in the call log table. Question and disposition details load on demand when you drill into a specific call, keeping the reporting view fast and focused.

Call Summary Area with Disposition, Category & Sentiment Data

The call summary area displays aggregated reporting data at a glance:

Disposition breakdown — See counts and percentages across your disposition categories
Category distribution — View how calls are distributed across categories
Sentiment overview — Review sentiment trends across your call volume
Export controls — Download summary and detail data directly from the summary area

Call Analysis View

Click into any call to open a dedicated analysis view that brings together everything about that call in one place:

QAI Questions & Answers — See how the AI answered each question for this call
Disposition Results — View the disposition outcome with a visual breakdown of how rules were matched
Transcription — Read the full call transcript with smooth scrolling and clear timeline contrast
Sentiment Analysis — Review sentiment data for the call

Disposition Breakdown

A dedicated disposition breakdown view shows you exactly how each call was categorized. Color-coded indicators make it easy to see which rules matched, which didn’t, and how the final disposition was determined.

Advanced Filtering for Disposition, Category, Sentiment & Questions

Filter your call data using new operators designed for QAI analytics:

Disposition filters — Filter calls by disposition result (e.g., “Qualified,” “Not Qualified,” “Transfer Ready”)
Category filters — Narrow results to specific call categories
Sentiment filters — Filter by sentiment score or sentiment range
Question-answer filters — Filter calls based on how specific QAI questions were answered

Unified Disposition & Question Management

Questions and dispositions are managed together in a streamlined interface within campaign settings. Disposition rules are configured in QAI Analysis > Configuration, where you define the matching logic that determines how each call is categorized.

Legacy Question Migration

Questions that aren’t linked to a disposition appear with a “legacy” label. You can copy them into the current system or remove them — your choice, at your pace.

Data Export

Export buttons are available in QAI data views and the call summary area, letting you download your analysis data for use in external tools or reports.

Additional Capabilities

Transcription scrolling — Navigate through entire conversations smoothly, even for long transcripts
Timeline contrast — Clear visual contrast on the call timeline for easier reading
Date selector — The date picker defaults to today when you open reports

How It Works

Navigate to Data > QAI Analysis > Reports
Your calls load in the call-first view with disposition, category, and sentiment columns visible
Review the call summary area for disposition breakdowns, category distribution, and sentiment trends
Use advanced filters to narrow results by disposition, category, sentiment, question answers, or other criteria
Click any call row to open the full analysis view
In the analysis view, review questions, dispositions, transcription, and sentiment for that call
Click the disposition result to see a detailed breakdown of rule matching
Use the export buttons to download data as needed

Example

A network running 8 campaigns with 12 QAI questions each opens QAI reports and immediately sees their call data with disposition and sentiment columns in the call log. The summary area shows that 62% of calls this week were categorized as “Qualified — Transfer Ready.” The team filters by that disposition and clicks into a specific call to see the 12 question answers, the full disposition breakdown showing which rules matched, and the complete transcript — all in a single focused view. They export the filtered dataset for their weekly performance review.

Configuration

QAI configuration spans two areas: questions and dispositions are set up within each campaign, while disposition rules are configured in QAI Analysis > Configuration.

QAI Questions (Campaign Settings)

Define the questions that QAI answers for every call on a campaign. Each question is analyzed by AI against the call transcription, and the answer is stored with the call record.

Question types:

Text — Free-form text answer (e.g., “What product did the caller ask about?”)
Multiple choice — Select from predefined answer options (e.g., “Which service was discussed?” with options: Medicare, Auto, Home)
True / False — Yes or No answer (e.g., “Did the caller schedule an appointment?”)
Number — Numeric answer (e.g., “How many times was the caller transferred?”)

Dispositions (Campaign Settings)

Dispositions categorize each call based on how QAI questions were answered. Define your disposition categories (e.g., “Qualified,” “Not Qualified,” “Transfer Ready”) within each campaign.

Disposition Templates (Campaign Settings)

Pre-built templates are available to accelerate disposition setup for common use cases. Start from a template and customize the categories to match your workflow.

Disposition Rules (QAI Analysis > Configuration)

Disposition rules determine when each disposition category applies to a call. Rules are configured in QAI Analysis > Configuration.

Rule matching:

All — Every rule must match for this disposition to apply
Any — Any single rule matching triggers this disposition
Percentage — A specified percentage of rules must match
Count — A specified number of rules must match

Answer matching:

Exact — The question answer must match the rule value exactly
Contains — The answer must contain the specified text
Regex — The answer must match a regular expression pattern
Any of — The answer can be any of multiple specified values

Setting Up QAI

Open a campaign and add your QAI questions — choose the question type and define the question text
For multiple choice questions, define the answer options
Add dispositions within the campaign — name each category, or start from a disposition template
Navigate to QAI Analysis > Configuration to define disposition rules
Set up rules that reference your QAI questions, choose a rule matching type, and specify the expected answers
If you see questions marked as “legacy,” decide whether to copy them into the current system or remove them

Getting Started

No setup required — the reporting experience is live for all accounts. Navigate to Data > QAI Analysis > Reports to start using the call-first view with disposition, category, and sentiment reporting.

If you have legacy questions to migrate, you’ll see them labeled in your campaign settings. You can migrate them at any time.

Questions? Reach out to your account manager or contact support.

Originally published at https://help.mojaai.com/en/articles/13643196-release-notes-2026-02-06-qai-qai-call-analytics

Release Notes: 2026-02-09 — Caps — Advanced Caps

Historical release note for Advanced Caps. Current setup guidance is linked at the top.

NEW FEATURE RELEASE

Advanced Caps

Location: Targets → Advanced Caps | RTB Targets → Advanced Caps | Buyers → Advanced Caps | Campaigns → Advanced Caps | Publishers → Advanced Caps

Release Date: February 2026

Looking for the current setup guide? This release note is kept for historical context. For the evergreen customer guide, see Advanced Caps: Volume and Spend Guardrails.

Overview

Advanced Caps gives you configurable guardrails for call volume and spend across key routing entities. Set caps on connected calls, converted calls, total calls, and revenue for Targets, RTB Targets, Buyers, Campaigns, and Publishers — with flexible timeframe windows. When a cap is approaching or reached, the platform responds automatically: lowering values on the configured side of the routing stack, warning your team, or marking entities ineligible — so you can stay within budget and volume limits without manual monitoring.

Cap counts update in real time, including calls currently in progress, which means concurrent call spikes won’t push you past your limits. Notifications arrive in-app and via Slack so your team can act immediately when thresholds are hit.

What’s New

Cap Types and Entity Coverage

You can now set caps on any of the five entity types in your routing stack: Targets, RTB Targets, Buyers, Campaigns, and Publishers. Each entity’s edit form now includes an Advanced Caps section where you configure all cap rules for that entity.

Four cap types are available:

Connected Calls — Counts calls that successfully connect to the target
Converted Calls — Counts calls that meet your conversion criteria
Total Calls — Counts all calls routed to the entity, regardless of outcome
Revenue — Tracks revenue generated against a dollar limit

You can mix and match cap types on the same entity to enforce multiple constraints simultaneously. For example, a buyer can have both a daily revenue cap of $5,000 and a monthly converted call cap of 2,000 — whichever cap is reached first takes effect.

Timeframes

Each cap operates within a configurable timeframe window. Available timeframes include hourly, daily, weekly, monthly, and custom rolling windows.

Each cap operates independently within its timeframe — for example, a daily cap resets at midnight and a weekly cap resets at the start of each week. You can stack multiple timeframes on the same entity, such as an hourly cap of 25 connected calls and a daily cap of 200 connected calls on the same target.

On-Cap-Reached Behavior

When a cap is hit, you choose how the platform responds:

Mark Ineligible — Removes the entity from routing until the timeframe resets
Lower Bid / Reduce Value — Reduces the payout or revenue value for the side where the cap is configured. Campaign and Publisher caps reduce publisher payout. Target, Buyer, and RTB Target caps reduce buyer-side revenue. Target-side caps do not currently lower publisher bids. Target-side Lower Bid does not lower publisher payout.
Warn — Sends a notification at a configurable percentage threshold without changing routing behavior

When multiple caps overlap on the same entity, the most restrictive cap wins. If a daily revenue cap triggers “mark ineligible” while an hourly connected call cap triggers “lower bid,” the entity is marked ineligible because that’s the more restrictive action.

How Lower Bid Applies

The Lower Bid action applies to the side of the routing stack where the cap is configured.


Cap location	What it controls	Lower Bid affects
Campaign → Publisher-scoped cap	Publisher traffic within that campaign	`publisher_paid_out`
Publisher	Publisher traffic	`publisher_paid_out`
Target	Buyer/target-side traffic	`revenue_paid_out`
RTB Target / RTB Formula	RTB buyer-side traffic	`revenue_paid_out`
Buyer	Buyer-level traffic	`revenue_paid_out`

If your goal is to reduce volume from publishers after a threshold, configure the cap on the Campaign/Publisher side. A Target or Buyer cap protects buyer-side economics, but it does not automatically reduce publisher payout.

Not currently supported: A buyer-side cap cannot yet automatically reduce publisher payout or make publisher traffic less attractive. For example, a Target cap reaching its limit can reduce buyer-side revenue or mark that target unavailable, but it does not cross over and lower the publisher bid.

Example: if a Target cap lowers value by 30%, Moja reduces the buyer-side revenue value for calls routed to that target. It does not reduce publisher payout unless the cap is configured on the publisher side.

Live Call Counting

Real-time cap enforcement — Enable live call tracking so calls currently in progress count toward your cap, not just completed calls.

This addresses a gap that batch-based cap systems miss: concurrent call spikes. When 50 calls arrive in the same minute, a system that only counts completed calls would allow all 50 through before recognizing the cap was exceeded. With live call counting enabled, the platform uses predictive counting to block new calls that would exceed the cap before they connect. The 51st call is blocked in real time, not reconciled after the fact.

Warning Thresholds and Notifications

Warning threshold — Set a percentage (e.g., 80%) to receive an early alert before the cap is reached. Notifications are sent once per threshold event to prevent alert fatigue.
In-app notifications — Cap warnings, cap-met, and cap-exceeded events appear in the platform notification center with details on which entity and cap type triggered the alert.
Slack notifications — Connect a Slack channel to receive cap alerts for your organization. Configure webhooks from the Slack Integrations page under Settings.

Notifications are de-duplicated — you receive one alert when a threshold is crossed, not a repeated alert for every call that arrives while the cap is active. This keeps your notification channels clean even during high-volume periods.

Publisher-Scoped Campaign Caps

Campaign-publisher caps — When creating or editing a Campaign, select a specific Publisher to scope caps at the campaign-publisher level for granular volume control.

This is useful for testing new publishers with controlled exposure before scaling. You can limit a new publisher to 100 converted calls per week within a specific campaign while the campaign continues routing calls from other publishers without restriction.

Why This Matters

Running campaigns across multiple targets, buyers, and publishers means managing volume and spend at every layer. Without comprehensive caps, a high-performing campaign can blow past daily budgets before your team notices, or a single target can absorb more calls than planned — leaving other targets underserved. Advanced Caps puts automated guardrails at every level of your routing stack, with real-time enforcement that catches concurrent spikes before they exceed your limits.

Example Use Cases

A buyer in the debt vertical has a $5,000 daily revenue cap with an 80% warning threshold. At $4,000 your team gets a Slack alert; at $5,000 the buyer is marked ineligible until the next day.
An insurance carrier accepts 25 connected calls per hour across their targets. With live call counting, the 26th concurrent call is blocked before it connects.
A publisher is contracted for 10,000 total calls per month. At 8,000 calls the ops team gets an in-app notification to evaluate pacing; at 10,000 the publisher is marked ineligible for the remainder of the month.
You’re testing a new publisher on an existing campaign — create a campaign-level converted call cap scoped to that publisher with a weekly timeframe to limit exposure while other publishers route without restriction.

Getting Started

Navigate to any entity (Target, RTB Target, Buyer, Campaign, or Publisher) and open the edit form.
Scroll to the Advanced Caps section.
Click Add Cap and select the cap type (connected calls, converted calls, total calls, or revenue).
Choose a timeframe (hourly, daily, weekly, monthly, or custom rolling) and set the limit value.
Configure the on-cap-reached behavior: lower bid / reduce value, warn at percentage, or mark ineligible.
Optionally enable live call counting and set a warning threshold percentage.
Save the entity. Caps take effect immediately on the next routed call.

Slack Alerts: To receive cap notifications in Slack, go to Settings → Slack Integrations, add your Slack webhook URL, and select the channel for cap alerts. Notifications will be sent for warning thresholds, cap-met, and cap-exceeded events.

Questions? Reach out to your account manager or contact support.

Originally published at https://help.mojaai.com/en/articles/13678762-release-notes-2026-02-09-caps-advanced-caps

Release Notes: 2026-02-09 — DNI — DNI Snippet Enhancements: Cross-Domain Tracking & Multi-Number Replacement

FEATURE ENHANCEMENT RELEASE

DNI Snippet Enhancements: Cross-Domain Tracking & Multi-Number Replacement

Two new configuration options are available on the snippet create/edit page: cross-domain visitor tracking and multi-number replacement.

What’s New

Cross-Domain Visitor Tracking — A visitor’s tracking number now follows them across different domains in your funnel. The snippet passes a visitor identifier via URL parameter so the destination domain assigns the same tracking number. Enable it in the new cross-domain tracking section on the snippet page.
Multi-Number Replacement — Replace multiple phone numbers on a single page, each with its own tracking number. Add entries in the “Multi-Number Replacement” section with a target number, optional pool override, campaign ID, and DOM selector per entry.
Per-Number Campaign Attribution — Use the data-moja-campaign HTML attribute to associate specific number placements with campaigns on multi-number pages.

Why This Matters

Cross-domain tracking keeps attribution intact when your visitor journey spans multiple websites. Multi-number replacement gives you per-line call tracking on pages with more than one phone number — no need to create separate snippets for each.

Getting Started

Navigate to Integrations → Snippets, open a snippet, and expand the new configuration sections. Save and redeploy your script.

Questions? Reach out to your account manager or contact support.

Originally published at https://help.mojaai.com/en/articles/13678835-release-notes-2026-02-09-dni-dni-snippet-enhancements-cross-domain-tracking-multi-number-replacement

Release Notes: 2026-02-11 — Platform — Ask AI Reporting — Smarter Queries, Better Answers

FEATURE ENHANCEMENT RELEASE

Ask AI Reporting — Smarter Queries, Better Answers

Location: Reporting → Ask AI

Release Date: February 11, 2026

Ask AI Reporting now handles more complex questions and delivers cleaner, more readable answers across your reporting workflows.

What’s New

Conversational follow-ups — Ask a question, then follow up naturally. “Which one had more calls?” or “is that a lot?” gets an instant answer from the data already on screen — no new query needed.

Smarter entity recognition — Ask AI uses context clues to understand what you mean. Mentions of publishers, campaigns, buyers, and targets are interpreted based on how you phrase the question. When context isn’t clear, the AI asks you to clarify.

Human-readable results — Results now show names — campaign names, publisher names, buyer names, organization names — instead of internal IDs.

Accurate conversion rates — Conversion rate queries now calculate against all call attempts, giving you a true performance picture.

Complex query support — Questions that involve combining result sets or multi-step comparisons are now fully supported.

Why This Matters

You can ask more of your data in fewer steps. Follow-up questions flow naturally, entity names are understood in context, and results come back in a format you can act on immediately.

Example Use Cases

Ask a reporting question, then follow up with “which one had the most?” — instant answer, no new query.
Request conversion rates by buyer or target and get accurate calculations across all call attempts.
Run multi-step comparisons across time periods and get a clean breakdown.

Getting Started

These improvements are live now. Navigate to Reporting → Ask AI and start asking questions.

Questions? Reach out to your account manager or contact support@mojaai.com.

Originally published at https://help.mojaai.com/en/articles/13706348-release-notes-2026-02-11-platform-ask-ai-reporting-smarter-queries-better-answers

Release Notes: 2026-02-19 — RTB — RTB Reporting — Outbound Visibility & Inbound Improvements

Release notes for RTB Reporting — Outbound Visibility & Inbound Improvements

FEATURE ENHANCEMENT RELEASE
RTB Reporting — Outbound Visibility & Inbound Improvements
Location: Reporting → RTB Requests
Release Date: February 18, 2026

Overview

This release expands RTB reporting in two ways: it adds a new Outbound section that shows what the platform sends to buyers, and it upgrades the existing Inbound view with new columns, filters, and pagination. Together, these changes give you a complete picture of RTB activity — publisher pings coming in and bid requests going out — in one reporting surface.

What’s New

New: Outbound Section
A new Outbound section now appears at the bottom of the RTB Requests report. It shows each outbound bid request grouped by request ID — with the campaign, publisher, buyer, number of steps, latest HTTP status code, state, and timestamp.

Each row groups all the individual bid steps for that request. Expand a row to inspect step-level detail: buyer endpoint, HTTP method, timing, request config, and the buyer’s full response. Config and response data open in a JSON viewer.

Outbound state — Each outbound request shows one of three states: COMPLETED, NO_ROUTES, or ERROR. States are color-coded in the table.
Latest HTTP status — A separate column shows the HTTP response code from the buyer’s last step (e.g., 200, 404, 500), color-coded by range.
Inbound Request ID — Each outbound request is linked to the originating inbound ping via an Inbound Request ID column. Use it to trace a full RTB request end-to-end: the publisher ping that triggered it, the outbound bid steps it generated, and the call outcome.

Updated: Inbound View
The existing inbound RTB Requests table has been updated with new columns and controls.

New columns — The inbound table now shows Caller ID, Campaign, Publisher, and Buyer alongside the existing State column.
Filters — Campaign, Publisher, and Buyer filter dropdowns are now available on the inbound view, so you can scope it to a specific slice of traffic.
Pagination — The inbound table now paginates server-side, improving performance for high-volume accounts.

New: Inbound/Outbound Toggle in RTB Statistics Summary
The RTB Statistics Summary now includes an Inbound/Outbound toggle. Switch to Outbound to see aggregate metrics — Requests, Responded, Connected, and Converted — broken down by campaign, publisher, buyer, and state.

Outbound filters — The Outbound view includes the same Campaign, Publisher, and Buyer filter dropdowns as the updated inbound view.

Why This Matters

Until now, RTB reporting showed what publishers sent in — but not what happened next. Outbound reporting closes that gap. You can see which buyer endpoints are responding, which are returning errors, and how bid outcomes connect to actual call conversions. The inbound improvements make it easier to find specific requests and understand their context without having to cross-reference other reports.

Example Use Cases

Filter the Outbound view by buyer to find an endpoint with a high rate of 500 errors — and confirm the issue before it affects fill rates.
Use the Inbound Request ID on an outbound row to trace a specific caller’s journey from publisher ping through buyer bid to connected call.
Compare Responded vs. Connected counts across buyers to identify which buyers are winning bids but not converting to calls.
Use the new Caller ID column in the inbound view to look up a specific caller’s RTB request without leaving the report.

Getting Started

Navigate to Reporting → RTB Requests.
Use the Campaign, Publisher, and Buyer dropdowns to filter the inbound view.
Scroll to the bottom of the page to find the new Outbound section.
Toggle between Inbound and Outbound in the RTB Statistics Summary to compare aggregate metrics.
Click any outbound row to expand step-level detail, or click a Config or Response cell to open the JSON viewer.

Questions? Reach out to your account manager or contact support.

Originally published at https://help.mojaai.com/en/articles/13767528-release-notes-2026-02-19-rtb-rtb-reporting-outbound-visibility-inbound-improvements

Release Notes: 2026-02-27 — Account — My Account - Manage Everything in One Place

What’s New: My Account — Manage Everything in One Place

Release Date: February 27, 2026

Overview

We’ve launched the My Account page — a centralized place to manage your company settings, subscription, team, billing, and payment methods without leaving the platform.

No more juggling external portals or hunting through different screens. Everything account-related is now in one place.

What You Can Do Now

View & Edit Account Information

See your company details at a glance:

Company name and account timezone
Your customer type (Brand, Network, or Publisher)
Verticals you support

Administrators can edit these settings directly.

Track Your Subscription

Full visibility into your plan:

Current plan and subscription status
Per-minute rates for each subscribed item
Next invoice date
Cancel your subscription anytime — no phone calls required

Manage Your Team

Control who has access to your account:

View all team members and their roles
Invite new users to your organization
Remove users when needed
Leave an organization yourself (unless you’re the last administrator)

Update Payment Methods

Keep your billing current without leaving the platform:

Update your credit card directly — no redirect to external portals
View your current payment method on file

Access Billing History

Stay on top of your costs:

View your complete invoice history
Download invoices as PDF

How to Access My Account

Log in to your account
Click “My Account” in the sidebar navigation
You’re there! All account sections are visible on one page

Who can see it: Administrators and team members. Publishers and buyers have focused access to their operational areas and won’t see the My Account page.

What Administrators Can Do


Action	Administrator	Team Member
View account information	✅	✅
Edit company name & timezone	✅	—
View subscription details	✅	✅
Cancel subscription	✅	—
Invite & remove team members	✅	—
Update payment method	✅	—
View & download invoices	✅	✅

Tips for Getting Started

Check your subscription details — Make sure your plan and rates look correct
Invite your team — Get everyone on the account who needs access
Verify your payment method — Update your card if needed to avoid billing interruptions
Download recent invoices — Great for expense reports or accounting

Questions?

Reach out to your account manager or contact support@mojaai.com.

Originally published at https://help.mojaai.com/en/articles/13890411-release-notes-2026-02-27-account-my-account-manage-everything-in-one-place