Sam asked for a full diagnostic on why CallRail's dynamic number insertion (DNI) had stopped working on aguiarinjurylawyers.com. The swap hadn't fired in 5+ days, meaning every website visitor was seeing the static (502) 888-8888 number instead of a tracked pool number. That meant zero visitor-level call attribution from the site during that window. Sam also wanted the web pool confirmed as the primary tracking method, a full audit of all active CallRail numbers with consolidation recommendations, and a check on two WPCode snippets (CallRail and Intaker) for correctness and performance.
The CallRail swap.js script was not loading on the website at all. Zero CallRail scripts were present among 94 scripts on the page. The cause: WPCode snippet ID 11078 ("CallRail Tracking") was set to Inactive. This snippet contains the swap.js loader:
<script type="text/javascript" src="//cdn.callrail.com/companies/751325874/6f798afe64be14481550/12/swap.js"></script>
The fix was simple: toggled the snippet from Inactive to Active and clicked Update. The swap started working immediately. The Louisville number changed from the static (502) 888-8888 to pool number (502) 842-5049 on page load, confirming DNI was restored.
After reactivating the snippet, investigation showed the swap.js was loading as a render-blocking script in the <head> because the WPCode snippet location was set to "Site Wide Header." This impacts LCP and page speed.
Changed the WPCode snippet location from "Site Wide Header" to "Site Wide Footer." Verified that the swap still works correctly, all 4 CallRail scripts are now non-blocking, and there is no visual flash or delay in number swap.
Documented all 50 active numbers across the CallRail account (492642869, company 751325874). Numbers were categorized into: