Install the Website Chat Widget
Add a branded messaging experience to an approved website so visitors can ask questions, share contact details, and reach the right ConvoRev conversation path.
Configure, install, and test
Create or select the website widget in ConvoRev, copy the installation code, place it on your approved website, and test the complete visitor journey before launch. Use a floating widget for site-wide access or an inline widget when chat should appear inside a specific page section.
Plan the visitor experience
Have these decisions ready before you copy the installation code. This keeps the first live experience focused and easier to verify.
Approved pages
Choose where the widget should appear and whether any pages should be excluded.
Brand presentation
Confirm the display name, logo, colors, welcome message, and starter questions.
Conversation route
Select the AI Agent, inbox, campaign, or handoff path that should receive visitors.
Visitor details
Decide which contact fields are necessary and avoid requesting sensitive personal information.
Configure the widget in ConvoRev
- 1
Open the website chat settings
Sign in to the correct ConvoRev account and open the website widget or chat interface settings.
- 2
Set the appearance
Choose the launcher position, brand colors, contrast, corner style, display name, and logo. Preview the result against both light and dark page backgrounds.
- 3
Write the opening experience
Add a concise welcome message and starter questions that reflect the most common visitor goals. Keep the first interaction clear rather than presenting too many choices.
- 4
Assign knowledge and routing
Select the AI Agent and approved knowledge sources. Confirm where a conversation goes when a visitor requests a person or the agent reaches a boundary.
- 5
Save and copy the configuration ID
Save the widget, then copy the complete installation snippet. Do not change the configuration identifier inside the generated code.
Choose the installation type
Use the option that matches how you want visitors to access chat. Replace the example identifiers below with the values from your own ConvoRev configuration.
Floating widget
Best for a launcher that stays available across the website.
Add the script before the closing </body> tag or in your builder's site-wide custom code area.
<script src="https://api.convorev.com/v1/chat-widget/CONFIG_ID"></script>Inline widget
Best for a dedicated contact, support, or conversation section.
Place the container where the chat should appear, then load the embed script once on the page.
<div data-chat-widget="CONFIG_ID" style="width:100%;height:600px;"></div>
<script src="https://api.convorev.com/v1/chat-widget/embed.js" async></script>Optional campaign route
Use only when a specific campaign or approved route has been configured for this widget.
<script src="https://api.convorev.com/v1/chat-widget/CONFIG_ID?campaign=CAMPAIGN_ID"></script>CONFIG_ID and CAMPAIGN_ID are placeholders. Keep the approved api.convorev.com source and your exact identifiers intact.Add the code to your website
The field name varies by platform, but the installation principle is the same: add the complete code once, publish the change, and clear any page or site cache.
| Website setup | Where to place the code | Key check |
|---|---|---|
| Custom HTML website | Before the closing </body> tag, or in the intended inline section | Load the script only once |
| Website builder | Site-wide custom code, footer code, or an HTML/embed block | Confirm the builder accepts scripts |
| WordPress | A trusted header/footer insertion method or a custom HTML block | Avoid duplicate placement from the theme and a plugin |
| Shopify | The active theme layout before </body>, or an approved custom section | Retest after theme changes |
| Tag manager | A custom HTML tag triggered on the approved pages | Verify consent and trigger rules |
Test the implementation before launch
Open the published page as a visitor rather than testing only inside the website editor. Use a private browser window to reduce the chance that extensions, cookies, or an authenticated session affect the result.
- The launcher or inline chat appears on every intended page and stays hidden where excluded.
- The widget works on desktop and mobile without covering navigation, forms, or important buttons.
- The welcome message, starter questions, branding, and visitor fields are correct.
- A common question receives an accurate answer from the assigned knowledge.
- An unknown or out-of-scope question follows the expected fallback or handoff path.
- The conversation and captured details reach the correct ConvoRev inbox or route.
Launch gate
Do not promote the widget until a complete test conversation has reached the expected destination and a team member can find and respond to it.
If the widget does not appear
The widget is missing everywhere
Confirm the published page contains the complete snippet, the configuration ID is correct, and the script appears only once. Check that the website or domain is approved in the widget settings, then clear the site cache and retest in a private window.
It works in the editor but not on the live site
Publish the latest website version and inspect any cache, consent, Content Security Policy, or script optimization rules. Some builders do not execute scripts inside an editor preview.
It appears on the wrong pages
Review both the ConvoRev display rules and the placement or trigger used by your website platform. A site-wide footer insertion overrides page-specific placement unless an exclusion rule is active.
The widget loads, but answers or routing are wrong
Verify the assigned AI Agent, knowledge sources, campaign, inbox, fallback behavior, and coverage settings. Re-run a controlled test after every routing change.
It works for some visitors only
Test another browser and device, disable privacy or script-blocking extensions temporarily, and compare consent choices. Record the page URL, browser, device, time, and any console error before contacting support.
Protect privacy and maintain the experience
Collect only what you need
Keep visitor fields relevant to the conversation and avoid asking for passwords, payment details, health information, or other sensitive data.
Review real conversations
Use early conversations to improve starter questions, knowledge coverage, routing, and handoff instructions.
Retest after website changes
Theme updates, consent tools, caching changes, and page redesigns can affect placement or loading.
Keep ownership clear
Assign a team member to review unanswered questions and confirm the widget remains aligned with current offers and policies.
Send us the details
Include the affected page URL, browser and device, approximate test time, what you expected, what happened, and a screenshot of any browser console error.