What the tracking script collects¶
This page lists what the tracking script sends to Enfonica and what it stores in the visitor's browser, so you can answer privacy questions and complete a website's cookie notice.
Sent to Enfonica¶
On each page view, and periodically while the visitor is active, the script sends:
- The tracking site's code.
- A random session ID generated by the script.
- The page URL, including the query string, and the referrer.
- Campaign parameters and ad click IDs from the URL:
utm_*,gclid,gbraid,wbraid,dclid,fbclid,msclkid,ttclid,li_fat_idandtwclid. - The values of Google Analytics
_gaand_ga_*cookies, if present, so calls can be linked to the same session in Google Analytics 4. - What the browser reports about itself: the user agent, and where the browser provides them, its device type, platform and browser brand, the number of touch points and the screen width. Call Tracking keeps only the derived device category (mobile, tablet or desktop), browser family and operating system family.
Call Tracking derives an approximate location from the visitor's connection. The address itself isn't kept in readable form.
Not collected¶
- Cookies other than Google Analytics cookies.
- Form input, page content or keystrokes.
- The visitor's name, email or phone number. The caller's phone number is captured by the phone network when they call, not by the script.
- Which numbers were swapped on the page.
Stored in the browser¶
The script keeps a session identifier in the browser's web storage, which identifies the visit for 30 minutes after the last activity. The script doesn't set cookies.
Where data goes¶
Session and call data are stored by Enfonica in Australia. Calls are sent to third parties only through the integrations you enable, and the caller's phone number is never sent to Google Analytics, Google Ads or Meta Ads. See Integrations overview for what each integration receives.
Requests from the browser¶
The script makes requests to https://ctjs.au only. See Content Security Policy.