> ## Documentation Index
> Fetch the complete documentation index at: https://moengage.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.
# MoEngage Assist Chrome Extension
> Install the MoEngage Assist Chrome extension to debug your Web SDK integration, inspect live event payloads, and troubleshoot campaigns.
# Overview
The MoEngage Assist Chrome extension is a dedicated debugging tool designed to help developers and marketers monitor and troubleshoot their MoEngage Web SDK integration and implementation. Install the extension to validate and debug your Web SDK integration directly from your browser.
Web SDK version [2.74.00](/docs/release-notes/sdks/web#7th-may-2026) or later is required to ensure complete compatibility and functionality of Web Assist.
With this extension, you can:
* Verify service worker registration.
* Confirm push token generation.
* Inspect event tracking in real time.
* Troubleshoot and debug implementation issues.
* Access campaigns and related features.
# Installation Steps
1. Navigate to the [Chrome Web Store](https://chromewebstore.google.com/).
2. Search for [*MoEngage Assist*](https://chromewebstore.google.com/detail/dhggnkfnnoebbfofpimfehcklnekmbgi?utm_source=item-share-cb).
3. Select **Add to Chrome** to install the extension.
4. Pin the extension to your browser toolbar for quick access.
If the MoEngage Web SDK is not installed on the active webpage, the extension displays an "SDK not found" state. For more information on integrating the Web SDK, see [Web SDK Integration](https://www.MoEngage.com/docs/developer-guide/web-sdk/web-sdk-integration/basic-integration/web-sdk-integration).
# Extension Tabs
When the Web SDK is successfully integrated, the extension populates operational data across the following four tabs.
## Issues
The **Issues** tab highlights critical integration or configuration errors that require immediate attention.
Use the **Filter by issue category** drop-down menu to sort the displayed errors. Categories include:
* **Setup:** Highlights foundational configuration errors (for example, Web Push failing in HTTP mode, missing service worker files, or unsupported Promises requiring polyfills).
* **Track:** Identifies data collection anomalies (for example, passing empty objects as attribute values, missing attribute strings, or blank notification titles).
* **Info:** Flags campaign-delivery errors (for example, attempting to track a card ID that has not been received or has been deleted).
Each issue card provides contextual information and a *Learn More* link for resolution guidance.
## Setup Info
Validate the foundational configuration and environment details of your MoEngage workspace directly from the browser. The **Setup Info** tab provides a comprehensive overview of your Web SDK implementation, structured into the following sections:
Displays core workspace metadata and configuration statuses, including:
* **Data center:** The region where your data is hosted.
* **App ID:** Your unique workspace identifier.
* **Multi ID enabled:** Indicates whether the Multi-ID tracking feature is active.
* **SPA mode enabled:** Indicates whether Single Page Application tracking is enabled.
* **Shopify:** Indicates whether moengage is integrated in the shopify website or not.
* **Billing type:** Outlines your active subscription model ( *Subscriber based billing*).
* **Is sub domain shared?:** Indicates whether the configuration supports shared sub-domains.
* **Settings last fetched:** Shows the relative timestamp of the most recent SDK configuration sync (for example, *Just now*).
Outlines the registration and operational status of your service worker, which is critical for Web Push notification delivery:
* **Status:** Indicates the current registration state (for example, *Registered*).
* **Service worker file:** The defined file path where the service worker script is hosted.
* **Scope:** Defines the URL domain scope that the service worker controls.
Details the specific configuration and current user permission state for Web Push prompts:
* **Opt-in type:** The configured prompt flow (for example, *2-step*).
* **Soft ask:** The user's interaction status with the custom browser prompt .
* **Hard ask:** The user's interaction status with the native browser permission prompt.
* **Push token:** Displays the active device push token if the user has successfully subscribed.
## Track
The **Track** tab monitors real-time data collection payloads and validates the event stream for the active session. It is divided into two sub-tabs:
* **Event**
* **User**
Monitors live behavioral and system events being tracked on the current page.
* **Search and Filter:** Use the dedicated search bar to quickly filter the live stream by a specific event name or attribute.
* **Status Indicators:** Successfully captured event payloads display a green **Tracked** badge next to the event name.
* **Payload Validation:** Select any tracked event to expand its payload and inspect the underlying key-value pairs. Depending on the specific event type (such as on-site messaging interactions or page views), you can validate detailed parameters, including:
* **Campaign Metadata:** Identifiers such as campaign\_id, campaign\_name, and cid.
* **Execution Properties:** Configuration details such as Variation ID, Locale Name, Locale ID, and targeted Campaign Tags.
* **User Context:** Session-specific booleans and strings evaluated at the time of the event, such as Logged In Status, First Visit, and the active URL.
**Note:** Ensure you expand the relevant events during testing to verify that custom attributes and campaign tracking identifiers are being passed correctly to the MoEngage backend.
Displays comprehensive session metadata, identity resolution details, and custom traits for the active user on the current webpage.
Manually clearing local storage resets the MoEngage SDK session and break event tracking. Always utilize the logoutUser() method before clearing localStorage.
* **User identity:** Indicates all the identification associated with the user within the MoEngage ecosystem.
* **Device connection:** Displays detailed information about the connected device and browser.
* **Device UID:** The unique cryptographic identifier generated for the current device or browser instance.
* **Device added:** Confirms whether the device has been successfully registered in the MoEngage backend (for example, *Yes*).
* **Session details:** Provides temporal and sequential data regarding the user's active browsing period.
* **Session ID:** The unique alphanumeric string representing the current active session.
* **Number of sessions:** The cumulative count of sessions associated with specific user on a pariticular device (for example, *93*).
* **Session started on:** The exact localized timestamp indicating when the current session initialized.
* **Session expires on:** The projected timestamp indicating when the current session will automatically terminate due to inactivity.
* **User attributes:** A collapsible list displaying the specific user attributes assigned to the user profile. Successfully logged attributes display a green **Tracked** badge alongside the attribute key and its corresponding masked or unmasked value.
## **Campaign**
The **Campaign** tab enables you to debug and inspect active campaigns targeted at the current user session. It is categorized by channel type:
* OSM (On-Site Messaging)
* Web Personalization
* Cards
**Campaign List:** Provides a searchable index of active campaigns detailing the Campaign Name, ID, and trigger count. **Campaign Properties:** Selecting a specific campaign reveals comprehensive execution details, including:
* Status, Template Type (for example, POP\_UP), Expiry Time, and Updated Time.
* Priority levels and behavioral configurations (for example, blocking, scrollable, sticky).
* The complete campaign payload, which can be copied directly to your clipboard for further analysis.
**Campaign Details**
Selecting a specific campaign card navigates to a detailed analysis view. This expanded view reveals comprehensive execution parameters and behavioral configurations, divided into the following sections:
* Select the **View in Dashboard** link within the Campaign details panel to open the specific campaign configuration directly within your MoEngage workspace.
* If a specific module or feature has not been integrated within your Web SDK implementation, MoEngage Assist displays a descriptive error state to assist with troubleshooting. For example, if the OSM module is missing, the extension indicates: *"OSM not integrated. To start seeing campaigns, please integrate the OSM module on your website."*
* **Campaign status:** Tracks current eligibility and delivery metrics.
* Validates Page eligibility and Display status.
* Displays the total page view impressions for the current load and the lifetime impressions.
* **Campaign properties:** Outlines the core structural configuration and rendering behavior defined in the campaign setup.
* **Metadata:** Includes Template type (for example, POP\_UP), Expiry time, Updated time, and Priority.
* **Rendering Rules:** Details specific UI/UX constraints such as Max show count, Auto dismiss after, Delay between same campaign, Blocking, Scrollable, and Sticky flags.
* **Trigger actions:** Details the specific behavioral conditions required to execute the campaign.
* Identifies the evaluated Primary event (for example, MOE\_PAGE\_EXIT) and confirms its trigger status.
* Displays the rule description and the configured Trigger delay (for example, *Immediately*).
* **Frequency capping:** Displays the global and page-level limits configured to prevent campaign fatigue.
* **Rules:** Outlines the maximum permitted displays for All campaigns (for example, *Max 3 Per day*) and specific Page load constraints.
* **Device frequency data:** Expand this section to view the specific device's execution counts against the configured rules. It breaks down consumption for the Last hour (LH) and the current Date.
