CallTrackingMetrics Migration & CRM Integration Journey

Posted by: Bri Guarnieri Date Posted: July 31, 2025
Back to Case Studies

Issue

We had a number of different issues throughout our integration process & even getting to the point of integration!

Issues Overcome/Conditions Pre-Build:

  • Needed call menu functionality in CallTrackerFX to replicate call routing in CallTrackingMetrics.
  • We needed to be able to send calls and forms as real time as possible.

Issues During the Build:

  • Continued troubleshooting instances where forms would not pass due to special characters.
  • Troubleshooting because forms on landing pages were not captured properly.
  • We added the Fallback Plugin, which landed hundreds of robo/spam submissions into LeadManagerFX…and their CRM.
  • Forms and calls not passing to their CRM in a timely manner (taking hours in some cases)
  • Fields not populating correctly or at all, despite setting logic to do so.
  • CallTrackingMetrics were hardcoded on some pages on the site, which meant CallTrackerFX wasn’t swapping!

Solution

As noted above, we encountered a number of errors and issues throughout the integration process (huge shoutout to Rafael for his continued effort and time to resolve these as we worked through the integration). To resolve these issues, we took the following actions to keep the process moving in a positive direction, despite it taking about 7 months to complete:

Key Area 1: Communication with the Client

I sent weekly updates detailing the work that had been completed that week & what was up next and/or still in progress. This allowed a clear outline for the client that we passed to his internal team. We kept him informed, so he could look good to superiors, who only knew the errors that were happening and not the steps in between. We also had a few quick touch base meetings ahead of me going out of the office, or when major adjustments to the integration needed to be made. This helped 1) build my relationship & trust with the client (this was a transfer account for me) and 2) establish unified next steps, where all parties could be a part of the process.

Key Area 2: Client Communication with Me – A big part of the project was also the willingness of the client to send me errors as soon as they came up. The client was diligent about forwarding us forms when they didn’t make it & when they received calls from CallTrackingMetrics numbers. Their effort went a long way in being able to quickly identify errors in a complex integration and resolve in a timely fashion.

Key Area 3: Clear Guidelines for the Dev Team – Ultimately, there was a lot of back and forth between Rafael and I. I had to clearly outline issue 1/2/3 in messages with examples, samples, and references to streamline the process as much as possible.

What was the result? 

We are now at a point where we have intermitent errors, but overall, we’ve successfully transitioned them into CallTrackerFX, which cut costs for their team, improved their call tracking setup (more channels tracked), and gives us more data and power in RevenueCloudFX. It also instilled trust with the point of contact that we would take action quickly, hear out concerns, and maintain a solid relationship moving forward.

Achievement

Migrated the client away from CallTrackingMetrics & configured CallTrackerFX! We also built out an integration to replicate their CallTrackingMetrics functionality to send forms and calls in real time with unique routing.

Snippet/Screenshot/Link