Data Sync

How data would flow from GoHighLevel, Meta Ads and Google Ads into the dashboard.

DEMO MODE

GoHighLevel

Connected - Demo

CRM · leads, appointments, sales

Meta Ads

Connected - Demo

Ad spend and campaigns

Google Ads

Connected - Demo

Ad spend and campaigns

Data Sync

Simulation only. No external APIs are called.

Last Sync

September 25, 2026 06:07 AM

Records Processed

12,842

New Leads

126

New Appointments

42

New Sales

8

  1. 1Step 1: Connecting...
  2. 2Step 2: Fetching data...
  3. 3Step 3: Normalizing records...
  4. 4Step 4: Calculating metrics...
  5. 5Step 5: Updating dashboard...

Press “Run Demo Sync” to simulate a full pipeline run.

Sync Log

Most recent runs first.

Sync log
DateSourceClientRecordsStatus
Sep 25 · 6:07 AMGoHighLevelJamie Med Spa1,238Success
Sep 25 · 6:06 AMMeta AdsJamie Med Spa42Success
Sep 25 · 6:06 AMGoogle AdsJamie Med Spa17Success
Sep 25 · 6:05 AMGoHighLevelClient B604Success
Sep 25 · 6:05 AMMeta AdsClient B28Success
Sep 25 · 6:04 AMGoogle AdsClient B12Warning
Sep 25 · 6:04 AMGoHighLevelClient C351Success
Sep 25 · 6:03 AMMeta AdsClient C19Success
Sep 24 · 6:07 AMGoHighLevelJamie Med Spa1,196Success
Sep 24 · 6:06 AMMeta AdsJamie Med Spa40Success
Sep 24 · 6:06 AMGoogle AdsJamie Med Spa16Success
Sep 24 · 6:05 AMGoogle AdsClient C9Success

Production Architecture

How the demo's mock data layer maps to the real system.

Meta Ads

Marketing API · spend, campaigns

Google Ads

Ads API · spend, campaigns

GoHighLevel

Contacts, appointments, opportunities

  1. Data Ingestion

    Scheduled sync + webhooks, retries, raw landing tables

  2. Normalization

    Unified client / treatment / campaign / date keys

  3. Attribution

    Match lead → appointment → sale → campaign

  4. PostgreSQL

    Daily performance + entity tables (Supabase)

  5. Dashboard

    This application, reading the repository layer

Demo currently uses local synthetic data. Production architecture would replace the mock data layer with API integrations and a central database.