Google Sheets: Primary Identifier Mapping Required
Starting September 25, 2026, Google Sheets destination syncs require a primary identifier mapping to track row changes accurately. New syncs and edits to existing syncs must specify a unique source column as the key, either via the UI or API/Terraform with is_primary_identifier: true.
Changelog
Starting September 25, 2026, Google Sheets destination syncs require a primary identifier mapping: a unique key from your source data. We use it to track which rows are new or changed, so monthly active records are measured accurately. Syncs you don't touch keep running as they do today; this only applies to new syncs and edits to existing ones.
Pick a source column to use as the key in the UI when creating or editing a sync.
Action required if you use the API or Terraform
Add a mapping with is_primary_identifier: true pointing to a source column that uniquely identifies each row. Starting September 25, calls that create or update a Google Sheets sync without this mapping will fail.
Want this turned on sooner? Contact Support and we can enable it early.
Source: original entry ↗
More from Census
Follow Census to get its new changes in your feed and email digest.
Braze: Email and User Alias as Identifiers
The Braze connector now supports email and user_alias as user identifiers for Event and PurchaseEvent syncs, alongside the existing external_id option, providing more flexibility in data synchronization.
LinkedIn Conversions: lead as an Optional Field
LinkedIn Conversions now supports an optional lead field to map Lead Gen Form Response IDs and attribute conversion events to specific lead forms.
API V2 Beta Endpoints Now Available
Census introduces the first V2 API endpoints with a new Sources API that supports region and storage backend selection, Group ID management for access controls, and Personal Access Token authentication. Workspaces have been removed from the API and Workspace API Keys are no longer supported.