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<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 thelanguage configuration option. Currently, we support:
- English (en)
- Spanish (es)
- The
langURL parameter on your page (for example,?lang=es) - The language previously saved in local storage
- The browser’s language setting
support@embedreach.com.
Customizing Copy
You can replace specific words and strings in the Reach interface withlanguage.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.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 theftue keys:
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 theai_bar keys:
Measure dashboard
You can rename the column headers in the Measure transactions table. For example, to show “Order ID” instead of “Purchase”: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”: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.
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, setexplainer 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.