Ringba Bridging

Ringba bridging is configured through outgoing webhook templates.
The exact templates customers use (for example, "RINGBA ENRICH" and "RINGBA WEBHOOK")
are global event triggers that can be selected from the available templates under Event Triggers.

This article describes the bridging mechanism. Specific template configurations
and token mappings may vary by company.

Two-Way Enrichment

Ringba and TrackDrive can each act as either the originator or the receiver.

The bridge typically works in one of the following ways:

TrackDrive Originates, Ringba Receives

An outgoing webhook posts call data to Ringba's ingestion endpoint.

Webhook trigger:
- Call – Fire during the call, before dialing the buyer

Behavior:
- TrackDrive sends call data to Ringba.
- The webhook body contains TrackDrive tokens mapped to Ringba's expected field names.
- Ringba receives and processes the enrichment payload.

Ringba Originates, TrackDrive Receives

Ringba posts data to TrackDrive using the posting instructions generated
from a TrackDrive offer's Posting Instructions section.

Required values:
- Lead token
- Traffic Source ID
- Endpoint URL

These values should be used exactly as specified in the posting instructions.

Identifying the Call Across Systems

Each system must be able to reference the same call using an identifier
recognized by both platforms.

Pattern 1: TrackDrive UUID Sent to Ringba

• TrackDrive sends the call UUID to Ringba's enrich endpoint.
• Ringba stores the TrackDrive call UUID.
• Ringba includes the UUID in any return webhook along with:
  • Publisher payout
  • Conversion status

Pattern 2: Ringba UUID Stored in TrackDrive

• TrackDrive accepts a Ringba-side identifier in a custom contact field.
• A common example is a field containing the Ringba call UUID.
• When a Traffic Source conversion occurs, TrackDrive posts the payout back using the received Ringba call UUID.

The exact field names are user-defined. Use naming conventions that make
the data flow clear and maintainable on both sides.

Ping/Post Variant

For ping/post integrations where TrackDrive pings a Ringba buyer before transferring the call:

1. TrackDrive sends a ping request to Ringba.
2. Ringba returns a ping response.
3. If the response is successful:
   • TrackDrive routes the call to the phone number returned in the response.
   • TrackDrive applies any attributes returned in the ping response.
   • The call is then transferred according to the routing information provided by Ringba.