Digging deeper on what causes CTFX numbers not to swap

Posted by: JP Betis Date Posted: September 17, 2024
Back to Case Studies

Issue

Recently, during the audit I made for Pod Pack, I noticed something odd on their CallTracking setup. When I tested it for swapping I was shocked to see that all were not swapping at all. When I look back last audit I made those numbers are still swapping perfectly. So I did the following troubleshooting steps to verify what causes the problem.

  1. Check if call tracking script is available on client’s website.
    • I did confirmed that it was on the website and it’s following the correct CTFX script format as seen on their tracking code https://app.webfx.com/marketingcloudfx/settings/tracking-code
    • https://webpagefx.mangoapps.com/msc/MTkzOTY3N18xMzk2MDQ1Mw
  2. Verified and confirmed that it uses all possible number combinations for swapping
  3. All Tracking rules for each numbers are correct
  4. Call on the function name on Developer’s console
    • Typing n the function “Calltrack” on developer’s console will provide you all the information about the calltracking functions on your client’s website. When I tried to check if the tracking rules correspond correctly on the data that should be displayed on client’s website, I was able to confirm that it should be correct as the Source and Medium, Number to replace and default forward to based on the information provided on the developer’s console is the same as what was setup on each of the numbers
      • https://webpagefx.mangoapps.com/msc/MTkzOTY4NV8xMzk2MDQ2NQ
  5. Since the LMFX forms and CTFX calltracking is working, I already assumed that MCFX pixel and CTFX script is not being blocked by any ad blocker or by the website server itself

Now, we’ve basically exhausted all possible cause of any CTFX issue, what’s next then?

I checked again the client’s website and noticed that everytime I reload the website an error keeps propagating (typeError Note.href) https://webpagefx.mangoapps.com/msc/MTkzMzA3Ml8xMzkzNzYyNw. When I clicked the error, it redirects me to CTFX script folder where the error points to node.href https://webpagefx.mangoapps.com/msc/MTkzMzExNl8xMzkzNzczMQ. It seems that there is a mis configuration on object values on node.href.

Solution

Since I’m not capable to troubleshoot it further and made proper changes, I then submitted R&D task request and they were able to work on it within the day. It was confirmed that the culprit was the object value on node.href having it misaligned to what the intended value should be.

Achievement

Snippet/Screenshot/Link

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