The CRM join, honestly

Salesforce Call Tracking Integration: The Honest Map

A Salesforce integration that logs calls against leads is genuinely useful — and we do not sell one. What we offer is the data layer: call detail records through our API, which your Salesforce reporting can meet. Here is the map, without the fake logo wall.

Prefer to talk? Call 1300 858 751
  • No fabricated integration
  • What the join should do
  • CDR data as the bridge

Integration questions

Do you have a Salesforce integration?

No — we do not sell a built-in Salesforce connector, and we would rather say so than borrow the logo. The honest bridge is data: our API exposes call detail records for your numbers, which your Salesforce-side reporting can ingest.

What does a Salesforce call tracking integration normally do?

Two jobs: match an inbound call to a lead or contact so the activity lands on the record, and attribute opportunities back to the campaign whose tracking number produced the call. Evaluate any connector against those two jobs with your own workflow.

What call data can your API provide for that join?

Per-call records for your numbers — timing, duration, service — appearing within about one to two minutes of each call completing, via the CDR area of our RESTful, bearer-token API described on the API page.

"Call tracking meets Salesforce" is one of the most requested joins in the category, and one of the most over-promised. This page will not claim a connector we do not have — we sell number-based call tracking on Australian infrastructure, not CRM integrations. What it does: explains what a good Salesforce integration actually does, how to evaluate one honestly, and where our data layer fits if you build the join yourself.

What the integration is supposed to do

Strip away the demo gloss and a Salesforce call-tracking integration does two jobs:

  1. Call-to-record matching. An inbound call arrives on a tracking number; the integration matches it to a lead or contact, so the call lands on the right Salesforce record with timing and duration.
  2. Campaign attribution. Because the call arrived on a number assigned to a specific campaign, the eventual opportunity can be traced back to the marketing source — closing the loop from spend to revenue.

Everything a vendor demos is some arrangement of those two jobs. Evaluate any connector by asking how it handles them at your call volume, with your match rules, on your Salesforce edition — documentation, not logos.

Our honest position: no connector, real data

We do not sell a Salesforce integration, and pages implying otherwise would be borrowing credibility. What we do provide is the data layer such a join consumes: the CDR area of our API exposes per-call records for your numbers — RESTful JSON, bearer-token authentication, records appearing within roughly one to two minutes of a call completing. If your team builds the Salesforce-side join — or runs it through middleware you already use — that is the feed it needs. The patterns for standing it up are in our API integration guide.

The boundary worth knowing before you build

Attribution by tracking number is campaign-level: which number, and therefore which medium, produced the call. It does not tell you which keyword the caller searched — that requires session-level platforms with dynamic number insertion, a different category. The candid split is in what call tracking software is. Match the integration depth to the question your Salesforce reports actually answer.

The sequence

Numbers first: tracking numbers from $5 a month per number, searchable on available numbers, with rates on the pricing page. Data second: the nightly CDR pull, walked through in getting started with the API. Join last — whether that join is a connector from a vendor who has one, or your own build on top of the records we expose.

Data first, connectors second

Generate the data worth joining

Tracking numbers from $5 a month per number — per-second call records your reporting can ingest.