Session Objective

Answer why some CallRail rows say Conversion_Status__c = Not Signed while their linked Litify Intake status is Converted.

Work Completed

• Queried live Salesforce FieldDefinition for CallRail_Call_Log__c.Conversion_Status__c.
• Queried live Salesforce aggregates by call-log conversion status, Case_Signed__c, and linked Intake status for GCLID call logs.
• Queried the converted-intake GCLID call-log rows directly.
• Searched local scripts/docs for Conversion_Status__c and Case_Signed__c usage.

Findings

• CallRail_Call_Log__c.Conversion_Status__c is Text(255), not a picklist and not the same as litify_pm__Intake__c.litify_pm__Status__c.
• Live aggregate for GCLID call logs linked to converted intakes:
  • Conversion_Status__c = Not Signed, Case_Signed__c = false, Intake status Converted: 9 rows.
  • Conversion_Status__c = N/A, Case_Signed__c = false, Intake status Converted: 1 row.
  • Conversion_Status__c = Signed, Case_Signed__c = false, Intake status Converted: 1 row.
• Multiple CallRail call logs can point to the same converted Intake and carry different call-level statuses. Example: one intake had an earlier Not Signed call and a later Signed call, while the Intake itself converted later that day.
• Some call logs are linked to intakes that converted years before the 2026 CallRail GCLID call. Those were already excluded from upload candidates.

Conclusion

For Google Ads offline converted-intake uploads, the authoritative fields are the linked Intake/Matter fields: litify_pm__Status__c, litify_pm__IsConverted__c, litify_pm__Converted_Date__c, and litify_pm__Matter__c. CallRail_Call_Log__c.Conversion_Status__c should be treated as call-level context only and should not disqualify a row when the linked Intake has actually converted after the call.

Suggested Next Steps

If this becomes recurring reporting, a future agent should add an audit note or derived field to separate CallRail call status from Litify final intake outcome, because the label Conversion Status is easy to misread in marketing reports.

Pickup Prompt

When reviewing CallRail offline conversion rows, do not use CallRail_Call_Log__c.Conversion_Status__c as the final case outcome. Use the linked Intake/Matter conversion fields for final outcome and keep call-log status as supporting call-level evidence only.