Objective
This article explains how to resolve an issue where a newly added Salesforce collection or custom object is not showing up or appearing as an option in your Segment data warehouse destination (such as BigQuery) selective sync settings. If you cannot see your new Salesforce collection in your warehouse sync configuration after enabling it at the source, following this procedure will guide you through forcing a full sync to make the object visible.
Product
Twilio Segment
Environment
Segment Console
User Account Permission/Role(s) Required
Workspace Admin or Source/Destination Edit access permissions.
Procedure
Log in to your Segment Console.
Navigate to your Workspace, select the Sources tab, and click on your Salesforce Source.
Open the Schema or Selective Sync settings page for the source.
Locate the newly added custom collection from your collections list.
Expand the collection to view its properties and find the field named SystemModstamp.
Uncheck or switch the toggle to Disabled for the SystemModstamp field.
Save your changes.
Wait for the next scheduled source sync to complete (this typically occurs every 1 to 3 hours depending on your current billing plan). Disabling this field forces Segment to run a full snapshot object sync instead of an incremental delta.
Verify that the collection now appears and is available for configuration in your Destination Warehouse (e.g., BigQuery) selective sync settings.
Once the collection successfully appears and begins syncing to your warehouse, return to the Salesforce source settings and re-enable the SystemModstamp field to ensure future runs remain incremental and save Salesforce API usage.
Additional Information
Salesforce uses the
SystemModstampfield as an internal checkpoint mechanism for delta replications. Turning it off forces a full table scan that clears the checkpoint cache and populates the missing schema information downstream.For more information on configuration options, please refer to the official Twilio Segment Salesforce Source Documentation.