MoEngage - Cross-Channel Marketing Consent

Overview

MoEngage is a customer engagement and marketing automation platform that enables brands to deliver personalized communications across push notifications, email, SMS, in-app messaging, and web channels. Its web SDK collects detailed behavioral data from website visitors to build audience segments and trigger automated cross-channel campaigns based on user actions.

What This Script Does

MoEngage deploys a JavaScript SDK loaded from cdn.moengage.com and related domains. The SDK initializes on page load and begins tracking visitor behavior including page views, button clicks, form submissions, scroll events, and custom-defined actions. It assigns a persistent device identifier stored in browser cookies and localStorage, which survives session boundaries and enables long-term behavioral profiling. The SDK also manages web push notification permissions — prompting visitors to allow browser push notifications and registering the device token with MoEngage's servers.

Data Collection and Transmission

The SDK collects page URLs, referrer data, UTM parameters, device and browser metadata, and timestamps for all tracked events. Custom events configured by the site owner (such as product views, add-to-cart actions, or signup completions) are captured with associated properties. All event data is transmitted to MoEngage's ingestion endpoints (api-0X.moengage.com) and associated with the visitor's unified profile. Cookies and localStorage keys include the MoEngage device ID, session identifiers, and push notification state.

Consent & Compliance

MoEngage is classified as analytics and marketing technology. Under GDPR and the ePrivacy Directive, the behavioral tracking, persistent device identification, and push notification registration all require explicit prior consent. The SDK processes personal data for profiling and targeted marketing communications, which falls squarely within consent requirements. Under CCPA/CPRA, the detailed behavioral data collected by MoEngage — including browsing history, interaction patterns, and device identifiers — constitutes personal information. Its use for cross-channel marketing targeting qualifies as "sharing" of personal information, triggering "Do Not Sell or Share" opt-out requirements. MoEngage scripts must not execute until valid consent is obtained.

Should You Block This Without Consent?

Yes. MoEngage performs extensive behavioral tracking and builds marketing profiles for cross-channel campaign targeting. Both the analytics data collection and the marketing automation features require explicit consent before the SDK loads.

Visit website

Consent Categories

Analytics

Marketing

Also Known As

MoEngageMoEngage SDKMoEngage push notificationsMoEngage trackingMoEngage cookiesMoEngage analytics

Industries

Computers Electronics and Technology

Tracked Domains (1)

moengage.comAnalytics

Frequently Asked Questions

Does MoEngage require consent before loading?

Yes. MoEngage performs extensive behavioral tracking — page views, clicks, scroll events, and custom actions — to build audience segments for push notifications and cross-channel campaigns. Both the analytics and marketing functions require explicit prior consent before the SDK loads.

What does the MoEngage SDK store in the browser?

MoEngage assigns a persistent device identifier stored in cookies and localStorage that survives session boundaries for long-term profiling. It also stores push notification registration state, session IDs, and custom event data. All data is sent to api-0X.moengage.com ingestion endpoints.

How does ConsentStack manage MoEngage?

ConsentStack blocks MoEngage from loading until the visitor grants both analytics and marketing consent. The SDK is held behind a dual-category gate because its device fingerprinting, behavioral profiling, and push registration all require consent under GDPR and CCPA. ConsentStack enforces this automatically.