Companion is a small widget that you can add to your website. This provides a dynamic way to engage your site visitors without requiring them to leave the page. Companion units can deliver interactive experiences, gather first-party data, and promote specific content, providing a valuable touchpoint for visitors.
Before you begin
Confirm the companion unit is disabled before launch.
Identify whether you will embed the Global Snippet Code directly on your website or use a tag manager like Google Tag Manager.
Plan the placement rules to specify which pages on your site will display the companion (All Pages or Specific URLs).
Configure companion settings
1. Behavior
Navigate to the Launch tab.
Click on Website > Companion.
Determine when to display the companion under Behavior.
a. Page Load, which shows right after a user opens a page, or,
b. Scroll Depth, which triggers the companion when a visitor scrolls a certain % of a page. Select the percentage required.Determine How often to display the Companion.
a. Trigger at Most, which sets a limit on how often a visitor can see your companion, or,b. Traffic Percentage, which only shows the Companion to a %
of visitors.
2. Preferences
Determine when the companion widget initially appears by selecting either Open or Closed.
Define the placement of the companion widget on the screen by selecting Left or Right.
Determine the devices on which the companion will be visible. Select All, Mobile or Desktop.
Manage the Privacy Policy link by selecting Jebbit, Custom URL or Don't Show.
Enable or disable the help feature with the 'What is this?' setting.
Define the action of the close button. Select Hide Bubble Text to only close the text element, or Hide Companion to close the entire feature.
3. Placement
Select All Pages to display the Companion on every page of your site.
Select Specific URLs to define rules for showing the Companion on particular pages.
Set rules using ALL conditions match (and) or ANY conditions match (or) logic. Most users use ANY.
4. Icon Design
You can customize how the Companion Experience is displayed and styled. There are two display types:
Display type
Select from the Type dropdown:
Widget
Side Tab
Widget design controls
Size
Width
Height
Button
Icon: Upload a custom icon for the widget
Icon size
Background color
Corner radius
Border width
Border color
Show shadow: Toggle drop shadow behind the widget
Text
Show text: Toggle the text label on or off
Input: Add the text you want shown
Font
Size
Text color
Side Tab design controls
Text
Input: Add the label text
Font
Size
Text color
Background color
Add the global snippet code
Click on your brand name in the upper right corner and select Settings from the drop-down.
Click Onsite Deployment from the left panel.
Click Copy Snippet.
Add it to your website by embedding it directly within the
<head>or<body>tags.
Enable companion
Toggle the Disabled switch to Enabled. This will make your Companion unit live on your website.
You have the flexibility to control when and where the Companion unit appears on your site using either Google Tag Manager's triggering features or the settings within the Experiences platform. For information on configuring the Companion unit's launch settings, refer to the "Configure companion settings" section earlier in this article.
Configure companion via Google Tag Manager
Google Tag Manager provides an alternative method for deploying the Jebbit Global Code Snippet. By using Tag Manager, you gain greater control over when and where the Jebbit code is executed on your pages.
Log into your Google Tag Manager account.
Create a new tag and set the tag type to Custom HTML.
Navigate to your brand name in the upper right corner and select Settings from the drop-down. Select Onsite Deployment on the left panel.
Locate Global Snippet Code from the Onsite Deployment menu.
Click Copy Snippet.
Return to Google Tag Manager.
Paste the copied Global Snippet Code into the HTML field of the tag you created in Step 2. Click Save.
Use Google Tag Manager to indicate which pages on your site the code in the tag should fire on. Additionally, can accomplish the same thing within the Experiences platform from the Launch page for your unit.
Best practices for driving traffic
Every site is unique, and user behavior can vary significantly. To optimize the effectiveness of your Companion experience, consider the following best practices.
Welcome Message: Strong CTA to drive users into companion, highlight incentive, or subject of.
Copy: Given the smaller real estate of companion, we suggest keeping the content concise.
Placement: we recommend placing on high traffic pages.
Next steps
Monitor the companion's performance using the Channel Analytics dashboard.
Test the Companion thoroughly in your development environment before launching in production.
FAQ
Where should I place the Global Snippet Code on my site?
Place the Global Snippet Code on any page where you want to launch your Companion. For single-page launch (e.g., the homepage), add it to the
<head>or<body>of that page. For maximum flexibility, add the snippet globally within the<head>tag to enable launching on any page.
Should I wrap the Global Snippet Code in <script> tags when I paste it into another system?
The most common issue that users run into is not adding <script> tags around the Global Snippet Code. They are not included in the snippet that you grab from Jebbit because they are not needed when pasting the snippet onsite within the <head> or <body> tags. But if you are pasting the Global Snippet Code into another system, like Google Tag Manager, then you will need to make sure you wrap the code in <script> tags.
What types of prompts work best in the companion bubble?
Use prompts like "How can we help you?" or "What are you looking for today?"
What is the difference between "ALL" and "ANY" URL placement rules?
Most customers will use the "ANY" placement rules because "ANY" logic allows the Companion unit to trigger when any one of the URL placement rules that you set are met. Selecting "ALL" is more restrictive, because it means that the Companion will not trigger onsite unless every single rule that you set is met.
What is the best way to test a companion unit before launching on our live site?
Test in a development environment first. The, make sure you incorporate the URLs from your dev environment into the placement rules from the launch page. This will allow you to QA your Companion from the perspective of a consumer engaging with your experience. When you are ready, be sure to add the Global Snippet Code to your production environment and update the URL placement rules from the launch page.