From your first connection
to your next sync.

Before you start

Have access to authorize the DataCharted app for your GoHighLevel agency and a Google Cloud project where you can configure BigQuery. The hosted product writes to your own project and reads supported CRM data without modifying records in GoHighLevel.

Review supported datasets and limitations and pricing. If you need an evaluation or help setting up a warehouse, contact us to agree the scope.

Set up your account

1. Create your account

   Open Create account, enter your agency name, email, and a password of at least eight characters. You’ll arrive at the dashboard after signup.

2. Connect GoHighLevel

   Choose Connect GoHighLevel and complete the authorization flow. Return to Locations to see the available sub-accounts. If a dataset needs permissions that were not previously granted, use the reconnect prompt.

3. Connect BigQuery

   Under Destination, provide a service-account key or choose Google authorization when that option is enabled. Select your project, dataset, and region. DataCharted verifies access during setup; missing stream tables are created from the extractor schemas when the first sync runs.

4. Select locations and streams

   Enable the locations to include, then open Streams. Choose the datasets relevant to your reporting. The catalogue explains which streams support selectable modes and which use fixed full refresh.

5. Run and verify

   Open Sync history and trigger a manual sync. Review status, row counts, errors, and sample output in BigQuery before relying on the tables for reporting.

BigQuery access

The connected identity needs permissions to run jobs and create or write the relevant BigQuery resources. BigQuery Job User and appropriately scoped BigQuery Data Editor access are typical starting points; creating a new dataset may require additional project-level permissions. Use the access your project administrator approves.

Your BigQuery dataset region should match your intended reporting setup. Google Cloud bills your project separately; read the cost guide before choosing a frequent refresh schedule.

Understand sync modes

Incremental streams append new records using a creation-date watermark. Existing contact edits are not captured by the contact incremental mode; choose a full refresh when those records need reloading.

Full refresh reloads the supported dataset scope. Contacts, inbound call records, and form and survey submissions can use either mode. Opportunities and the reference datasets always refresh in full. Full refresh does not create a history of every intermediate change.

Schedules and manual runs

Create schedules with a cron expression. Check the timezone displayed by the scheduler before saving. You can also start a manual run for all enabled locations, one location, or one stream. Avoid schedules that run more often than a typical job can finish.

Sync history and notifications

Each run records its status, loaded rows, and errors. Open a run for stream-level detail and logs. A partial run means some work succeeded while some needs attention; inspect the failures before using the output for complete agency reporting.

Under Notifications, select the outcomes that trigger an email and specify recipients. An optional webhook can send results to your own tooling. Notifications report completed run outcomes, not a real-time CRM event feed.

Pause or disconnect

Disable locations or streams to stop including them in future runs. Review active schedules when pausing an account. Disconnect the BigQuery destination to remove its connection from the app, and revoke provider authorization when appropriate. For account deletion or commercial cancellation, contact support.