Call log column dictionary

Who this is for: anyone reconciling reporting, building an export, or trying to work out what a column actually counts before they base a payout on it. Where this lives: Reporting → Call Logs · Reporting → Call Logs → Call Summary

This is a reference, not a walkthrough. For the diagnostic process — narrowing a time range, tracing one call, deciding whether a problem is routing or configuration — see How to read call logs.

Scope of this reference

The fields below are the ones documented in the product help centre and release notes. The complete list of selectable Call Log columns, their exact display names, and which are included in an export are not documented anywhere today — see the [CONFIRM] block at the end. Where this page and the portal disagree, the portal is right.

How columns work

Two kinds of column appear in the Call Log:

System columns are always available — the identifiers, routing, status, and financial fields below.

Custom tag columns are yours. A tag that is already arriving on calls does not automatically appear in the column dropdown: the tag has to be added under Custom Tags first, with the name spelled exactly as it appears on the call. Once added, it becomes selectable as a Call Log column.

That applies to tags created anywhere — a call flow, a script, an inbound webhook, DNI, or an inbound RTB request. If calls are receiving a tag like voice_agent, you have to add voice_agent as a Custom Tag before you can put it in a column.

Call identity and timing

Field	What it means	What to check
Call log ID	Unique reference for the call	Quote it in any support conversation so the exact call can be traced
Timestamp	When the call happened	Confirm the event time and the timezone. Campaigns and targets each carry their own configured timezone, and reporting follows that rather than your local time
Caller ID	The caller’s phone number (ANI)	Use it to find repeat callers, duplicates, or a specific reported call. This is the number matched by postbacks and webhooks — not the number dialled
Tracking number	The number that received the call	Confirm the call entered through the number you expect
Direction / source	How the call entered Moja	Distinguishes a tracking-number call from an inbound source or an RTB flow

Attribution

Field	What it means	What to check
Campaign	The campaign matched to the call	A call under an unexpected campaign usually means the tracking number is attached somewhere you forgot
Publisher / source	The traffic source tied to the call	Empty here means no publisher was set on the number in the campaign’s number group
Routing plan	The routing logic used	Compare against the campaign’s intended routing setup
Selected buyer	The buyer selected for the call	Empty means no eligible buyer was found
Selected target	The destination target selected	Empty means no eligible destination — check target status, hours, caps, filters, and routing rules

Outcome

Field	What it means	What to check
Call status	The call outcome	Connected/completed, failed, timeout, missed, or a disconnect status
Disconnect reason	Why the call ended or failed	Separates caller hangup from buyer failure, timeout, carrier issue, and system issue
Duration	How long the call lasted	Compare against the duration or conversion rule on the target
Conversion status	Whether the call met the configured qualification rule	A connected call only earns revenue if it meets the buyer payout or conversion rule
Revenue / payout	The financial outcome	If empty or zero, check duration, payout rules, buyer qualification, and revenue configuration
Recording	Audio recording, when enabled and available	Recording can be disabled above the campaign, by the buyer or publisher

RTB

Field	What it means	What to check
RTB request ID	Reference back to the RTB request	Use it to line the call up against RTB logs, bid responses, and reject reasons

Fields in this group appear only on calls that used an RTB flow. For bid-side troubleshooting, RTB Logs — not Call Logs — are the right surface.

Duration and cost in Call Summary

Call Summary shows Total Billable Minutes (TBM) rather than raw Total Call Length when billing data is available. TBM is the sum of per-call minutes rounded up to the nearest minute — the same minutes used to calculate Cost — so summary duration reconciles against how calls are billed. If billable minutes are not returned, Call Summary falls back to TCL.

The call log grid still shows Total Call Length only; there is no TBM column on the grid. Buyer and publisher summary views are unchanged.

Note

This is the single most common reconciliation surprise: a 12-second call and a 55-second call are both 1 billable minute, so TBM will exceed TCL on any account with lots of short calls. That is arithmetic, not an error.

System call-state tags

Moja writes positive stage tags onto the call during the call, for the voice agent path, the buyer/target path, and RTB attribution. They are system tags on the call log — available for review, filtering, and reporting — and they do not require a recording.

Tag	Meaning
LAST_VOICE_AGENT_ATTEMPTED	Voice agent node entered
LAST_VOICE_AGENT_REACHED	Voice agent actually connected
LAST_VOICE_AGENT_HANDOVER	Handover confirmed
LAST_VOICE_AGENT_FINISHED	Voice agent finished, including after a tool-call handover
LAST_BUYER_ATTEMPTED / LAST_BUYER_REACHED	Buyer or target dialled / answered
BUYER_FAILURE_REASON	Why the buyer path failed — no bid, busy, no-answer, and similar
LAST_RTB_GROUP / LAST_RTB_FORMULA	RTB attribution, alongside ping timing tags

These tags track platform stages — agent, handover, buyer, RTB — not every line inside a voice agent script. Step-level reporting inside a script depends on the agent collecting and handing over those fields as tags of its own.

Filter the Call Log on these tags to build views such as “agent reached, no buyer connected.”

Note

Calls from before these tags existed keep the prior Call Summary behaviour. Only traffic after the 22 July 2026 release uses the tag-based funnel — so a period spanning that date will not compare cleanly.

Voice agent columns in Call Summary

Built on the same tags:

Column	What it counts
VA Conn / VA No Conn	Whether the voice agent connected, over the voice-agent-eligible call set
VA Buyer Conn	Agent path completed and a buyer connected
VA Buyer No Conn	Buyer was attempted but did not connect
VA No Buyer	No buyer was attempted after the agent path
VA Dropoff Before RTB	Call ended before the RTB stage
VA Empty Handover	Handover happened with nothing carried through
VA Buyer Conn %	Connected ÷ (connected + buyer no-connect + no buyer). Dropoff and Empty Handover are deliberately excluded

Column header tooltips give the in-product definition for each metric. Where a tooltip and this page disagree, trust the tooltip.

Google Ads attribution columns

On accounts using the Google Ads integration, Reporting / Call Tracking adds:

Label / column	What it counts
WITH GCLID	Calls carrying a captured Google click ID
CONVERSIONS	Calls counted as conversions
UPLOADED	Conversions uploaded back to the ad platform
Tracking IDs	The captured tracking identifiers on the call
Conversion Value | Type	Conversion value and conversion type

See Send call conversions to Google Ads.

What an empty value means

Empty field	What it may mean
No buyer or target	No eligible destination was selected. Check routing plan, target status, hours and timezone, caps, filters, and duplicate rules
No revenue or payout	The qualification rule was not met, or payout/revenue is not configured for that outcome
No recording	Recording is disabled, the call did not connect, or the recording is not yet available
No RTB reference	The call did not come from an RTB flow
No row at all	The call never reached Moja, or the tracking number and source are misassigned

Call Life

Reporting → Call Log → open a call → Call Life gives the event timeline for that single call: routing decisions, pre-bridge and preconverted checks (grouped, so long logs stay readable), and inbound RTB activity. A side detail panel opens an individual event without losing your place on the timeline.

Call Life answers “what happened, in what order.” The columns above answer “what was the result.” Use Call Life whenever the columns disagree with what you expected.

Exports

The Numbers page exports inventory and campaign association — that is a different export, documented in Manage your number inventory.

[CONFIRM — product]

To finish this reference, product needs to confirm:

1. The complete list of selectable Call Log columns and their exact display names as rendered in the column dropdown, so this page can be checked against the product rather than assembled from release notes.
2. Which columns are included in a Call Log export, and whether the export follows the currently selected columns or a fixed set.
3. The enumerated values for Call status, Disconnect reason, and BUYER_FAILURE_REASON — the release notes list examples (“no bid, busy, no-answer, etc.”) rather than the closed set. A cause-and-fix row per value is the single highest-value addition to this page.
4. The timestamp format and timezone displayed in the grid and returned in exports. The v1 REST API declares created_at, updated_at, and paused_until as OpenAPI date-time (RFC 3339) in the published spec, but Call Life’s event_time is an untyped string, and the webhook macro timestamps are not specified anywhere.
5. Whether custom tag columns appear in exports on the same terms as system columns.

Related

• How to read call logs — the diagnostic process
• Keep ping and publisher fields on the call with custom tags
• Why am I getting calls but no revenue?
• Why am I seeing RTB logs but no call logs?
• Ask AI reporting