architect-user-data-api

What problem does it solve?

Provides high-level guidance for designing and operating Braze user identity and ingestion systems so teams can reliably create, merge, migrate, and delete user profiles without breaking targeting or data integrity.

Core Features & Use Cases

• Identity resolution strategy: When to use external_id, user_alias, email, phone, or braze_id and how that choice affects targeting and persistence.
• Migration and safety patterns: Two-phase external_id rename → verify → remove workflows, batch sizing, and rollback guardrails.
• Ingestion architecture: Tradeoffs between /users/track (async) and /users/track/sync (ordering guarantees), merge vs identify semantics, and deletion/audit best practices.
• Use case: Plan a migration from legacy IDs to a hashed customer ID while preserving analytics, minimizing MAU disruption, and ensuring safe removal of deprecated IDs.

Quick Start

Ask the skill to evaluate your external_id migration plan and provide a step-by-step rename, verification, and removal checklist with required permissions and batch-size recommendations.