Overview
This guide explains why CTM custom fields such as GCLID and UTM parameters don't appear in Dazos CRM just because the CTM webhooks are active, and what to prepare before requesting the mapping.
Prerequisites
Before you begin, make sure you have:
An active CTM integration with Dazos CRM (webhooks already configured).
A list of the specific CTM custom fields you want mapped to Dazos (e.g., GCLID, UTM fields, Facebook Click ID, GBRAID, WBRAID, etc.).
Sample call examples from CTM where those custom fields are populated with data.
For any picklist-type fields: confirmation that the same values exist in both CTM and the Dazos CRM picklist, spelled and formatted exactly the same way.
Steps
Understand that custom field mapping is a separate step from webhook setup. When Dazos configures your CTM webhooks, custom field mapping is not included automatically. Webhooks enable the connection between CTM and Dazos CRM, but each individual custom field you want to pass through — such as GCLID, utm_source, utm_medium, utm_campaign, GBRAID, WBRAID, Facebook Click ID, Facebook Lead ID, or any other custom field — must be explicitly requested and configured separately.
Compile the list of CTM custom fields you want mapped. Identify every CTM field whose data you need to appear in Dazos CRM. Common examples include:
GCLID
utm_source, utm_medium, utm_campaign, utm_term, utm_content
GBRAID
WBRAID
Facebook Click ID
Facebook Lead ID
Landing URL
Any other custom or marketing tracking fields in your CTM account
Gather sample call examples from CTM where those fields are populated. The Dazos support team needs to review backend logs to identify the exact key names used in the CTM payload for each field. Providing call activity IDs or examples where the fields contain real data makes this process faster and more accurate.
Submit a request to Dazos Support. Contact the Dazos support team and provide:
The full list of CTM custom fields you want mapped.
Sample CTM call activity IDs or examples where those fields are populated.
The corresponding Dazos CRM fields you want them mapped to (if known).
The support team will review the backend logs and configure the mapping on your behalf.
For picklist-type fields, verify that values match exactly between CTM and Dazos CRM. If any of the fields you are mapping use a picklist (dropdown) format, the values in CTM must exist in the corresponding Dazos CRM picklist and must match exactly — including spelling, capitalisation, and spacing. If a value exists in CTM but not in the CRM picklist, or if the values do not match character-for-character, the data will not map correctly. Coordinate with your Dazos contact to align these values before testing.
Result
After completing these steps, the requested CTM custom fields will be mapped to their corresponding fields in Dazos CRM. Data from those fields will begin populating on lead records for inbound calls where the fields are populated in CTM at the time the call ends. Fields that were not explicitly requested and configured will continue to not appear in Dazos CRM, regardless of whether webhooks are active.
⚠️ Important: Custom field mapping only affects new calls going forward. Previously received calls will not be retroactively updated with field data that was not mapped at the time of the call.
If you are unsure whether your custom fields have been mapped, or if data is still not appearing after mapping has been confirmed, contact Dazos Support and provide a specific call activity example from CTM where the field is populated, so the team can trace the data through backend logs.