architect-ecommerce

What problem does it solve?

Architects and engineering teams struggle to reliably connect commerce platforms, search/recommendation engines, and mobile app platforms to Braze without creating duplicate events, inconsistent product identities, or broken attribution. This Skill provides clear patterns for event ownership, product catalog synchronization, and cross-system mapping so teams can design predictable, auditable integrations.

Core Features & Use Cases

• Integration patterns: Guidance on canonical event sources per channel (Shopify, GTM/pixel, mobile SDKs) and how to avoid duplicate ingestion.
• Data model & catalog design: Recommendations for a shared product ID namespace, attribute fidelity, and catalog sync cadence to support personalization and recommendations.
• Partner-specific considerations: Practical notes for Algolia, Constructor, Stylitics, Tapcart, and Poq on how their events and APIs typically map into Braze.
• Attribution & event mapping: Strategies to carry placement, query_id, and campaign identifiers through search and recommendation clicks to enable downstream conversion attribution.

Quick Start

Create an integration plan for a Shopify storefront using Algolia for search and Tapcart for mobile that specifies canonical event owners, a single product ID namespace, event property normalization for Braze, and a catalog sync schedule.