Google Analytics Configuration Guide

Note: This GA4 event schema is only available as a togglable feature with Envive v3. If you are using Envive v2, a different subset of events applies. See Widget Analytics Event Sources for more information.

Envive can make a set of GA4-friendly events available on your site via window.dataLayer. This lets you combine Envive engagement signals (chat usage, widget interactions, enablement status, etc.) with your existing GA4 reporting to build a complete picture of performance.

This page explains what Envive provides, what you (the merchant) are responsible for, and a few common setups that work well in practice.

Related: Schema Doc

---

What Envive provides (and what we don’t)

✅ What Envive provides

When enabled, Envive will push events into window.dataLayer using a stable event schema designed for GA4.

• These pushes are only a connection point.

• They are designed to be easy to forward into GA4 with a tag manager such as Google Tag Manager (GTM).

❗ What Envive does not provide automatically

Envive does not automatically create GA4 tags/triggers in your account.

To get Envive events into GA4, you (or your analytics team/agency) must:

1. capture the Envive pushes from window.dataLayer, and

2. forward them into GA4 using your tag manager configuration.

---

Important: Envive must enable GA4 dataLayer pushes for your store

By default, Envive events may not appear in your window.dataLayer.

To begin:

1. Request enablement from the Envive Team (your CSM or support contact).

2. Once enabled, Envive will begin pushing eligible events into window.dataLayer.

3. After that, your tag manager can begin forwarding those events to GA4.

If you configure GTM/GA4 before enablement, your setup may look “correct” but you will not see events flowing until Envive turns it on.

Note: You can easily see what is available in your window.dataLayer by opening developer tools (F12) and navigating to the Console tab then typing in window.dataLayer.

---

How the data flows (high level)

Most merchants use this pattern:

1. Envive pushes an event to window.dataLayer

2. Your Tag Manager (GTM, etc.) listens for that event

3. Your GA4 tag sends a GA4 event with selected parameters

4. GA4 reports show the event and any parameters you register as custom dimensions/metrics

Think of Envive as providing “signals”. Your tag manager is the bridge that turns those signals into GA4 events.

---

What you should expect in GA4

1) These events are “base signals”

Envive intentionally publishes a small set of stable, GA-safe events and parameters. We avoid:

• free text content (privacy + high cardinality)

• raw URLs and other high-cardinality values

• internal UUIDs that typically aren’t useful in GA4

2) You build derived metrics in GA4 (or your BI)

Most merchants combine Envive events with their existing GA4 events to create derived metrics such as:

• envive_assisted_conversions

• envive_unassisted_conversions

• engagement-to-purchase funnels (e.g., chat request → purchase)

• performance segmented by Envive enablement (envive_enabled = true/false)

Envive provides the building blocks; you define what “assisted” means for your business.

---

Common setup: Google Tag Manager (GTM)

Below are a few “foolproof” configurations that are common across merchants. These examples are intentionally practical and conservative.

Note: UI labels may differ slightly depending on your GTM version, your GA4 setup, and whether you’re using GTM containers managed by an agency.

Simple GTM Setup: One GA4 Event tag per Envive event

This is the simplest and most reliable approach.

Step 1 — Create a Custom Event trigger

In GTM:

• Triggers → New → Custom Event

• Event name: envive_initialized

• (Optional) “This trigger fires on”: All Custom Events

Repeat for other Envive events you want (e.g., envive_chat_request, envive_chat_response).

Step 2 — Create a GA4 Event tag

• Tags → New → Google Analytics: GA4 Event

• Configuration tag: select your existing GA4 Configuration tag

• Event name: envive_initialized

Add event parameters (examples):

• envive_enabled → {{DLV - envive_enabled}}

• sales_agent_enabled → {{DLV - sales_agent_enabled}}

• start_time_ms → {{DLV - start_time_ms}}

• initialize_time_ms → {{DLV - initialize_time_ms}}

Attach the trigger created in Step 1.

Step 3 — Create Data Layer Variables (DLVs)

For each parameter you want to send:

• Variables → New → Data Layer Variable

• Name: DLV - envive_enabled

• Data Layer Variable Name: envive_enabled

Repeat for other parameters.

Step 4 — Test in GTM Preview

Use GTM Preview/Debug:

• confirm the Custom Event fires

• confirm the GA4 Event tag fires

• confirm parameters are populated (not undefined)

---

GA4 configuration tips (so the data is usable)

Register parameters you care about

In GA4, event parameters do not automatically appear everywhere.

To use parameters like envive_enabled in reports/explorations, you may need to register them as:

• Custom dimensions (most common)

• and in some cases, custom metrics (for numeric values you want to aggregate)

Give it time

GA4 reporting is not always instant. Even after setup is correct, you may see delays before new events/parameters appear in standard reports.

---

Troubleshooting checklist

If you don’t see Envive events in GA4:

1. Confirm Envive enablement

   • Envive events will not appear in window.dataLayer until the Envive Team enables them for your store.

2. Confirm events exist in the dataLayer

   • Use GTM Preview/Debug or your browser dev tools to verify the custom event names (e.g., envive_initialized) are actually occurring.

3. Confirm GTM triggers match the event names exactly

   • Event names are case-sensitive.

4. Confirm your GA4 Event tags are firing

   • In GTM Preview, verify the GA4 tags fired on the expected events.

5. Confirm parameters are being sent

   • In GTM Preview, check that your Data Layer Variables return values (not undefined).

---

Where to go next

• Review the full event and parameter definitions: Schema Doc

• If you’re ready to start: contact the Envive Team to enable GA4 dataLayer pushes for your store.