WooAI Analytics Integration Guide

Overview

WooAI Chatbot Pro tracks every chat interaction automatically across all three analytics platforms at the same time. The plugin’s internal Dashboard in WP Admin also records all events independently — it is never blocked by ad-blockers and gives you a reliable baseline even when external SDKs are unavailable.

Supported providers

Quick setup

Google Analytics 4

1. Get your Measurement ID: go to analytics.google.com → Admin → Data Streams → your web stream. The ID is in the format G-XXXXXXXXXX.
2. In WordPress admin: WooAI Assistant → Analytics Settings → Google Analytics 4 → toggle ON → paste ID → Save.
3. Optional: Enable the GA4 DebugView mode toggle to see events in real-time during testing. Disable it for production.

Meta Pixel

1. Get your Pixel ID: go to business.facebook.com → Events Manager. The Pixel ID is 10-16 digits.
2. In WordPress admin: WooAI Assistant → Analytics Settings → Meta Pixel → toggle ON → paste Pixel ID → Save.

Mixpanel

1. Get your Project Token: go to mixpanel.com → Settings → Project Settings → Project Token.
2. In WordPress admin: WooAI Assistant → Analytics Settings → Mixpanel → toggle ON → paste Token → Save.

Verify it works

Complete event taxonomy

The table below lists every event the plugin fires. Events are fired to all enabled providers simultaneously. Ecommerce events are marked with 🛒.

Note on custom events: Meta Pixel has a limited set of standard events (shown as “standard” below). All other events use Meta’s custom event API under the WooAI* namespace. GA4 uses wooai_* prefix for non-standard events.

Note on product_view vs products_viewed in Meta Pixel: To avoid double-firing ViewContent events when a product carousel displays multiple products, products_viewed (list-level) fires as a Meta custom event (WooAIProductsViewed), while individual product_view events use the standard ViewContent for retargeting. As of v0.38.19.

Custom event naming rules: GA4 auto-prefixes unmapped events as wooai_*. Meta Pixel auto-formats unmapped events as WooAI<PascalCase>. Mixpanel uses WooAI <Title Case> for unmapped events.

Standard ecommerce event parameters

All four ecommerce events (add_to_cart, view_item, begin_checkout, purchase) send rich product data to every provider. Here is exactly what each platform receives.

Google Analytics 4

Sent via window.gtag('event', eventName, params):

Per-product fields inside items[]:

Meta Pixel

Sent via window.fbq('track', eventName, params):

Mixpanel

Sent via window.mixpanel.track(eventName, properties):

Privacy / GDPR / Consent behavior

With a Consent Management Platform (CMP) installed

WooAI integrates with the WordPress Consent API. Compatible CMPs include Complianz, CookieYes, Cookiebot, and any plugin implementing the WP Consent API standard.

• Analytics events fire only after the visitor accepts analytics/statistics cookies.
• GA4 Consent Mode v2 is supported: the default state sent before consent is analytics_storage: denied and ad_storage: denied. When the visitor accepts, the CMP calls gtag('consent', 'update', ...) to grant the relevant categories.
• Meta Pixel and Mixpanel SDKs are initialized but do not fire events until consent is granted.

Without a CMP installed

Events fire immediately when provider IDs are configured. The default GA4 Consent Mode v2 state is analytics_storage: granted.

What data is sent

• No personal data: only anonymous chat session IDs, product IDs, and monetary values.
• Users identify themselves only if they voluntarily share personal information in the chat.
• The 90-day visitor cookie (waa_visitor_id) is set only with analytics consent. Without consent, an ephemeral session-only ID is used that is never persisted.

Override consent behavior (developer filter)

add_filter( 'woo_ai_chatbot_consent_default', function( $state, $cmp ) {
    // Force denied by default regardless of CMP detection
    return 'denied';
}, 10, 2 );

Data flow

User action in chat widget
          |
          v
  trackEvent() central dispatcher
  (analytics/index.ts)
          |
    +-----+--------------------------------------------+
    |                                                  |
    v                                                  v
Internal: POST /woo-ai/v1/analytics/events     External providers (parallel):
          |                                           |-- window.gtag(...)        --> GA4
          v                                           |-- window.fbq(...)         --> Meta Pixel
  waa_events DB table                                +-- window.mixpanel.track() --> Mixpanel
          |
          v
  WP Admin Dashboard
  (Conversations + KPIs)

All three external providers fire in the same JavaScript tick — there is no serialization. The internal backend call is asynchronous and does not block the user experience.

Limitations and roadmap

• Ad blockers (~25-30% of desktop users) block external SDKs. The internal Dashboard is always-on and unaffected. Use it as your ground truth for absolute numbers.
• Server-side attribution (GA4 Measurement Protocol, Meta Conversions API) – planned for v0.40+. When available, it will recover approximately 30% of purchases that ad-blockers currently hide from external providers.
• Cross-domain checkout – if your checkout domain differs from your shop domain, GA4 session continuity requires manual linker configuration. Contact support for assistance.
• Revenue currency – requires plugin v0.38.17+. Earlier versions may report revenue in USD regardless of store currency.

Troubleshooting

Still stuck? Open WP Admin → WooAI Assistant → Analytics Settings and use the built-in connection test button, or check the browser console for [GA4Tracker], [MetaPixel], and [Mixpanel] log messages.

Settings page direct link: /wp-admin/admin.php?page=woo-ai-chatbot-analytics-settings

8. Chat Log Centralization (v0.38.22+)

Closed chat sessions are automatically pushed (hourly) from each client site to the central License Manager database on dev37. This allows the WooAI team to analyze conversations for AI quality improvement.

What gets pushed

• Session metadata: start/end time, message counts, outcome, language
• Full conversation messages (user + AI turns with timestamps)
• Hashed visitor identifier (SHA-256 — never the raw cookie value)
• AI provider, model used, and topic metadata

How it works

The plugin registers an hourly WP-Cron job (woo_ai_chatbot_push_chat_logs). When it fires, it fetches up to 50 expired sessions not yet pushed, builds a JSON payload, and POSTs to:

POST https://dev37.leowebmarketing.pro/wp-json/wooai-license/v1/chat-logs/upload

The endpoint validates the license key and domain activation before accepting data. Sessions are marked pushed_to_lm = 1 on success.

Privacy

The visitor_id cookie value is SHA-256 hashed before transmission — the raw value never leaves the client site. Right-to-be-forgotten requests: contact support to delete by hashed visitor ID.

Retention

• Central LM database (dev37): 90 days
• Local client site: sessions are retained per the existing session expiry setting

Viewing logs

Access the central log viewer at: WP Admin (dev37) → Licenses → Chat Logs