Call tracking

CallTrackingMetrics

Send completed calls to OrcLink by webhook. Each call becomes a call outcome.

Built, not yet tested liveBuilt. Not yet tested against a live CallTrackingMetrics account.

Live: shipped in OrcLink's production release before this one. Built, not yet tested live: built and tested with sample data, not yet run against a live account of the vendor. Coming soon: listed, not available to connect yet.

How to connect

Dashboard > Integrations > CallTrackingMetrics > Connect. Copy the webhook URL and the secret (shown once) into CallTrackingMetrics.
Send completed calls to https://<your OrcLink host>/api/webhooks/ctm/<workspace id> (the Integrations card shows the exact URL).
Use the secret as the HTTP Basic-auth password of the webhook (CallTrackingMetrics cannot send custom headers).

What OrcLink reads

Each completed call: times, duration, result, the tracking number, the caller number (hashed on receipt), its source and landing page, and gclid / fbclid / msclkid when CallTrackingMetrics has them. Texts, forms and calls still in progress are not read as calls.

What OrcLink writes back

Nothing.

Never stored

Raw email addresses and phone numbers: hashed (SHA-256) the moment they arrive.
The raw payload: only its SHA-256, for provenance.
Your credentials and webhook secrets in clear: they are stored encrypted (AES-256-GCM).

Known limits

A call keeps a hash of the caller number, its last 4 digits, the tracking number dialled, the call times and result and a recording reference (not the audio). The full caller number only if you turn that on, never in HIPAA mode.