Skip to main content

Call Details Report Events Reference

Amanda Cross
Updated

The Call Details report appears at the bottom of the Reporting screen. This report contains:

When you click the arrow on the left side of the row, the row expands to show tabs of information. For example you might see tabs like Events, Record, Tags, Ring Tree Events, or Transcript. 

call_details_report_events_tab.png

This article contains descriptions of the events you might see in the Events tab. It contains the following sections:

Events

The following sections contain the list of events divided into categories for easier reference.

Call Lifecycle Events

These events capture the standard phases of a call in Ringba: 

  • Inbound Call: Call arrived at Ringba system (start of lifecycle).
  • Connected: Call successfully connected to a target.
  • Converted: Call met the campaign or target's conversion criteria.
  • Completed: Call ended and all post-call processing finished.
  • Call Annotation With Tags: Call was annotated with custom tags.
  • Duplicate Call: Ringba flagged the call as duplicate based on campaign/account settings.
  • Blocked Call: Call never connected because Ringba identified the call as undesirable. Ringba blocks calls for a variety of reasons. For example, spam calls, calls from numbers professional litigators identified by TCPA Shield, and calls from numbers you have blocked.
  • Incomplete Call: Call ended before completion (e.g., dropped, not fully processed).
  • End Call Source: This event shows which party (caller, target, or system) ended the call and the time it ended.
  • Target Dialed: Ringba dialed a target. This event might include cost and routing details.
  • Busy Call: Ringba dialed the target, but the target was busy and the call did not connect.
  • No Answer: Ringba dialed the target, but the target did not answer and the call did not connect.
  • Error: A system error occurred during call routing or connection attempt.
  • No Targets Answered: Ringba attempted to dial all eligible targets, and all failed to answer. The call did not connect.
  • No Target Found: Ringba found no eligible or available targets so the call did not connect.
  • Rejected For Funds: Ringba prevented the call from connecting to a target because it had insufficient funds.

Call Flow Events

These events occur when a call comes in to a campaign that has an associated call flow.

  • Voice Mail: Call reached a Voicemail node in the call flow and connected to voicemail.
  • Split Test Selected: Call reached a Splitter node in the call flow and Ringba selected a routing for the call.
  • IVR Node Enter: Call entered a Gather node in the call flow.
  • IVR Node Exit: Call exited Gather node node.
  • User Input: User input was received during IVR.
  • User Input Fail: User input failed during IVR.

Caller Information Events

These events occur when you collect information about the caller ID in advance of the call.

  • Data Enrichment: Data enrichment was performed for the call.
  • Custom Data Enrichment Success: Custom data enrichment succeeded.
  • Custom Data Enrichment Failure: Custom data enrichment failed.
  • Blacklist Check: Blacklist check was performed for the call.
  • TCPA Shield Check: TCPA Shield compliance check was performed.

Payout and Conversion Events

These events capture the parts of the call lifecycle where the call converts and the publisher does or does not get a payout credit:

  • Payout Call: The publisher received payout credit for this call.
  • No Payout: The publisher did not receive payout for this call, such as because the call did not satisfy the payout criteria. The event includes the reason.
  • No Conversion: The call did not meet the campaign's conversion criteria. The event includes the reason.
  • Voided: The call completed, but an admin user invalidated the payout by setting the amount to zero.
  • Conversion Adjustment Requested: The publisher request an adjustment to the conversion status of the call.
  • Conversion Adjustment Approved: The publisher's request to adjust the conversion status of the call was approved.
  • Conversion Adjustment Rejected: The publisher's request to adjust the conversion status of the call was rejected.
  • Call Payments Adjusted: The payment for this call was adjusted manually.
  • Voided Conversion: The conversion for this call was voided manually.
  • Call Profit: Profit calculation for the call.  

RTT and RTB with Passthrough Events

These events happen for calls that go through a ring tree target or through a real-time bidding with pass through campaign:

  • Ring Tree Pinging Summary: This event summarizes the results of all ring tree pings for the call, including the ring tree name and ID, each target's name and bid, and the required duration on the bid.
  • Ring Tree Target Raw Result: This event captures the raw response and details from a ring tree target ping.
  • Ring Tree Success: Ringba successfully pinged a ring tree. This event includes the bid and call info.
  • Ring Tree Failure: Ringba attempted to ping a ring tree during routing, but the ping failed.

RTB Events

These events apply to calls in a real-time bidding (RTB) campaign:

  • Routing Plan: This event shows which targets were eligible or ineligible for routing during the call.
  • Custom Scoring Check: This event shows the outcome of custom scoring logic applied to the call.
  • Jornaya TCPA Check: This event documents TCPA compliance verification for the call using Jornaya.
  • Winning Ping: Indicates the winning ring tree target ping.
  • RPC Calculation Summary: Summarizes how Revenue Per Call (RPC) was calculated for this call.
  • Bid Trace: Provides a trace of all RTB bids made for the call.
  • RTB Reroute Eligibility Checks: Summary of RTB reroute eligibility checks for the call.
  • RTB Winning Bid: This event records the winning bid and related details.
  • Confirmation Request Success: This event captures a successful confirmation (second ping) to a target.
  • Confirmation Request Failure: This event captures a failed confirmation (second ping) to a target.
  • Confirmation Request Raw Result: This event captures the response and details from a confirmation (second ping) request.
  • TrustedForm Check: This event indicates Ringba checked TrustedForm to ensure the number had a consent certificate.
  • Second Step Passthrough Pings: Summarizes passthrough pings in multi-step RTB routing.
  • Zero RTB Bid: This event records that no RTB bid was made or all bids were zero.

Recording and Transcription Events

These events capture the processes of recording the call and transcribing the call recording:

  • Recorded: This event shows the system processed the call recording and added a link to the call record. The event includes the buyer name and ID and the link to the recording.
  • Transcription: This event shows the system transcribed the call recording and added it to the call record.
  • Transcription Requested: This event shows the transcription request (pending or in progress).
  • Transcription Error: This event shows the requested transcription failed or encountered an error.

Revenue Recovery Events

These events apply to calls that go through the revenue recovery process after a target ends the call too soon:

  • Revenue Recovery Summary: This event lists the ineligible targets and the reason they were ineligible as well as the eligible targets.
  • Revenue Recovery: This event indicates that rerouting the call according to revenue recovery logic was triggered by the target ending the call too early.
  • Incoming Revenue Recovery: This event indicates the beginning of the next leg of the call after it was rerouted according to revenue recovery logic.

Information Exchange Events

These events relate to calls where the process includes sending or receiving information to or from an outside system:

  • Call Webhook: This event shows the account received call data from an outside system via webhook.
  • Pixel Fire: This event indicates that a tracking pixel fired.
  • Upload Offline Conversion: If an attempt to upload data to another system fails, Ringba tries again a number of times. This event appears to capture each attempt, so this event might have different meanings:
    • Offline conversion data was uploaded for the call (e.g., to ad platform).
    • Google Ads offline conversion upload succeeded for this call.
    • Google Ads offline conversion upload failed for this call (reason attached).

Call Details Report Events Reference FAQ

What if I still have questions about the information I see on the Call Detail Report Events tab? 

If you have any questions or need additional help, please reach out to our support team via chat or email at support@ringba.com.

Related to

Related articles