Overview
When troubleshooting a CallRail field mapping issue — such as a field that appears in CallRail but isn't passing through to the CRM — you can inspect the raw payload that CallRail sends using the Dazos Logger. All integrations, including CallRail, log their payloads there, making it the definitive place to verify which fields are actually being received by the CRM.
⚠️ Note: Do not look for webhook logs inside the CallRail UI — that functionality does not exist there. The correct place to inspect the CallRail payload is the Dazos Logger within iCampaign.
Before You Begin
You must have an Admin or Super Admin role in iCampaign to access the Dazos Logger.
The Dazos Logger menu item must be visible in your iCampaign sidebar. If it is not visible, your account may not have the required role — contact Dazos Support.
Datadog logging must be enabled for your instance. If the logger loads but shows no results, contact Dazos Support and reference ticket ICD-1254-2.
Steps
Open the Dazos Logger
From the iCampaign sidebar, navigate to Dazos Logger. The page opens with summary cards showing total log counts broken down by Info, Warn, and Error status for the selected time range.
Filter Logs to the CallRail Integration
Use the filter bar to narrow results to CallRail-related entries. Set the Service or Module filter to the CallRail integration. Adjust the Date Range to cover the time period when the call in question was received (e.g., Last 24 Hours or a custom range).
Click Filter to Apply
Click the Filter (magnifying-glass) icon to apply your selections. The log list will update to show matching entries. Click Reset (eraser icon) to clear all filters and return to the default view.Locate the Relevant CallRail Log Entry
Find the log entry that corresponds to the call you are investigating. Log rows will show the timestamp, service, module, and status to help you identify the correct entry.Open the Log Detail to Inspect the Payload
Click the icon on the relevant row and select View details. The detail panel will display the raw payload data received from CallRail, including all field names and their values as sent by CallRail at the time of the call.
Verification / Expected Result
After opening the log detail, you should be able to see the full list of fields and values that CallRail sent to the CRM for that call. Compare these field names exactly against the fields you are attempting to map in the CRM integration settings.
✅ Best Practice: Field names in the payload are case-sensitive. If a field name in the payload does not match the mapped field name exactly, the data will not pass through. Use the payload view to confirm the exact field name as CallRail sends it.
Troubleshooting / Common Errors
Dazos Logger is not visible in the sidebar: Your account may not have the Admin or Super Admin role required to access the logger. Contact your administrator or Dazos Support.
Logger loads but shows no results: Datadog logging may not be configured for your instance. Contact Dazos Support and reference ticket ICD-1254-2.
Field appears in CallRail but not in the payload: If a field is visible in the CallRail UI but absent from the payload shown in the Dazos Logger, CallRail is not including that field in the webhook it sends to the CRM. In that case, the field cannot be mapped regardless of CRM settings — review the CallRail configuration for that field on the CallRail side.
Do not look for logs in the CallRail UI: CallRail does not provide a webhook request log view within its UI. The Dazos Logger is the correct and only place to inspect payloads received from CallRail.