The AM noticed the landing page (/locations/orlando-lp/) was showing an unexpected out-of-state number. The client is high-temperature and had flagged this as an ongoing issue since March. With 10+ tracking numbers configured across multiple PPC campaigns and channels, it wasn’t immediately clear which rule was causing the wrong number to show on that specific page.
Investigated the CTFX configuration and identified the root cause: the landing page had (800) 822-1190 hardcoded in its HTML, which happened to match the target number configured in the Website Calls pool. When CTFX detected that number on the page, it automatically swapped it with the pool’s tracking number — which is expected behavior, but undesired on a PPC landing page that should show a specific campaign number. The fix was to hardcode the correct PPC number (407-890-8130) directly in the landing page HTML so CTFX wouldn’t recognize it as a swappable target.
Resolved a months-long tracking issue on a high-temperature client by identifying an unintended interaction between a hardcoded page number and an active CTFX pool — something that’s easy to miss in a complex multi-number setup.
https://app.webfx.com/todos/269122300