Prompt
What should I use for customer identity if I need CRM integration?
Latest observation
Nov 13, 2026
OpenAI APIWeb search: off
If you need CRM integration, the best choice for customer identity is usually a stable, unique customer ID from your system, and then map CRM records to it.
Recommended approach
Use:
- Primary identity: a first-party customer ID you generate and control
- Supporting identities: email, phone number, CRM contact ID, and other known identifiers
Why this is best
- CRM IDs can change or differ across systems
- Email/phone can be shared or updated
- A stable internal customer ID lets you reliably link:
- website activity
- app events
- support tickets
- purchase history
- CRM contacts/accounts
Best practice
Store an identity map like:
customer_id→ internal canonical IDemailphonecrm_contact_idcrm_account_id
If you’re integrating with a CRM directly
Use the CRM’s:
- Contact ID for person-level tracking
- Account/Company ID for B2B tracking
But still keep your own canonical customer ID as the source of truth.
Simple rule
- B2C: use a person/customer ID
- B2B: use an account ID + contact ID
- Across all systems: keep a canonical internal ID and sync CRM IDs to it
If you want, I can suggest the best identity strategy for your specific CRM (Salesforce, HubSpot, Dynamics, etc.).