Mapped records
Record grain: customRecord
Date basis: As of latest refresh
Rules: One contributing record per typed ID
Custom reporting · Google Sheets sample
GoHighLevel Custom Records report template
Explore a mapped Jobs example with status and customer-association coverage. The sample shows how a custom-schema report should make its required mapping explicit.
Custom Records
Invented sample · Fixed as of October 13, 2026 · USD · America/Chicago
Change filters to explore the sample locally. No account connection.
Mapped records3As of latest refresh
Completed records1As of latest refresh
Records with customer association2As of latest refresh
Records without customer association1As of latest refresh
Records by mapped status
View chart data
| Group | Value |
|---|---|
| Scheduled | 2 |
| Completed | 1 |
Customer association coverage
View chart data
| Group | Value |
|---|---|
| Matched | 2 |
| Unmatched | 1 |
| Record | Schema | Status | Customer associations |
|---|---|---|---|
| Install 1001 | jobs | Scheduled | 1 |
| Install 1002 | jobs | Completed | 1 |
| Install 1003 | jobs | Scheduled | 0 |
What the metrics mean
Completed records
Record grain: customRecord
Date basis: As of latest refresh
Rules: One contributing record per typed ID
Records with customer association
Record grain: customRecord
Date basis: As of latest refresh
Rules: One contributing record per typed ID
Records without customer association
Record grain: customRecord
Date basis: As of latest refresh
Rules: One contributing record per typed ID
Required data and boundaries
- Selected custom-object schema
- Verified customer associations
- Contacts
- Validated schema mapping
The invented Jobs schema is not universal custom-object support. Production needs a selected schema, accepted source fields, and verified customer associations.
Synthetic Jobs schema: a validated status field and job-customer association. Deduplicate records before counting; multiple relationship edges never multiply a record. Production requires schema version, direction and cardinality acceptance.
Early access · These public previews use invented records. Join early access to discuss connecting your own GoHighLevel account.
From this sample to a connected report
Choose the template
Use the report whose definitions match the decision you need to make.
Check required inputs
Confirm source access, relevant mappings, history, and any configured goals.
Create the worksheet
The early-access design reuses compatible imports and creates a report worksheet.
Choose freshness
Select source refreshes deliberately. New executions transferring records add usage.
Related report samples
Customer accounts
Business Accounts
Business-linked contacts and their current opportunities.
Explore sample →Bring your own reporting question.
Make this your reporting workflow.
Explore the samples now. Join the existing waitlist to request connected early access, or discuss a predictable subscription for larger workloads.