How identification works in Pipeback

In Pipeback, each contact has:

• Email: required and unique (our primary key)

• Pipeback ID: automatically generated by the system

• User ID: optional field for your own system's identifier

What is user_id for?

The user_id is a field where you can store the unique identifier from your system (e.g., UUID, database ID, etc.).

Benefits:

Simplified integration

• Easily connect Pipeback contacts with records in your database

• No need to lookup by email every time

Efficient synchronization

• Update data in both systems using the same identifier

• Avoid sync errors

Better tracking

• Correlate events and actions between Pipeback and your system

• Easier debugging and analytics

How to use it

When creating or updating a contact, include the user_id:

{
  "email": "customer@example.com",  // required
  "user_id": "uuid-12345-from-your-system",
  "name": "John Smith"
}

Practical example

If in your system the customer has ID usr_8f3a2b, you send:

• Email: john.doe@company.com (required)

• User ID: usr_8f3a2b (their ID in YOUR system)

This way, whenever you need to sync data, you can use the user_id to quickly identify the user across both platforms.

💡 Summary: Email identifies the user in Pipeback, user_id identifies the same user in YOUR system.