Measured live · last 24 h · refreshed every 5 min · all times UTC. The full walkthrough is folded under “How we measure” at the bottom.
1A member actsChannels → MuleSoft (app level: APIs through the Omni Gateway)instant
2It lands as a recordmembership-api → PostgreSQL (system of record)instant
3Two real-time paths forkReal-time Sales Cloud sync (Informatica CAI) + Informatica CDC~2 s · ~20 s
4IDMC makes it trustedIDMC CDI mappings, run by idmc-control: land → raw → staging → curated + DQ~5 min
5Bronze → Silver → GoldGoogle BigQuery medallion (transformed by IDMC CDI)~1–2 min per member · full rebuild on a schedule
6Gold fans outThe golden layer → dashboards, AI, Salesforce, source systems~2-5 min
7Data 360 closes the loopSalesforce Data 360 → lists → win-backstreams ~20 min · lists 12 h
How we measure — full walkthrough
The single journey of one member event, stage by stage — each one hands its result to the next. A member acts, the event is captured, it goes live in seconds on two real-time paths, Informatica IDMC turns it into one trusted record, BigQuery shapes it into Gold, the golden layer fans out to analytics, AI, Salesforce and the source systems, and Salesforce Data 360 closes the loop. The descriptions were verified on 2026-09-28; all times UTC. Every latency shown on this page is measured, not typed in.
1A member actsChannels → MuleSoft (app level: APIs through the Omni Gateway)instant
A sign-up, membership, booking, visit or payment comes from the website, the mobile app or the in-store kiosk. Website and kiosk calls enter through the governed MuleSoft front door; the mobile app calls membership-api directly.
Channels
Member Web (Next.js) · Mobile App (Expo) · In-Store kiosk and POS. Sign-in is OIDC through Keycloak (realm topstadium). Every sign-up form takes an optional home address (street, city, state, ZIP).
External gateway :8060
MuleSoft Flex Gateway (Local Mode) routes and governs the website and kiosk calls: client-id enforcement, tiered rate limits by member tier (bronze 30 · silver 120 · gold 600 per minute), CORS, governance headers.
↓The request reaches membership-api as a governed, authenticated call.
2It lands as a recordmembership-api → PostgreSQL (system of record)instant
membership-api writes the event to Postgres, the one system of record, and a database trigger announces the change.
membership-api :8000
System of engagement: /signup · /memberships · /checkout · /payments · /bookings · /checkin. Only the 5 active locations can be booked (Atlanta, Austin, Dallas, Houston, Orlando). A repeated booking submit returns the same reservation, never a second charge. The tier follows the membership purchase and is cleared on cancel.
Postgres topstadium
System of record: members (with address), memberships, bookings, visits, payments, pos_orders, gl_entries, billing_schedule, dunning, email_log, rule_events, audit_log, venues.
stadium_event_notify
A Postgres trigger fires pg_notify the moment a row lands, already shaped for the real-time path.
↓One committed row in Postgres, and a change notification, now drive two real-time paths in parallel.
3Two real-time paths forkReal-time Sales Cloud sync (Informatica CAI) + Informatica CDC~2 s · ~20 s
The same event immediately takes two live routes: a fast write to Salesforce, and a change-capture stream into BigQuery, so the member is visible everywhere within seconds, before the trusted rebuild runs.
Real-time Sales Cloud sync (Informatica CAI)
idmc-control relays the pg_notify to Informatica CAI, which cleanses the record, makes an ACTIVATE/REVIEW decision and upserts the Salesforce Contact (then Membership / Booking / Visit), keyed on the member id. Fail-open: a sign-up never waits on Salesforce.
Database Ingestion CDC → BigQuery
Postgres logical replication feeds the Database Ingestion task dbmi_stadium_cdc_rt into BigQuery stadium_cdc; 44 live views in analytics_rt read it.
↓The member is live in Salesforce and in the real-time dashboards: provisional values, soon replaced by trusted ones.
4IDMC makes it trustedIDMC CDI mappings, run by idmc-control: land → raw → staging → curated + DQ~5 min
Informatica IDMC lands the data, cleanses it, applies data-quality rules and de-duplicates it into ONE trusted record per member: the “bronze+” record.
Land → raw → staging
The member lane runs after each sign-up: Postgres → BigQuery land → raw, then cleansed into staging. In the same run it upserts the Salesforce Contact with the trusted values and writes the trusted record back to the CRM, payments-and-loyalty and accounting systems.
Trusted record (bronze+)
Rule-based de-duplication in an Informatica CDI task merges duplicates into one trusted record → members_curated (person_key).
Data quality
CDQ rule tasks run inside every lane and write dq_scorecard · dq_results. Only valid records move on.
Address verification
Every 20 s, new customers' home addresses are checked by Informatica Address Verification (VERIFIED, VERIFIED_CORRECTED, NOT_FOUND …) with the standardized address, ZIP+4 and county → contact_enrichment.
Catalog + CLAIRE
CDGC holds the catalog, the business glossary “Retail Simulation — Data Foundation” (33 terms) and lineage (Postgres → IDMC → BigQuery → Salesforce); CLAIRE GPT answers from it.
↓A single trusted, scored record per member is ready to shape into the warehouse.
5Bronze → Silver → GoldGoogle BigQuery medallion (transformed by IDMC CDI)~1–2 min per member · full rebuild on a schedule
In BigQuery the data moves up the medallion: raw Bronze, cleansed Silver, trusted Gold. Informatica CDI does the transforms; BigQuery stores the layers. Gold is the single source of truth for everything downstream.
Bronze → Silver
idmc_land and raw (bronze landing) → staging (cleansed and standardized by IDMC CDI with CDQ rules).
Silver → Gold
analytics_idmc: gold marts built by IDMC CDI: trusted members (bronze+), facts, billing health, member vs walk-in, rule enforcement, data-quality scorecard.
Full rebuild
The full refresh (10 consolidated multi-transformation mappings + landing, Salesforce and reverse-ETL tasks) runs on the CDI speed set by the toggle at the top of this page: Normal saves the IDMC job limit, Demo runs as fast as possible. Its cadence and last run are in “Scheduled refreshes” below.
↓BigQuery Gold now holds the trusted truth, ready to fan out.
6Gold fans outThe golden layer → dashboards, AI, Salesforce, source systems~2-5 min
The trusted Gold layer feeds every consumer: this is the thick golden arrow on the diagram. Analytics, AI, Salesforce and the source systems all draw from the same trusted records.
→ Tableau Cloud
Workbook “Retail Simulation — Data Foundation”: 19 tabs on live BigQuery (CEO, CEO decisions, Live, Members 360, Data trust, Data governance …), with lean “Retail Simulation — EVP” workbooks for fast demo loading, including MuleSoft API traffic streamed to BigQuery, plus Tableau Pulse (4 metrics).
→ AI
An MCP server exposes Gold and Informatica data-quality tools to AI agents; the vectorizer embeds DQ-valid customer records into pgvector every 5 min. Next (planned): MuleSoft Agent Fabric to govern the MCP servers and an Agentforce agent.
→ Sales Cloud (bronze+ wins)
Trusted bronze+ values overwrite the real-time CAI values: the Contact in the member lane after a sign-up, memberships, bookings and visits in the activity lane after the event, and accounts, activities, invoices and the DQ scorecard in the full rebuild. DQ circuit breaker: the push is skipped if DQ-valid trusted members are fewer than 80% of what Salesforce holds.
→ Reverse-ETL to source systems
IDMC upsert tasks write the trusted record back to the CRM · Payments & loyalty · Accounting systems in the member lane after each sign-up and in the full rebuild (non-empty-only contract). CRM data is also loaded daily at 03:50 UTC.
↓Trusted data is now in Salesforce, where the customer-360 work happens.
7Data 360 closes the loopSalesforce Data 360 → lists → win-backstreams ~20 min · lists 12 h
Salesforce Data 360 unifies the trusted records into one customer profile, turns them into insights and customer lists, and drives win-back activity back into Sales Cloud, closing the loop that started with the member's action.
Data streams
The Salesforce CRM connector brings Contact · Account · Membership · Booking · Visit into Data 360 about every 20 minutes.
Identity resolution
Ruleset “Stadium Members” unifies each customer into one Unified Individual; it finds no extra merges because IDMC has already de-duplicated them.
Insights & lists
Calculated insights (visit engagement, booking value, membership) feed the lists “Gold members with no visit in 21+ days”, “Customers without a membership”, “High-value customers at risk”, “Customers created in the last day” and “New customers today (passed quality checks)”. Lists publish every 12 h (07:00 and 19:00 UTC).
Win-back
The lists drive win-back tasks back into Sales Cloud, on the same record the member's first action created. List results are read back into BigQuery for Tableau on the CDI speed schedule (Normal every 6 h, Demo every 15 min).