Co-branding the Hosted Experience

The Root hosted property is a white label solution with various branding options to highlight the partnership with Root.

How to Customize

Email your branding assets and selections (listed below) to [email protected]. Please include:

  • A brand slug (see Brand Slug)
  • Your logo files (see Logos)
  • Your brand colors in hexadecimal format (see Color)
  • The text for the back button, if you'd like to change it (see Back Button)

Root will configure your brand in test, confirm with you once it's ready, and repeat the process for production.

Areas of Customization

Brand Slug

A brand slug is the short identifier for one set of branding (logos and colors) on your account. Include the slug you'd like to use in your email to Root. Slugs may only contain lowercase letters, numbers, and hyphens, and must start with a letter or number (for example, acme or acme-auto).

If your account will have more than one look and feel (for example, separate brands or product lines), send one slug per brand along with that brand's assets.

Once Root confirms a brand is configured, you can select it for a customer by adding the brand query parameter to the HostedX link. See Selecting a Brand.

Color

The colors used throughout the experience (everything orange in the examples below), in hexadecimal format (for example, #FF5714).

ColorDescription
PrimaryMain brand color. Used for buttons, highlights, and other key interface elements.
SecondaryOptional. Used for secondary interface elements.
TertiaryOptional. Used for tertiary interface elements and links.

Any color you don't provide defaults to Root orange (#FF5714).

Logos

HostedX supports up to two logos per brand. Both are optional.

LogoWhere it appears
Primary logoThe header at the top of the page, on every page except the mobile onboarding experience (see below).
Co-branded logoIn the body of the landing pages (for example, the customer name and prefill review pages) and in the agent support dialog. This is the best place for a "Partner | Root" logo.

Specifications

  • Format: PNG with a transparent background. Root's configuration tooling only accepts PNG files.
  • Background: The header and page backgrounds are white, and there is no dark mode. Please supply logos that read well on a light background.
  • One file per logo: There are no separate light/dark, square, or icon variants. Whatever file you send is used everywhere that logo appears.
Primary logo (header)Co-branded logo (page body)
Displayed sizeScaled to fit a box up to 200 × 39 px on desktop and tablet. On narrow phone screens the box shrinks to 50% of the screen width (for example, 175 px wide on a 390 px screen). Aspect ratio is preserved and the logo is left-aligned.120 px wide on landing pages (on desktop and mobile), with the height following your logo's proportions. Displayed at about 170 px wide in the agent support dialog.
Recommended aspect ratioAbout 5:1 (wide and short), which fills the header box completely.Any, but a wide lockup around 3:1 to 4:1 (for example, "Partner | Root") keeps the page compact.
Recommended pixel size400 × 80 px (2x). Up to 600 × 120 px (3x) is fine.360 px wide (3x) or more, at your logo's natural proportions.
Minimum200 × 40 px. Anything smaller is scaled up and will look soft.120 px wide. Anything smaller is scaled up and will look soft.
MarginsCrop tightly. Empty space around the artwork shrinks the visible logo.Crop tightly.

Tips

  • Design for a small display. The header logo is shown only about 39 px tall, so fine print and taglines in a lockup become unreadable. Use a simplified, horizontal version of your logo.
  • Wider than 5:1 gets shorter, not bigger. The width is capped at 200 px, so a very wide logo (for example, 8:1) will display only about 25 px tall. A square or tall logo is limited by the 39 px height instead (a square logo displays at 39 × 39 px).
  • Higher resolution helps, but there's no benefit past 3x. Very large files (for example, over 1,000 px wide) only add load time.

What to expect

  • If no primary logo is configured, the header displays the Root logo instead.
  • If no co-branded logo is configured, the co-branded spots simply show no logo.
  • On the mobile onboarding experience, the header contains only a back arrow, so the primary logo is not shown.
  • There is no logo on the loading page itself. The header logo remains visible while the experience loads.
  • The following are not customizable at this time: the browser tab title and favicon (always Root), the page footer, and the support email address shown on error pages ([email protected]).

Back Button

The text display to inform customer where they would be returning if the clicked the button. In the example below all the non-loading pages have a "Back to your vehicle order" which might not make sense for the partner's product.

Selecting a Brand

Once Root has confirmed your brand slug is configured, you can select it yourself by adding a brand query parameter to the HostedX link, with your slug as the value. Leave the rest of the link exactly as it is and only append brand. How you do that depends on how your integration sends customers to HostedX:

Static link (your integration links to HostedX using a bridge_auth_id and experience):

https://<hostedx-url>/?bridge_auth_id=<your-bridge-auth-id>&experience=customer_onboarding&brand=acme

Carrier Platform link (your integration sends the link returned by Create Bridge Link, which carries an auth token parameter instead of bridge_auth_id and experience):

https://<hostedx-url>/?auth=<token>&brand=acme

Brands can be previewed in the test environment before going live by using the same brand parameter on your test link.

How the brand is chosen

brand valueResult
A slug configured for your accountThat brand's logos and colors are used.
Omitted, or a well-formed slug Root doesn't recognizeYour account's default brand is used.
A malformed slug (for example, containing capital letters, spaces, or symbols)No brand is applied, and the experience uses Root's default look.
Any slug when your account has no default brand configuredNo brand is applied, and the experience uses Root's default look.

A few things to keep in mind:

  • The brand is applied when the customer first opens the link, and is then kept for that session. Changing the brand value on a link that has already been opened won't change the brand for that session.
  • The brand value must be a slug that Root has confirmed. Slugs that haven't been configured, or that have been disabled, fall back as described above.
  • Not sure which slug is your default, or want to add or change a brand? Email [email protected].

Hosted solution examples

🗒️

The screenshots below illustrate where branding is applied. Your logos, colors, and layout may differ slightly from the examples.

Loading/Bridging

Quote Customization

Legal Documents

legal docs

Billing

billing

Did this page help you?