Skip to main content
You can customize the appearance of Reach to match your application’s branding through the theme property in the SDK configuration.

Theme Configuration

Reach supports shadcn/ui’s styling conventions, making it easy to maintain consistent design.

Color Format Support

Reach supports multiple color format types:
  • HEX colors: #00758a
  • Named CSS colors: pink
  • HSL (shadcn/ui format): 240 5.9% 10% (hue saturation lightness)
  • Tailwind classes: bg-purple-500
We only support the default tailwind background color classes (bg--). Custom color names, bg-inherit, bg-current, and bg-transparent are not supported. To see a full list of supported tailwind colors, please refer to the tailwind documentation.

Font Customization

Reach allows you to customize the fonts used throughout the interface. You can use any system font or any font available on Google Fonts—just specify the font name in your theme config, and Reach will automatically load it for you. Example: Using a Google Font
If you specify a font that is not a system font, Reach will automatically inject the appropriate Google Fonts <link> tag for you. You do not need to manually include any font imports.

Key Style Variables

System fonts include:
  • system-ui
  • apple-system
  • BlinkMacSystemFont
  • Segoe UI
  • Roboto
  • sans-serif

Language

Reach supports multiple languages through the language configuration option. Currently, we support:
  • English (en)
  • Spanish (es)
To set the language, specify the language code in your configuration:
If no language is specified, Reach detects the user’s preferred language in this order:
  1. The lang URL parameter on your page (for example, ?lang=es)
  2. The language previously saved in local storage
  3. The browser’s language setting
For language requests or to discuss adding support for additional languages, please contact our support team at support@embedreach.com.

Customizing Copy

You can replace specific words and strings in the Reach interface with language.overrides. Overrides are set per feature and per language, and we support en and es for every key. Any key you leave out keeps its default. Copy overrides are currently available for Engage, Measure, and Reputation.

Engage terminology

You can rename the core terms used throughout Engage to fit your product. For example, to use “Contacts” instead of “Users”:
Each term has a singular key and a plural _other key. Set both together: overriding only one of the pair is not supported.
The full list of Engage terms and their English defaults:

Engage onboarding screen

When Engage onboarding is enabled (see Hiding or Enabling Features), businesses that haven’t set up Engage see an introductory screen. You can replace its copy with the ftue keys:
The full list of onboarding keys and their English defaults: The _email_only variants are shown instead of eyebrow and description when SMS is hidden.

Engage AI bar

When the AI automation builder is turned on, the automations and broadcasts lists show a prompt bar that opens the builder with whatever the user types. You can replace its heading and the line next to it with the ai_bar keys:
The full list of AI bar keys and their English defaults:

Measure dashboard

You can rename the column headers in the Measure transactions table. For example, to show “Order ID” instead of “Purchase”:
Partner overrides take precedence whether or not transaction purchase names are mapped. The full list of Measure strings and their English defaults:

Reputation headings

You can rename the headings and labels Reputation shows while a business sets it up and changes its settings. For example, to call the feature “Review Agent”:
The full list of Reputation keys and their English defaults: settings.open_label is the accessible name of the settings button on the Reputation dashboard. Screen readers announce it; it is not shown on screen.
The wording that describes how review requests treat your customers, such as the approach choices in setup and the Google Business Profile connection notes, can’t be overridden.
To request additional customizable copy, please contact our support team at support@embedreach.com.

Hiding or Enabling Features

You can hide or enable parts of Engage in the SDK configuration.
You can also hide SMS or sales by adding ?hideSms=true or ?hideSales=true to your page URL. URL parameters can only hide these features, not re-enable them.

Skipping the Feature Explainer

Every feature opens on an explainer landing page that introduces it before any setup begins. If your product already explains the feature, set explainer to skip and the business drops straight into the onboarding wizard instead.
The setting applies to every feature, and the explainer stays reachable: dismissing the wizard reveals it, so a business that wants the introduction can still read it. Unrecognized values log a warning and fall back to show. This does not change which businesses see onboarding at all. A business that has already completed setup still lands on its dashboard.