SUPPORT.TWILIO.COM END OF LIFE NOTICE: This site, support.twilio.com, is scheduled to go End of Life on February 27, 2024. All Twilio Support content has been migrated to help.twilio.com, where you can continue to find helpful Support articles, API docs, and Twilio blog content, and escalate your issues to our Support team. We encourage you to update your bookmarks and begin using the new site today for all your Twilio Support needs.

Fixing Segment Salesforce Actions Lead RecordTypeId Lookup Field Mapping

Issue

Standard Salesforce lookup fields (such as RecordTypeId or OwnerId) are not being populated on Lead records when setting up mapping using Segment’s Salesforce (Actions) destination, even though the integration reports success and other fields update as expected.

 

Product

Segment Destinations

 

Environment

Segment Console

 

Cause

This issue typically occurs when Salesforce lookup fields (such as RecordTypeId or OwnerId) are not updated, despite being present in the outgoing payload from Segment. 

 

Resolution

Step 1: Confirm Mapping in Segment

  • Ensure the field (e.g., RecordTypeId) is mapped in the Segment destination settings.
  • For upsert operations, check if the field should be included as a Record Matcher. Refer to Segment’s Salesforce Actions documentation.

Step 2: Validate Field Value

  • Confirm the value being sent (e.g., the 15- or 18-character Salesforce ID) matches an active record in Salesforce (e.g., an active Lead Record Type).
  • Avoid adding extra formatting (such as quotes) around the ID.

Step 3: Check Outgoing Payload

  • Use Segment’s Event Delivery or Event tester to inspect the outgoing payload.
  • Verify that the field (e.g., RecordTypeId) is present in the payload sent to Salesforce.

Step 4: Test with Other Fields

  • Try updating other standard and custom fields to confirm the integration is working for non-lookup fields.
  • If only lookup fields fail, this points to a Salesforce-side restriction.

Step 5: Review Salesforce Logs and permissions

  • Check Salesforce’s API logs for the incoming request.
  • Confirm whether Salesforce is receiving the field and if any errors or warnings are logged.
  • Ensure the Salesforce integration user has permission to write to the field.
  • If the field is present in the payload but not updated in Salesforce, consult with your Salesforce admin

 

Additional Information

  • If all troubleshooting steps above confirm that Segment is sending the correct data and permissions are set, but the field still does not update, this is likely a Salesforce-side issue.

Below you will find references to useful documents:

Have more questions? Submit a request
Powered by Zendesk