Skip to main content

Revenue Postback Endpoint

D
Written by Denise Abdullah
Updated over a month ago

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.

Did this answer your question?