Short answer
Test call tracking with fresh sessions before a choice, after acceptance, after rejection and after consent withdrawal. Check network requests and storage as well as the displayed number. A banner alone does not establish script control; limited attribution needs to remain identifiable in reports.
Key verification: Confirm measurement requiring consent does not start before the choice and withdrawal follows the defined procedure.
Sources and limitationsA visible banner can coexist with a measurement script that has already transmitted data. This guide proposes a technical consent journey test for a website using call tracking. It does not certify legal compliance or install tracking on CallsIQ; this publication remains static pages without measurement scripts.
Identify the processing you are controlling
Inventory attribution scripts, cookies, storage and network destinations. Record who determines their purpose and which consent manager choice permits loading. Do not call a cookie necessary solely because it helps measure sales. The Spanish AEPD cookie guidance covers information, consent, exceptions and withdrawal; classification requires reviewing the actual processing.
The CallRail privacy notice explains that its JavaScript can associate visitor activity with calls and collect browsing information. This describes the service rather than establishing that a particular installation respects visitor decisions.
Prepare an effective loading barrier
Where consent is required, link the tag to the corresponding consent manager choice. The normal phone number and link need to work when tracking stays inactive. Hiding an interface and preventing network requests are different facts; verify both.
Confirm with the provider and consent manager how withdrawal affects new loads, existing storage and an active session. Do not invent a CallRail JavaScript function or assume deleting a cookie disconnects every active process. If behaviour is neither documented nor tested, technical acceptance remains pending.
Original acceptance matrix
| Test state | Observation | Closure evidence |
|---|---|---|
| Fresh visit before choosing | Requests and storage before selection | Conditional tracking has not started |
| Rejection | Navigation and telephone remain usable | Choice respected across pages |
| Relevant acceptance | Expected loading and attribution | Controlled tag without duplicate installation |
| Later withdrawal | Agreed procedure and following pages | Verified withdrawal behaviour |
Use a fresh session for each scenario and retain configuration screenshots and traces without customer data. The CallRail manual DNI test explains that substitution uses JavaScript and cookies. Its number substitution test does not replace this matrix's consent checks.
Check more than the displayed number
The displayed telephone can retain the normal number while a script transmits data. It may also change while a duplicate tag remains outside consent manager control. Review network activity, storage and the phone link destination in the same scenario.
Test navigation between pages and a return visit with the choice retained. Include mobile and templates loading tags through different paths. After fixing a tag trigger, repeat rejection and withdrawal; testing acceptance alone favours precisely the journey that permits measurement.
Interpret reports within coverage limits
Fictional example: the telephone log includes calls without an associated web session. Some may come from untracked visitors or previously saved numbers. Do not assign them to the last accepting visitor or reconstruct identity from approximate timing. Preserve an unverified attribution category.
CallRail may fit supported installations and countries; number conditions need confirmation, and this guide does not establish Spanish number availability. If attribution requires consent, request a provider answer on loading and withdrawal before purchase. This protocol produces bounded technical evidence rather than a legal compliance guarantee. Its AEPD reference concerns Spain and does not establish rules for every country.
Sources and limitations
Documentary review: . Content type: Documentation-based guide with original resource.
Sources describe terms and capabilities stated by their owners. Proposed protocols and fictional examples do not establish product tests performed by CallsIQ.
- Spanish AEPD cookie guidancewww.aepd.es
- CallRail privacy noticewww.callrail.com
- CallRail manual DNI testsupport.callrail.com
Check current terms
Consider these options if they solve the problem described. Confirm features, limits and availability in your country.
CallRail for international clients: its phone-number documentation lists availability in the United States, Canada, the United Kingdom and Australia. Spain is not on that list. Consider this option if you manage phone operations in those markets, and confirm numbers, destinations and terms with the provider. Availability checked on 2 October 2026.
CallRailAffiliate linkThe labelled commercial links may earn CallsIQ a commission or referral reward. Our commercial policy.
Official sources, explained calculations and clearly labelled examples. Read about our methodology and use of AI in writing.