How to Mark a Call as Converted

What Conversion Means

Marking a call as converted signals that the call produced a
billable outcome: a sale, a qualified lead, a booked appointment,
or whatever the offer defines as a success. Conversion drives the
revenue calculation for buyers and the payout calculation for the
offer.

Calls track two independent conversion booleans:

buyer_converted - buyer-side conversion. Labeled Buyer Converted? in the Call detail UI. Counts toward buyer caps and buyer payouts.
offer_converted - offer-side conversion. Labeled TS Converted? in the Call detail UI (Traffic Source Converted). Used when offer-side and buyer-side conversion do not always align.

Automatic Conversion

Conversion is usually set automatically. The common mechanisms:

Duration-based. Any call lasting longer than a configured threshold converts.
Buyer conversion rules. Each buyer owns a set of rules that match on call tokens and apply within a defined business-hours range; the first matching rule converts the call.
Webhook-based. The buyer posts to a conversion webhook at the end of the call to confirm the sale.
Voice-agent-based. A keyword match or sidecar-extracted token fires a conversion.

Check the offer's and the buyer's conversion settings to see which
automatic mechanisms are active.

Manual Conversion via the UI

From the Call detail page, a user with the appropriate permission
can flip either conversion flag manually. The conversion area
shows two checkboxes:

Buyer Converted? with a Buyer combo box below it for selecting which buyer receives the conversion.
TS Converted? with the tooltip "Did The Traffic Source Convert?" and a Traffic Source label below it.

A Revenue input renders next to the checkboxes for users
granted the revenue permission on Call. Click Save Changes
at the bottom of the page to update; changes are recorded so
revised conversions can be traced.

Manual Conversion via the API

Two endpoints accept conversion updates:

PUT /api/v1/calls/:id with buyer_converted=true and optional revenue=<amount>, authenticated with a standard API key.
PUT /api/v1/secure/:secure_token/calls/:uuid for externally-initiated updates from a buyer system, authenticated by a per-company secure token and addressing the call by its UUID rather than its database id. Example:

  curl -X PUT \
    "https://your-domain.com/api/v1/secure/SECURE_TOKEN/calls/CALL_UUID?buyer_converted=true&revenue=10"

Both endpoints accept offer_converted as a separate parameter
when recording an offer-side conversion independently.

Effect on Billing

Converting a call triggers the billing pipeline to create the
appropriate charges, credits, and payouts on the next rollup.
Reversing a conversion (flipping the flag back to false) creates
offsetting entries. All billing adjustments made through
conversion flips are visible in the Call's billing detail panel.