This article explains why this happens and what you can do to prevent it.
Why This Happens
The CTM integration is bidirectional, meaning it both receives data from CTM and sends updates back to your Dazos CRM. When a follow-up interaction occurs — such as an outbound callback made to a lead — CTM pushes a new data payload to the CRM. If the Lead Source and Campaign Source fields are mapped in your CTM integration settings, this new payload will overwrite the original tracking values that were set when the lead first came in.
In practice, this means a lead that originally came in through a Google Ads campaign will appear to have been sourced from the most recent CTM activity (e.g., an outbound callback) by the time it is converted to an opportunity — even though no one on your team made that change manually.
⚠️ Note: This behavior affects all leads imported from CTM, not just those that were manually created. Any subsequent CTM activity on a lead record can trigger an overwrite if the source fields remain mapped.
Solution 1: Remove the Lead Source and Campaign Source Mappings in CTM Settings
The fastest way to stop the overwriting is to remove the field mappings for Lead Source and Campaign Source inside your CTM integration settings. This prevents CTM from automatically updating these fields whenever a new activity (such as an outbound callback) occurs.
Log in to your Dazos CRM instance.
Navigate to Settings → CRM Settings → Integrations → VOIP Settings.
Locate the field mapping section and find the mappings for Lead Source and Campaign Source.
Remove or disable the mapping for both Lead Source and Campaign Source.
Click Save to apply the changes.
✅ Expected Result: After unmapping these fields, CTM will continue to log call activities and create new leads normally, but it will no longer overwrite the Lead Source or Campaign Source on existing records when subsequent interactions occur.
Solution 2: Preserve Original Attribution Using Custom Fields and Workflows
If you need a more robust, long-term solution that permanently locks your original tracking data — even if the primary Lead Source and Campaign Source fields are still being used — you can set up custom fields combined with Dazos automation workflows.
This approach captures and stores the initial tracking information the first time a call lands, then locks it so subsequent CTM activities cannot overwrite it.
Create custom fields such as Original GCLID and CTM Activity ID in your Dazos CRM.
Set up a Dazos workflow that copies the Lead Source and Campaign Source values into these custom fields the first time a lead record is created.
The custom fields will hold the original attribution data permanently, regardless of any future CTM updates to the primary fields.
You can carry these custom tracking values across Leads, Intake Opportunities, and Accounts to eliminate data loss during conversions.
💡 Tip: This approach is especially useful if you need to report on both the original digital source and the most recent CTM activity separately — giving you full attribution visibility across the lead lifecycle.
Tips & Notes
⚠️ This issue applies across all accounts using the CTM bidirectional integration, not just individual instances. If you manage multiple client accounts, the fix should be applied to each account's CTM integration settings individually.
💡 If you are unsure which fields are being overwritten, compare the lead's original CTM source with the CRM source shown at the time of conversion. If they differ, the bidirectional integration is likely the cause.
✅ Best Practice: After applying either solution, create a test lead and simulate a follow-up outbound callback to confirm that the original Lead Source and Campaign Source values remain unchanged.