> ## 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. # July 2026 > View the July 2026 release notes covering new features and enhancements to the MoEngage platform. ## New In-App Messaging Trigger - On Push Click MoEngage now lets you show an In-App message reliably when a user clicks a push notification. When the user clicks the push, MoEngage displays the linked In-App message on top of the screen they land on, so push captures attention and the In-App closes the loop. Earlier, there was no dependable way to trigger an In-App from a push click. With Push to In-App, the linked message shows every time the push is clicked. The audience is inherited from the push campaign, and the delivery controls are configured automatically so the message shows on every push click. Things to note: * Supported SDK versions are Android BOM SDK 2.3.0 and later, and iOS SDK Package version 10.14.0 and later. * The feature works with Deep Link and Navigate to Screen click actions in the push campaign, but not with Rich Landing. * Periodic push campaigns are not supported. For more information, refer to [Create an In-App Campaign](/docs/user-guide/campaigns-and-channels/in-app-message/create/create-in-app-campaign). ## Merlin AI Campaign Insight Agent for SMS The Merlin AI Campaign Insight Agent now works for SMS, with coverage across all three campaign types at launch: One-Time, Periodic, and Event-Triggered. This adds to the existing support for Push and Email. For SMS, the agent adds: * **Connector performance insights**: Compares the SMS connectors and routes configured in your account to show which are driving delivery and which are dragging performance down. * **Spike and dip analysis**: Explains sudden surges or drops in SMS volume. * **Trigger behavior intelligence**: For Event-Triggered SMS, shows which events are triggering, at what frequency, and from which segments. * **Event-level root cause diagnosis**: When a triggered SMS campaign underperforms, identifies whether the issue lies in the trigger condition, audience qualifier, timing window, connector routing, or creative. * **Trigger frequency benchmarking**: Compares event trigger rates against your historical baselines. If the Insight Agent is already enabled for your account, this update rolls out automatically. If it is not yet enabled, contact your MoEngage CSM for access. ## Auth Flow Revamp MoEngage introduces a revamped authentication flow to prevent complete platform lockouts. You no longer lose access to all workspaces if your most recently used workspace fails due to revoked SSO, an IdP change, or an account block. **Key Updates** * Click the new Login to a different workspace option to choose your workspace before authenticating. * View your authorized workspaces, environment types (Live/Test), and login methods on the Select Workspace screen after 2-Step Verification. * Bypass inaccessible workspaces and log in to available ones immediately, eliminating the need for support tickets. * Experience this unified login flow across the Global Login Screen, DC-specific login pages, MCP, and Mobile App connections. * Keep your existing last-used workspace flow and 2-Step Verification configurations exactly as they are. **Session Management** MoEngage manages Dashboard, MCP, and Mobile sessions independently with distinct timeouts. MCP sessions expire after 30 days or 7 days of inactivity. **Rollout Schedule** This update deploys first to DC-03, DC-04, and DC-06. The remaining data centers and the Global Login Screen follow shortly. For more information, refer to [Log In to MoEngage](/docs/user-guide/getting-started/initial-setup/log-in-to-moengage#log-into-a-different-workspace). ## Email Open Tracking Consent Management MoEngage now provides a native way to manage email open tracking consent in line with regulatory guidance from France's CNIL (effective July 14, 2026) and Italy's Garante (effective October 28, 2026). These regulations require brands to obtain separate, explicit consent before including an open tracking pixel in emails sent to recipients located in those countries. The feature includes: * **Open tracking consent toggle and country selector**: Enable open tracking consent from Email General Settings and choose which countries it applies to. Recipients outside the configured countries are tracked as usual. * **Per-recipient consent attribute**: A new system attribute, `moe_email_open_tracking_consent`, stores each user's preference separately from their email subscription status. You can update it through User Import, the MoEngage SDK, or the Server-to-Server Data API. * **Automatic pixel suppression**: For non-consented recipients in configured countries, the open tracking pixel is not included in emails, including emails already sent. * **Consent management link in the email footer**: When the feature is enabled, MoEngage adds an open tracking preferences link to every email footer, separate from the unsubscribe or Manage Preferences link. * **Consent audit trail**: Every change to a contact's open tracking consent is logged as a system event with the new state, previous state, timestamp, and source. * **Fallback configuration for missing country data**: Configure how the platform handles recipients whose country attribute is not populated. The feature is off by default, so there are no behavior changes until you configure and enable it. Open rates may drop for customers with significant French or Italian audiences, because remaining open data comes only from recipients who have consented. Flows that use Email Opened as a trigger or entry condition may need review, because non-consented recipients do not generate open events. For more information, refer to [Consent Attribute and Open Tracking Pixel](/docs/user-guide/campaigns-and-channels/email/getting-started-with-email/consent-attribute-and-open-tracking-pixel). ## MoEngage Offering APIs The MoEngage Offering APIs are now live, letting you manage offerings programmatically: * **Create Offering**: Generate new offerings with target segmentation, custom scheduling, and content variations. * **Update Offering**: Update targeting or scheduling on active and scheduled offerings. * **List Offerings**: Retrieve a paginated list of offerings for reporting dashboards or automated workflows. These APIs are also available as tools within the MoEngage MCP server. A **Get Offering by ID** endpoint for direct lookup of a single offering is planned. For more information, refer to [Offerings API Overview](/docs/api/offerings/offerings-overview). ## SMS URL Shortening for Personalized Links MoEngage now supports URL shortening and click tracking for SMS links built using personalization parameters, such as user attributes, event attributes, and auxiliary data. Previously, URL shortening and click tracking only worked for URLs that started with `http://` or `www.`, requiring marketers to use custom Jinja as a workaround for personalized links. You can now mark a personalization parameter as a shortened link directly in the SMS campaign builder. MoEngage automatically constructs, shortens, and tracks the resulting URL, eliminating the need for custom Jinja and enabling click tracking for personalized SMS links. For more information, refer to [Create an SMS Campaign](/docs/user-guide/campaigns-and-channels/sms-mms-and-rcs/sms/create-an-sms-campaign#url-addition-and-shortening). ## API Firewall API Firewall adds IP allowlisting for MoEngage Data APIs, restricting access to approved IP addresses so that exposed credentials alone cannot be used to reach your data. With API Firewall, you can: * Create IP allowlists for your authorized servers, add all rules first, then publish them together. * Reject requests from unlisted IPs automatically, even when they carry a valid API key. * Define rules as single IPv4 or IPv6 addresses, CIDR ranges, or IPv4/IPv6 ranges. * Track who modified each rule, when, and from which IP, and see how many Data API calls succeeded from each rule over the last 30 days. The system fails open, so if something goes wrong, legitimate traffic continues to flow. SDK traffic from mobile apps and websites is not affected, because API Firewall applies only to server-to-server Data API requests. API Firewall currently covers Data APIs. For more information, refer to [API Firewall](/docs/user-guide/settings/account/security/api-firewall). ## Amazon S3 Import and Export Enhancements MoEngage has updated its Amazon S3 imports and exports: * **Connection details in the App Marketplace**: Set up S3 connection details once in **App Marketplace** > **Amazon S3** instead of re-entering credentials for each import configuration. This also lets large teams separate screen access permissions across team members. * **S3 Cross-Account Role Assumption**: A new authentication method that removes the need to share static access keys and applies to both imports and exports. * **Export to a single folder**: Choose to export files into a single folder instead of date-wise nested folders, to simplify downstream data pipelines. The release is backward compatible. Existing imports and exports continue to run, and connection setups are migrated to the App Marketplace automatically when the update is enabled. **Rollout Schedule** The feature is released on DC-01 to DC-04. For more information, refer to [Amazon S3](/docs/partner-guide/data-and-analytics/cloud-storage/amazon-s3). ## Attribute Trending Items Trending Items now includes Attribute Trend, which surfaces what is trending within a specific attribute, such as category or region, rather than showing all users the same global trends. You can map trends to any catalog attribute, including category, subcategory, location, or brand, and personalize them using a custom value for a fixed trend across users or a user property for per-user personalization. Item attribute and user action filters let you control the results. For more information, refer to [Trending Items](/docs/user-guide/content/recommendations/advanced-recommendations/category-trending-items). ## New Connectors, Connected Apps, and Dynamic Content MoEngage added new connectors, apps, and dynamic content integrations. * **Telegram media, action, and HTML support**: Include videos and photos with interactive CTAs, and use native HTML for message formatting. Refer to [Telegram](/docs/partner-guide/messaging-channels/messaging-apps/telegram). * **Reddit Ads Audience**: Sync custom segments to target Reddit communities and build lookalike audiences. Available via the Connected Segments add-on. Refer to [Reddit Ads Audience](/docs/partner-guide/retargeting-and-audience-sync/audience-sync/reddit-ads-audience). * **Truecaller**: Add verified Caller ID, SMS, and post-call interaction screens. Refer to [Truecaller](/docs/partner-guide/retargeting-and-audience-sync/audience-sync/truecaller). * **Deepgram AI Voice**: Automate and scale voice interactions such as outreach and surveys. Available via the Connected Channels add-on. Refer to [Deepgram](/docs/partner-guide/messaging-channels/voice/deepgram). * **Events and ticketing dynamic content**: Integrate real-time event and ticketing data from AXS, Oztix, Ticketek, and Ticketmaster into campaigns at the moment of send. Refer to [Ticketmaster](/docs/partner-guide/personalize-and-optimize/dynamic-content/events-and-ticketing/ticketmaster). * **Connected Apps HTML support and key-value pairs**: Format messages with native HTML and conditional logic, and pass dynamic data variables for content routing. Refer to [Create a Channel Connector Config File](/docs/user-guide/campaigns-and-channels/connected-apps/getting-started-with-connected-apps/create-a-channel-connector-config-file#basic-info). **Rollout Schedule** These updates are live across DC-01 to DC-04. ## Six New Data Sources MoEngage added six new data sources that bring real-time signals from payments, subscriptions, loyalty, e-commerce, and contextual data into your campaigns. These integrations are free to connect. * **Superwall**: Capture trial upgrades, membership renewals, and churn for retention and win-back campaigns. Refer to [Superwall](/docs/partner-guide/data-and-analytics/payments-and-subscriptions/superwall). * **Razorpay**: Track approved payments, completed transactions, and abandoned flows to recover pending checkouts. Refer to [Razorpay](/docs/partner-guide/data-and-analytics/payments-and-subscriptions/razorpay). * **NitroX**: Stream item engagements, cart changes, and completed orders to trigger abandonment recovery and cross-sells. Refer to [NitroX](/docs/partner-guide/commerce-and-loyalty/e-commerce/nitrox). * **Xeno Loyalty**: Send real-time loyalty actions such as tier upgrades, point achievements, and product returns. Refer to [Xeno Loyalty](/docs/partner-guide/commerce-and-loyalty/loyalty/xeno-loyalty). * **Xoxoday Loyalife**: Sync loyalty metrics such as point balances, tier standings, and predicted lifespans. Refer to [Xoxoday Loyalife](/docs/partner-guide/commerce-and-loyalty/loyalty/xoxoday-loyalife). * **WooTag**: Use contextual triggers such as local weather, live match updates, crypto trends, and traffic patterns. Refer to [WooTag](/docs/partner-guide/personalize-and-optimize/contextual-location/wootag). ## Computed Traits at Daily Frequency Computed Traits are now available at a daily refresh frequency. This can be enabled on request.