Close



Data Sources



General

Data Sources | General

Connections

Data Sources | Connections

Fields & Formulas

Data Sources | Fields & Formulas

Reports



Creating & Sharing

Reports | Creating & Sharing

Report Editing

Reports | Editing

Report Config

Reports | Report Config

Chart Cards

Reports | Chart Cards

Content Cards

Reports | Content Cards

Data Chat



General

Data Chat | General



General

AI | General

Clients



Integrations



Settings



KPI Forecasting



General

KPI Forecasting | General

Settings & Status

KPI Forecasting | Settings & Status

Seasonality

KPI Forecasting | Seasonality

Metrics by Source

KPI Forecasting | Metrics by Source

Budget Tracking



General

Budget Tracking | General

Anomaly Detection



General

Anomaly Detection | General

Automation Jobs



General

Automation Jobs | General

Change History

Automation Jobs | Change History

URL & Page Checkers

Automation Jobs | URL & Page Checkers

Local & Reviews

Automation Jobs | Local & Reviews

Search Console

Automation Jobs | Search Console

Insights



Managing Insights

Insights | Managing Insights

Change History

Insights | Change History

URL & Page

Insights | URL & Page

Local & Reviews

Insights | Local & Reviews

Other Insight Types

Insights | Other Insight Types

Local Listings



General

Local Listings | General

Profiles & Content

Local Listings | Profiles & Content

Performance & Activity

Local Listings | Performance & Activity

Media

Local Listings | Media

Categories & Services

Local Listings | Categories & Services

Reviews



General

Reviews | General

General

Social Posts | General

Creating Posts

Social Posts | Creating Posts

Managing Posts

Social Posts | Managing Posts

Data Warehouse



Pipelines

Data Warehouse | Pipelines

Access & Credits

Data Warehouse | Access & Credits

Source Fields

Data Warehouse | Source Fields

Data Studio

Data Warehouse | Data Studio

BigQuery

Data Warehouse | BigQuery

General

Clients | General

General

Integrations | General

MCP

Integrations | MCP

Webhook — Automation Payloads

Integrations | Webhook — Automation Payloads

Webhook — Local & Reviews

Integrations | Webhook — Local & Reviews

Webhook — Other

Integrations | Webhook — Other

Account & Billing

Settings | Account & Billing

Users

Settings | Users

Comments & Notes

Settings | Comments & Notes

Notifications

Settings | Notifications

FAQ

Settings | FAQ

Other

Settings | Other

Recent Updates



Account Settings

Settings | Account & Billing

Acknowledging and Resolving Insights

Insights | Managing Insights

Add comment from Slack

Integrations | General

Add comment from Zapier

Settings | Comments & Notes

Settings | Users

AI | General

AI | General

Reports | Content Cards

Anomalies Bulk Action

Anomaly Detection | General

Anomaly Algorithm

Anomaly Detection | General

Anomaly Detection

Anomaly Detection | General

Anomaly Detection Insight

Insights | Other Insight Types

Anomaly Detection Settings

Anomaly Detection | General

Anomaly Detection Webhook Payload

Integrations | Webhook — Other

Anomaly Job Common Errors

Anomaly Detection | General

An overview of Local Listings

Local Listings | General

An overview of Reviews

Reviews | General

Area Chart Card

Reports | Chart Cards

Attributes

Local Listings | Profiles & Content

Automatic Schema Updates

Data Warehouse | Pipelines

Automation: Facebook Ads Destination URL Checker

Integrations | Webhook — Automation Payloads

Automation: Google Ads Change History

Integrations | Webhook — Automation Payloads

Automation: Google Ads Destination URL Checker

Integrations | Webhook — Automation Payloads

Automation: Google Analytics Change History

Integrations | Webhook — Automation Payloads

Automation: Google Business Profile Answer

Integrations | Webhook — Local & Reviews

Automation: Google Business Profile Change History

Integrations | Webhook — Automation Payloads

Automation: Google Business Profile Pending Updates

Integrations | Webhook — Local & Reviews

Automation: Google Business Profile Question

Integrations | Webhook — Local & Reviews

Automation: Google Review

Integrations | Webhook — Local & Reviews

Automation: Google Review Change History

Integrations | Webhook — Automation Payloads

Automation Job Common Errors

Automation Jobs | General

Automation Jobs

Automation Jobs | General

Automation: Microsoft Ads Destination URL Checker

Integrations | Webhook — Automation Payloads

Automation: Page Status Checker

Integrations | Webhook — Automation Payloads

Automation: Robots.txt Change Detection

Integrations | Webhook — Automation Payloads

Automations Bulk Action

Automation Jobs | General

Automation: Search Console Activity

Integrations | Webhook — Automation Payloads

Automation: Search Console Keyword Movement

Integrations | Webhook — Automation Payloads

Auto Resolving

Insights | Managing Insights

Bar Chart Card

Reports | Chart Cards

Budget Campaign Dynamic Filter

Budget Tracking | General

Budget Common Errors

Budget Tracking | General

Budget history

Budget Tracking | General

Budgets Bulk Actions

Budget Tracking | General

Budget Settings

Budget Tracking | General

Budget Status

Budget Tracking | General

Budget Tracker Webhook Payload

Integrations | Webhook — Other

Budget Tracking

Budget Tracking | General

Budget Webhook URL

Budget Tracking | General

Bulk Action

Local Listings | General

Bulk Upload Images

Local Listings | Media

Calendar

Social Posts | General

Cancel Subscription

Settings | Account & Billing

Card Chat

Reports | Editing

Card Data Filters

Reports | Creating & Sharing

Custom Visualizations

‍
‍

Custom Visualizations let you go beyond the form controls in a chart or table editor. On the Custom tab you edit Visualization overrides (JSON) — a partial config that Jepto deep-merges on top of its defaults when the card renders.

This is the same idea as Looker’s Chart Config Editor: keep the data query and common options in the UI, and use JSON only for advanced formatting Highcharts (charts) or table presentation options that the forms don’t expose.

Overview

Available on chart and table cards under Settings → Custom.
Charts: JSON is Highcharts-style options stored on the card as visualization overrides.
Tables: JSON shapes table presentation (columns, rendering, sorting UI, etc.) — not Highcharts.
The editor shows {} when nothing is customized yet.
Turn Custom Chart Override off to make the JSON read-only (charts).

Prefer Chart / Table / Palette for everyday changes. Use Custom when you need options those tabs don’t cover (tooltips, plot bands, line dash styles, fine axis styling, and similar).

When to use Custom

Metrics, dimensions, dates, filters — Data tab (Data Query)
Chart type, common chart options — Chart tab
Table pagination, sorting UI, column display — Table tab
Series colors / report palette — Palette tab (Palettes)
Title, subtitle, card chrome — Card tab
Fast natural-language rewrite of the card — AI Edit / Card Chat
Advanced formatting not in the forms — Custom (this article)

Custom does not replace the data query. It only overrides how the result is drawn.

How to edit

Open a chart or table card in a report (Creating a Card).
Switch to Settings (not AI Edit).
Open the Custom tab.
On charts, leave Custom Chart Override on.
Edit the Visualization overrides (JSON) editor. Start from {} or extend what is already there.
Watch Card Preview update when the JSON is valid.
Fix any JSON error message before leaving — invalid JSON is not applied (preview keeps the last good config).
Save / leave the editor when the preview looks right.

Tips while editing:

Only include keys you intend to change. Jepto stores overrides, not a full chart dump.
After large Chart-tab changes, re-open Custom and confirm your JSON still matches what you want.
Changing chart type resets visualization overrides to {} — Custom JSON for the old type is cleared.

Merge order

When Jepto draws a chart, it deep-merges layers so later layers win on the same property path:

Jepto defaults — built-in options for that chart type (or table defaults).
Form settings — options from Chart / Table / Palette (and related form-driven visualization patches).
Custom tab JSON — the visualization overrides you type on Custom.

Series data still comes from the card’s data query result. Custom should style the chart; it should not try to invent the query.

How layers combine (later wins)

1. Jepto defaults
Chart-type or table built-ins

↓ deep merge

2. Form settings
Chart / Table / Palette (and form-driven visualization patches)

↓ deep merge

3. Custom tab JSON
Visualization overrides you type on Custom

↓

Rendered chart or table
Series values still come from the Data query

Charts vs tables

Charts

Custom JSON is merged with Highcharts options at render time (Highcharts.merge).
Good candidates: chart, plot title/subtitle, tooltip, legend, xAxis / yAxis, plotOptions, caption, annotations, and per-series style keys (for example dashStyle, lineWidth) when you know the series index.
Prefer the Palette tab for colors when possible. Palette changes can strip stale colors overrides from visualization so theme/palette stay consistent (Create Theme).

Tables

Custom edits the same visualization object the Table tab uses (pagination, sorting UI, column widths, cell formats, rendering flags).
Prefer the Table tab for everyday toggles; use Custom for shapes the form doesn’t expose.
Column overrides should use stable field ids that match your Data Query metrics/dimensions.

Important limits

Invalid JSON — shown inline; Jepto does not apply the broken draft.
Chart type change — visualization resets to {}.
Arrays replace, they do not deep-merge — an empty series: [] in Custom can wipe plotted series. Prefer plotOptions or series entries without replacing data.
Don’t put query fields in Custom — metrics and dimensions belong on Data.
Functions / dates / undefined — use plain JSON only (strings, numbers, booleans, objects, arrays). No JavaScript functions in the editor.
Undo — use the editor undo control if a Custom edit goes wrong.

Full Highcharts option reference: Highcharts API.

Examples

These snippets are starting points. Test each one on a real chart or table in your account before relying on them in client reports. Exact keys can differ by chart type.

Chart — background and axis label color

{
  "chart": {
    "backgroundColor": "#f7f7f9"
  },
  "xAxis": {
    "labels": {
      "style": {
        "color": "#334155"
      }
    }
  },
  "yAxis": {
    "labels": {
      "style": {
        "color": "#334155"
      }
    }
  }
}

{
  "tooltip": {
    "backgroundColor": "#0f172a",
    "style": {
      "color": "#f8fafc"
    }
  }
}

Chart — thicker dashed lines (all series via plotOptions)

{
  "plotOptions": {
    "series": {
      "lineWidth": 3,
      "dashStyle": "Dash"
    }
  }
}

Chart — caption under the plot

{
  "caption": {
    "text": "Source: connected client data. Values refresh with the report date range."
  }
}

Table — keep row heights strict (example)

{
  "rendering": {
    "rows": {
      "strictHeights": true
    }
  }
}

If a snippet does nothing, the chart type may ignore that option, or a form/palette setting may be overriding the same path — check merge order above and simplify the JSON to one key at a time.

How merge works (technical)

This section is for advanced users who need to reason about conflicts between form tabs and Custom.

What is stored

Jepto persists visualization as a diff from defaults, not a full Highcharts options object. Empty customization is {}.

Both the Chart (or Table) form and the Custom JSON editor write into that same field. Saving from either path merges into the card config; the preview then re-renders.

Render-time merge (charts)

At display time, chart components roughly do:

Start from chart-type defaults (+ runtime component options such as live series data).
Deep-merge cardConfig.visualization (your form + Custom overrides).
Apply palette / theme color policy where relevant.

Jepto uses Highcharts’ deep merge. Nested objects combine; arrays are replaced as a whole. That is why an empty series array in Custom is dangerous.

Form vs Custom

Chart tab maps form fields → partial Highcharts → strips down to overrides vs type defaults → patches visualization.
Custom tab parses JSON and patches visualization directly.
Palette tab updates palette and may remove color keys from visualization so palette remains the source of truth for series colors.
AI / Card Chat can also patch visualization (and may delete keys with null in AI patches).

Practical rules

Put everyday options in forms; keep Custom lean.
Avoid copying full exported Highcharts configs into Custom — prefer the smallest override that achieves the look.
After changing chart type, rebuild Custom from scratch for the new type.
If preview blanks out after a Custom edit, clear series from your JSON (or remove the whole draft) and undo.

Was this article helpful?



Nice one!

Thanks a lot for your feedback! If you’d like a member of our support team to respond to you, please send a message here



Please try again

Oops! Something went wrong while submitting the form.



Nice one!

Thanks a lot for your feedback! If you’d like a member of our support team to respond to you, please send a message here



Please try again

Oops! Something went wrong while submitting the form.

Custom Visualizations

Overview

When to use Custom

How to edit

Merge order

Charts vs tables

Charts

Tables

Important limits

Examples

Chart — background and axis label color

Chart — tooltip styling

Chart — thicker dashed lines (all series via plotOptions)

Chart — caption under the plot

Table — keep row heights strict (example)

How merge works (technical)

What is stored

Render-time merge (charts)

Form vs Custom

Practical rules