Track contact clicks in the browser

The PingAura browser script records when visitors click to get in touch with you. In AI Traffic → PingAura Telemetry, the Contact clicks card shows those clicks by type, by AI source (ChatGPT, Perplexity, Gemini and more) and by page.

What it records

• Clicks on phone links (tel:).
• Clicks on email links (mailto:).
• Clicks on WhatsApp links (wa.me and api.whatsapp.com). The phone number in the link may include spaces, dashes or a plus sign. Share links without a phone number are not counted.
• Clicks on the Joinchat WhatsApp button on WordPress.
• Clicks on any element with data-pingaura-track="your_event_name".
• Calls to window.pingaura.track('your_event_name').

Events you send with track() from the telemetry SDK on your server also appear in the Contact clicks card, alongside the clicks from the browser script.

A click shows interest. It does not mean a call was made or a message was sent. The phone number, email address and message text are never recorded, only that a click happened, on which page, and which AI source brought the visitor.

Before you begin

• Your domain is added to PingAura.
• PingAura Telemetry is on your plan, the same as the rest of AI Traffic telemetry. If the PingAura Telemetry tab in AI Traffic shows an upgrade notice, contact your account team.
• You can add a script tag to your site.

Step 1: Create a browser key

1. In PingAura, go to Workspace settings → API & MCP.
2. Click Create Key and choose Browser.
3. Copy the key.

Step 2: Add the script

Add this to every page, before </head>:

<script src="https://telemetry.pingaura.ai/t.js" data-key="YOUR_BROWSER_KEY" data-domain="example.com" defer></script>

• Replace YOUR_BROWSER_KEY with the key from step 1.
• Set data-domain to a domain registered in PingAura, without https:// or www.. The script only works on that domain and its subdomains.

That's it. Clicks on phone, email and WhatsApp links are recorded with no further changes.

Track your own buttons

Add data-pingaura-track to any element whose clicks you want to count:

<a href="/book" data-pingaura-track="book_demo">Book a demo</a>

Or record a click from your own code:

window.pingaura.track('book_demo');

Event names use lowercase letters, digits and underscores, up to 40 characters. For example book_demo or request_quote.

If your code may run before the script has loaded, queue the call instead. It is sent once the script loads:

window.pingaura = window.pingaura || [];
window.pingaura.push(['track', 'book_demo']);

window.pingaura.push(['track', 'name']) works both before and after the script loads, so you can always use it.

Is the key safe in my page?

Yes. The browser key is public by design. It can only send click events from your own domain, and it cannot read any data.

Server keys with the ingest scope are different. Never put an ingest key in a web page.

Privacy

The script remembers the site that first referred the visitor and the utm_source of their landing page in the browser's local storage for 30 minutes of activity, so a click in another tab is still credited to the right AI source. It does not set cookies.

Moving between pages on your own domain and its subdomains keeps the AI credit. Each subdomain keeps its own memory, so a click on a different subdomain than the one the visitor landed on starts fresh there.

PingAura uses the visitor's IP address to work out the country, to limit abuse, and to filter bots, and uses the user agent to filter bots. The IP address is not stored with the click. If your site needs consent for analytics, load the script after consent.

How accurate the counts are

Because the key is visible in your page, someone could send made-up clicks with it. PingAura limits how many clicks it accepts per visitor and per site, so treat the counts as a guide to interest rather than an exact tally.

Where it works

Anywhere you can add a script tag: WordPress, Webflow, Shopify, Wix, Framer, Next.js and plain HTML.

The script supports current versions of Chrome, Edge, Firefox and Safari (Safari 11.1 or later). Older browsers simply do not send clicks.

On WordPress, if you use a speed plugin that delays JavaScript (WP Rocket, LiteSpeed Cache, Perfmatters), exclude telemetry.pingaura.ai/t.js from delay so the first tap is counted.

The script does not send page views. Page views keep coming from your existing PingAura Telemetry setup: the telemetry SDK on your server or edge, or the WordPress plugin.