How the Site Talks to the CRM
The entire BBBC website is a frontend-only React app that fetches live data from a CRM backend via its REST API. There is no server-side code, no database, and no build step in the site itself. Every event, speaker, attendee, sponsor, and partner record is pulled at runtime from the CRM, cached in localStorage with a versioned key, and rendered client-side. Form submissions post tracking events back to the CRM via its external-tracking endpoint. This architecture keeps the site fast, cheap to host, and always in sync with the CRM without any manual export or import.
- Frontend-only React app: no server, no database, no build pipeline
- All event/speaker/attendee/sponsor/partner data fetched live from the CRM REST API
- localStorage cache with a versioned key (bumped when the CRM schema or data changes) so stale data is evicted
- Upcoming events cached for 1 hour; past events cached for 7 days (they rarely change)
- Form submissions post tracking events to the CRM external-tracking endpoint
- 429-aware retries with backoff honour Retry-After so a rate-limited refresh recovers instead of returning empty
- Stale-while-revalidate: a cached list renders instantly while a fresh fetch runs in the background; a failed refresh falls back to the last good cache
Events: custom_objects.events
Events live in the CRM as custom_objects.events records. The events service paginates through the full search endpoint, maps each raw record into a typed GhlEvent (via the event record mapper), and splits the results into upcoming and past slices with independent cache TTLs. Venue data is surfaced through relations to custom_objects.venues records, so even events synced from the event management API (which carry the venue only as a relation) can backtrack to the full venue record and its address. The hero countdown pulls the next bookable upcoming event; if none is bookable (sale ended or no future event), it falls back to the December Christmastravaganza countdown.
- Events fetched via the custom_objects.events search endpoint (paginated)
- Raw records mapped to a typed GhlEvent shape by the event record mapper
- Venue resolved via relations to custom_objects.venues records
- Sponsor fields (name, logo, tagline, quote, charity) extracted from the event record's sponsor fields
- Cover image, photo gallery, recap reel, debrief text, agenda, and charity details all stored on the event record
- event_capacity and total_attendees drive the urgency badge and the attendee count
- Cache version key is bumped manually when the CRM data is updated so visitors see fresh data on next load
Speakers: custom_objects.speakers
Speakers live in the CRM as a dedicated custom_objects.speakers custom object. The event record already carries speaker names (populated by the event management API), and the speakers service enriches those names with rich data from the speakers object: headshot, job title, organisation, bio, LinkedIn, and website. Matching is done by normalised name so the event's free-text speaker list lines up with the speakers object records without any manual linking. The service also cross-references all events to build a 'months spoken' map, so each speaker card shows a badge listing the months they have appeared at.
- Speakers fetched via the custom_objects.speakers custom object
- Rich data: headshot, job title, organisation, bio, LinkedIn, website, role
- Matched to events by normalised name (no manual linking required)
- Cross-referenced across all events to build a 'months spoken' badge
- Speaker profile pages (/speakers/:slug) built from the merged record
- Fallback to event-JSON speaker data if the speakers object record is missing
Attendees: CRM Contact Tags + Custom Fields
The 'Who's coming' attendee list surfaces ticket buyers for a specific event so attendees can scope out who they will meet. The live ticket-buyer roster is driven by a per-event tag applied by the CRM's post-booking workflow (e.g. 'attending-oct-2026'). The attendee service uses the CRM's server-side tag filter to return only contacts carrying that tag in one paginated request, with no full-scan. Profile enrichment data (looking for, ideal referral, LinkedIn, headshot, logo) lives on the contact object as custom fields, written by the AttendeeProfileForm which fires post-booking via a CRM email workflow. There is no separate staff approval step: the tag itself is the trust signal, and profile fields are optional so a tagged buyer appears even before they fill in their networking details.
- Attendee roster driven by a per-event CRM tag (e.g. 'attending-oct-2026')
- Server-side tag filter returns only tagged contacts in one paginated request
- Profile data (looking for, ideal referral, LinkedIn, headshot, logo) on the contact object as custom fields
- AttendeeProfileForm pre-fills from existing contact fields so returning attendees review, not retype
- Attendee list gated behind SMS verification (AttendeeAuthGate)
- In-flight dedup: the list fetch and the live count fetch share one search per event tag to avoid racing each other into a 429
- Stale-while-revalidate: cached list renders instantly while a fresh fetch runs in the background
Sponsors & Partners: custom_objects.partner
Sponsors and partners live in the CRM as a custom_objects.partner custom object. The partner service fetches approved partner records (partner_status='approved') for public display, with a 1-hour localStorage cache. The partner application form creates records with partner_status='pending'; BBBC staff approve manually in the CRM, after which they appear on the site. Per-event sponsor content (name, logo, tagline, quote, nominated charity, one-pager) is stored directly on the event record and extracted by the sponsor fields module, so the featured sponsor spotlight and sponsor event pages read real per-month content. The Digital Gurus sponsor has a fallback logo and exclusive offer built into the sponsor fields module.
- Partners fetched via custom_objects.partner (approved records only)
- 1-hour localStorage cache so the page stays fast
- Partner application form creates pending records; staff approve in the CRM
- Per-event sponsor content stored on the event record and extracted by the sponsor fields module
- Sponsor logo URLs normalised and Google Drive file links converted to direct image endpoints
- Digital Gurus sponsor has a fallback logo and exclusive BBBC offer
Form Submissions: External Tracking
Every form on the site (event reminders, contact us, speaker onboarding, sponsor onboarding, partner application, attendee profile, AOB video submission, add your logo) posts a tracking event to the CRM external-tracking endpoint via the tracking module. The endpoint and location ID are wired from the connected integration. Tracking payloads are built with the form's field values, the current page URL, and session metadata, so each submission appears in the CRM as a tracked event on the contact's timeline. This is how the CRM knows a visitor signed up for reminders, applied to speak, or submitted their sponsor logo, without any server-side code in the site.
- All forms post tracking events to the CRM external-tracking endpoint
- Endpoint and location ID wired from the connected integration
- Tracking payloads include form field values, page URL, and session metadata
- Each submission appears in the CRM as a tracked event on the contact timeline
- No server-side code: everything is client-side fetch to the CRM API