Connect Boei with your analytics platform to track widget interactions and measure conversions.
How to get there: Go to Analytics in the top menu.
When someone uses Boei on your site:

That's it! Boei will now send events to your analytics platform.
Boei sends two types of events:
| Event | Triggered When |
|---|---|
BoeiOpened |
Widget is clicked/opened |
BoeiConversion |
Form submitted or action completed |
When a visitor submits their contact details through any Boei form or chatbot, the following data is sent to your analytics platforms:
| Field | Description |
|---|---|
event |
Your conversion event name (e.g. BoeiConversion) |
event_type |
lead_collected |
lead_email |
The lead's email address |
lead_phone |
The lead's phone number |
lead_name |
The lead's name |
lead_source |
Where the lead came from: chatbot, contact_form, call_me_back, newsletter_signup, feedback_form |
page_url |
The page URL where the lead was collected |
enhanced_conversion_data |
Object with email and phone_number for Google Ads Enhanced Conversions |
Sends a conversion event with lead_email, lead_phone, lead_name, and lead_source as event parameters.
Fires a standard Lead event with Facebook Advanced Matching parameters (em, ph, fn) for improved ad attribution and audience matching.
Lead data is sent from all Boei lead capture points:
The enhanced_conversion_data object in the dataLayer is formatted for Google Ads Enhanced Conversions. In your GTM container, configure your Google Ads conversion tag to use this data for better conversion matching.
In addition to the events above, Boei fires four engagement events from chat conversations (AI chatbot, live chat, and AI agents). These let you build a full funnel (opened → consent → started → escalated → assigned → lead) and create remarketing audiences for high-intent visitors.
| Event | Triggered When |
|---|---|
chat_started |
Visitor submits their first message (send button, Enter, or quick-prompt button click). Fires before any consent or lead-flow gate, so it represents intent to chat. |
chat_consent_accepted |
Visitor accepts the consent checkbox (only if consent is enabled). Use chat_started as the denominator to measure consent acceptance rate. |
chat_escalated |
Conversation is handed off from AI to a human (queued for an agent) |
chat_assigned |
A human agent actually picks up / is assigned to the live chat |
Each event includes a payload your tags can read:
| Field | Description |
|---|---|
chatbot_id |
The widget UUID (on chat_started, chat_escalated, chat_assigned) |
consent_given_at |
ISO timestamp of consent acceptance (on chat_consent_accepted) |
waiting_for_agent |
true if no agent picked up yet (on chat_escalated) |
agent_name |
Name of the assigned agent (on chat_assigned) |
Yes. As soon as you toggle on Google Analytics 4, Google Tag Manager, Facebook Pixel, or Simple Analytics, these events flow automatically. No code changes on your site.
window.dataLayer. To forward them to a downstream tag (Google Ads, Meta CAPI, etc.), create a Custom Event trigger in GTM matching the event name (e.g. chat_started) and attach it to your tag.trackCustom events. Visible in Events Manager under Custom Events. Useful for building Custom Audiences (e.g. "people who started a chat but didn't convert").chat_started (exact match).Customize the conversion event name per channel:

This is useful for tracking different types of conversions separately.
See how often visitors:
Create goals based on:
Identify which channels drive the most engagement and conversions.