Braze to Pigment integration — real-time, two-way sync

Yes. Stacksync provides a managed, real-time two-way integration between Braze and Pigment: authenticate both systems, choose the objects to sync (such as Braze's Content Blocks and Users), map fields visually, and changes propagate both ways in milliseconds — no code required.

On the Pigment side: Applications, Metrics, Dimension lists, Tables, plus custom fields where Pigment exposes them. On the Braze side: Content Blocks, Users, Custom Attributes, Custom Events. Stacksync auto-detects both schemas and converts types between the two systems.

Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.

Common patterns for Braze and Pigment: Where Braze tracks people or companies: one identity; Where Braze handles customer conversations: billing context in view; Where Braze collects payments or triggers charges: events land in Pigment. A customer's details updated in either system update the other, so finance and the rest of the business stop maintaining two versions of the same customer.

Braze: REST API. Authentication: REST API keys scoped to specific endpoints, issued per workspace. Pigment: REST-based import and export API. Authentication: API keys, issued separately for import and export. Stacksync manages authentication, retries, and rate limits on both sides.

Pigment: Scenario versioning (budget versus forecast versus actuals) is native to the model, so exports need a scenario context to be meaningful. Braze: The users/track endpoint accepts attributes, custom events, and purchases for many users in a single batched request, which is the standard write path for syncs. Stacksync's field mapping accounts for these differences between Braze and Pigment without custom code.