Calltag connects the visit on your site to the call that follows. The published number stays on the page.
Visitors call the number you already publish. Calltag does not swap it for a tracking pool.
A click and a call meet when they belong together. The result is one row, not two reports.
Click events and call records are hosted in the EU.
How it works
Calltag links online sessions to inbound calls with time-based matching or a match code—without changing the number visitors see.
Time-based matching
When a visitor taps your number, Calltag records the moment. When your phone system reports the inbound call, the two meet inside a short time window—one attributed record, no code to type.
01
A small tag records the click on the page that shows your number.
02
Your phone system reports the inbound call to the same published number.
03
Calltag joins them inside your configured time window into a single record.
Match-code matching
For exact attribution—or when you need visitor answers before the agent answers—Calltag issues a short match code at the click. After the call connects, the caller enters the code; your call system resolves it and the session is matched with certainty.
01
The visitor taps your published number on the page.
02
Calltag generates a short match code tied to that visit and its attributes.
03
After the call connects, the code is entered—by the caller or dialed automatically.
04
Your call system resolves the code. Calltag returns the visitor and creates the match.
Why track calls
When someone dials after browsing your site, that conversation is often your highest-intent conversion. Calltag makes those calls measurable, optimizable, and actionable.
Attribute offline phone conversions to the online traffic sources that drove them—campaign, page, and session—so paid and organic channels stop carrying blind spots.
Push matched calls in real time as conversion signals back to marketing platforms, DSPs, and sources like Meta and Google. Close the loop, improve bidding, and grow lookalike audiences from callers who actually convert.
Send call outcomes into your web analytics stack—Google Analytics, Adobe Customer Journey Analytics, Matomo, and more—so phone and digital live in the same journey view.
Once the visitor is recognized on the call, route them to the right team immediately. Skip the maze of IVR menus that turn high intent into frustration.
Pre-call forms
The moment a customer reaches for the phone is not the moment to test their patience. It is the best moment to impress them.
Pre-call forms ask what customers need before they dial—on the page, in a short wizard—then pass those answers with the match code. Ambiguous, maze-like after-call journeys disappear. Agents already know the intent. Time from number click to a real person shrinks. Appreciation shows up later: when the agent has room for a thoughtful cross-sell instead of an apology for the hold music.
Tedious keypad trees and hard-to-follow menus cost customers time and nerves—and cost you trust. By eliminating IVR selection, you already know what callers expect from the contact, and you give agents a fair chance to deliver it.
Ask intent after the call
IVR maze
Keypad trees, ambiguous options, hold time—intent cools before an agent answers.
Know intent before the call
Pre-call form
Answers travel with the match code. The right team picks up—already briefed.
AI agents
When your customer service runs on AI agents, every unanswered question at the start of a call is a wasted opportunity. Calltag delivers vital information to your Agent about who the visitor is, what they need, and whether they consented to an AI interaction—before the agent even starts.
Pre-call answers travel with the match code into your call system. The AI agent opens with customer identity, page context, and call intent already in hand—so it can resolve more conversations on the first try and escalate fewer contacts to a human desk.
Ask for any required consent to interact with an AI agent while the visitor is still on your website—clear, intentional, and before the dial. Preferences travel with the session, so your voice AI can start compliant and confident from the first turn.
Secure pre-call authentication
When a customer is already signed in on your website, Calltag's match code can do more than attribute the visit. A sufficiently long, short-lived one-time code becomes an authentication key for the call itself—so agents stop verifying identity with birth dates, Social Security digits, or ZIP codes spoken over an open line.
An 8-digit one-time code that expires in minutes is unique enough to act as a one-time authentication key, especially when combined with the caller's phone number. It is bound to the signed-in web visitor's session, issued at the click, and resolved when the call connects. Guessing or spoofing it is impractical; sharing a birthday or ZIP is not.
Verbal knowledge checks waste time for agents and customers—and they are easy to spoof with data that already circulates online. Match-code authentication removes those questions from the conversation, shortens handle time, and raises the bar for anyone pretending to be the account holder.
Your data is safe
Click events and call records are hosted in the EU.