Competing Script Preventing CallTrackerFX from Working

Posted by: Julie Medrano Date Posted: April 30, 2026
Back to Case Studies

Issue

CallTrackerFX had already been configured but couldn’t be enabled because a WhatConverts script was still running on the site. Searching the page source for “whatconverts” returned nothing, making it unclear where the script was or how it was being loaded.

Solution

Searching the page source for “whatconverts” returned nothing, so we did some research first to find out how WhatConverts loads its script. Found that they use s.ksrndkehqnwntyxlhgto.com as their script domain — not their brand name. With that, we checked the Network tab and confirmed the script was still actively firing on the site. The next challenge was finding where it was added in WordPress so it could be removed. It wasn’t listed anywhere as a recognizable WhatConverts entry — tracing the initiator led to a scripts.iconnode.com script tag in WPCode > Global Header, where the WhatConverts script was embedded. Commented it out rather than deleting it in case a rollback was needed.

Achievement

Located and removed a competing script that wasn’t findable through conventional source inspection — by using the Network tab to see what was actually loading and tracing it back to its origin in WPCode.

Snippet/Screenshot/Link

https://app.webfx.com/todos/269060080