Calltouch Integration for Call Tracking and Number Replacement
Call tracking often becomes a black box: calls exist, but it's unclear which visits they belong to. A standard callback script provides a funnel but doesn't link it to the traffic source. Calltouch solves this—number replacement, webhooks with call context, and ready analytics. We've completed over 50 such integrations and know where N+1 CRM queries or session_id losses usually pop up. Contact us for a consultation—we'll tell you how to implement call tracking without pain.
Why Calltouch Call Tracking Matters for Ad Analytics
Without linking a call to UTM tags, you're spending your budget blind. Calltouch automatically assigns source, medium, campaign, and keyword to each call. This lets you see which ads led to an actual conversation, not just a click. On one project (electronics e-commerce), after implementing number replacement, call-to-lead conversion increased by 30%—thanks to proper attribution and disabling inefficient channels. Advertising budget savings reached up to 40%.
How Calltouch Number Replacement Works
Calltouch uses dynamic replacement: each visitor gets a unique number based on the source. According to Calltouch documentation, this allows distinguishing calls from Yandex.Direct, Google Ads, social networks, and organic. The algorithm works as follows: the script on the site determines UTM tags, requests a number for that combination from the Calltouch server, and inserts it into the HTML. After the session ends, the number is freed.
Compare attribution effectiveness:
| Parameter | Without Calltouch | With Calltouch |
|---|---|---|
| Call attribution accuracy | ~30% | ~95% |
| Time to create a lead | 5 min (manual entry) | 1-2 sec (automatic) |
| Lead duplicates | Frequent | Excluded |
How to Set Up Call Transfer to CRM
The standard method is webhooks. When a call ends, Calltouch sends a POST request to your endpoint. Example in Laravel:
Route::post('/webhooks/calltouch/call', function (Request $request) { $data = $request->all(); Lead::create([ 'phone' => $data['callerNumber'], 'source' => 'calltouch', 'utm_source' => $data['utmSource'] ?? null, 'utm_campaign'=> $data['utmCampaign'] ?? null, 'duration' => $data['callDuration'] ?? 0, 'session_id' => $data['sessionId'] ]); }); This is enough for a basic CRM. If you also need call recording, Calltouch sends a link to the audio file in the callRecordUrl field. It's important to catch duplicates: the same call may come twice (due to webhook retries). Solution — check uniqueness by sessionId.
Detailed Webhook Setup Steps
- In your Calltouch account, go to "Settings" → "Webhooks".
- Specify your endpoint URL (e.g.,
https://example.com/webhooks/calltouch/call). - Select events: "Call Start", "Call End" (both are necessary for full analytics).
- Save and test: make a test call—data should arrive on your server.
- Handle duplicates: implement a check by
sessionIdor use server-side cache.
Call Tracking Installation
The initialization script goes into <head>:
<!-- Insert into <head> --> <script type="text/javascript"> (function(n,e,o,r,i) { if (!n[i]) { var c = n[i] = function() { c.queries ? c.queries.push(arguments) : c.run ? c.run.apply(c, arguments) : c.queries = [arguments] }; c.q = []; var s = e.createElement(o); s.type = "text/javascript"; s.async = !0; s.src = (r ? "https:" : "http:") + "//mod.calltouch.ru/init.js?id=SITE_ID"; e.getElementsByTagName("body")[0].appendChild(s) } })(window, document, "script", document.location.protocol === "https:", "ct"); </script> After that, enable number replacement in your Calltouch account—the platform itself determines which number to show to the visitor based on the source.
JavaScript API — Passing User Data
To link a call to a specific request, pass the email or session ID:
// Pass user's email for CRM matching ct('setEmail', user.email); // Pass custom request data ct('setData', { order_id: orderId, order_total: total, utm_source: utmSource }); Integration with Yandex.Direct and Google Ads
Calltouch can send call conversions back to ad systems. Configure this in your Calltouch account without code. Compare with manual upload:
| Approach | Time spent per month | Error risk |
|---|---|---|
| Manual export | 4-5 hours | High |
| Calltouch | 10 minutes | Minimal |
Common Integration Errors
The most common is N+1 queries to CRM when processing each call. If the site has 1000 calls per day and each CRM request hits the database, the webhook response time increases. Solution — batch processing: collect calls in a queue (e.g., Redis) and save them in batches every 5 minutes. The second problem is losing session_id on page reload: save it in localStorage and pass during script initialization.
On one project, the CRM rejected calls without UTM tags. We added a fallback: if no UTM tags, set "organic". This increased attribution by 15%.
What's Included in the Work
- Installing call tracking and number replacement scripts.
- Configuring webhooks to transfer calls to your CRM (amoCRM, Bitrix24, RetailCRM, custom).
- Integration with Yandex.Metrica and Google Analytics ("Call" goals with UTM tags).
- Testing correct operation, handling errors (timeouts, retries).
- Architecture documentation and operator instructions.
Timelines and Pricing
Standard integration with one site takes 1 to 3 business days. If custom logic is needed (e.g., non-standard CRM or complex assignment scenarios), the timeline increases to 5 days. The cost is calculated individually after assessing the scope of work.
Why Choose Us
- 5+ years of experience in call tracking integrations.
- Over 50 projects with Calltouch, including high-load e-commerce stores.
- We provide a guarantee on settings: if an error is discovered within a month, we fix it for free.
Order Calltouch integration—get accurate call analytics and reduce lead loss. Contact us for a consultation.