Website Widget Google Analytics Signals

The client-installed TECOBI widget currently sends two Google Analytics event names into the website analytics implementation already running on the client site.

This is the widget engagement event. The widget uses the same event name for launcher opens and option clicks, then distinguishes the deeper option click with a label value.

Clients should treat this as the top-of-funnel widget engagement signal. It is useful for measuring how often visitors enter the widget and which option paths get selected once the widget is open.

gtag('event', 'tecobi_widget_click', {
  category: 'click'
});

ga('send', 'event', 'click', 'tecobi_widget_click');

gtag('event', 'tecobi_widget_click', {
  category: 'click',
  label: '<option title>'
});

This is the successful widget submission signal. It does not fire just because the widget opens or because a form starts. It fires after the widget receives a successful lead creation message and a lead ID is present.

• The widget listens for a tecobi-lead-creation message from the embedded form flow.
• If the message does not include a valid lead ID, the lead event is not sent.
• The current implementation does not attach a custom label or value to this event.

gtag('event', 'tecobi_widget_lead');

ga('send', 'event', 'Widget', 'tecobi_widget_lead');

The widget does not install Google Analytics itself. It checks for the analytics functions that already exist on the client website and uses those if they are available.

Before reporting on widget traffic or widget conversions, confirm the client site is actually exposing the analytics functions the widget expects and that both signals fire in the right sequence.

• Confirm Google Analytics is already installed on the client website before testing widget events.
• Click the floating widget launcher and verify tecobi_widget_click appears in the analytics debugger or network tools.
• Click a widget option and confirm the same click event appears with the option title as a label where supported.
• Complete a real widget lead flow and verify tecobi_widget_lead fires only after successful lead creation.
• If no events appear, verify the client site exposes window.gtag or window.ga before assuming the widget is the problem.
• Use the lead event as the cleaner conversion signal when building reports, goals, or audiences.

Use the two events for different reporting jobs instead of treating them as duplicates.

If a client builds goals, key events, audiences, or ad platform imports from the widget, the lead event is the more reliable success signal and the click event is the better top-of-funnel interaction signal.