Written by Viktor Lazar, Adobe Champion and Adobe Certified Master

CX Enterprise atlas / Shared Services & Administration | Platform & administration

A CX Enterprise core service for defining behaviour rules on Adobe Analytics report suite data, such as cart, browse or form abandonment, and publishing an event whenever a visitor matches one. Events flow through the Adobe-hosted pipeline to Adobe Campaign, which reconciles them with profiles and sends a remarketing email or SMS, typically within 15 to 90 minutes. Since January 2025 only customers with an Adobe Campaign licence can use it.

• Documentation

23 entries, last checked 2026-09-30, element 052 (Xt) of the atlas

Built on 1

• Adobe Analytics

Integrates with 1

• Adobe Campaign

Integrated by 4

• Adobe I/O Events: Analytics Triggers events
• Adobe Analytics: Live Stream add-on, Adobe Campaign integration
• Adobe Campaign: Transactional messaging, Triggers in Campaign
• Adobe CX Enterprise interface

Contains 7 parts, 23 entries

• Trigger types# Collection

  The three kinds of trigger offered when creating a trigger.

  Last checked 2026-09-30

  • Abandonment trigger# Capability

    Fires when a visit includes some behaviour but not a follow-up, for example a product view or cart addition without checkout, after a chosen period of inactivity. Used for cart, browse, search and form abandonment remarketing. The "Likelihood to Return in 30 days" propensity score was removed in 2020.

    Last checked 2026-09-30

  • Action trigger# Capability

    Fires after a specific action or sequence of actions, such as a newsletter sign-up, a credit card application, joining a loyalty programme or watching a particular show.

    Last checked 2026-09-30

  • Session start and session end trigger# Capability

    Fires on the start or end of a visitor session, with a configurable period after which a new session starts.

    Last checked 2026-09-30

• Trigger definition# Capability

  A trigger names one Analytics report suite and a set of rules on its metrics and dimensions: what the visit must include, what it must not include, and how long to wait with no action before firing.

  Integrates with: Report suites

  Last checked 2026-09-30

  • Rule containers# Capability

    Containers hold the conditions of a rule and are evaluated independently at hit level; conditions that must happen in the same hit go in the same container, and containers combine with Any, And or Or logic.

    Last checked 2026-09-30

  • Trigger metadata# Capability

    Extra Analytics dimensions or variables attached to the event payload, such as product name or page, so Campaign can build the right remarketing message.

    Last checked 2026-09-30

  • Triggers limits# Capability

    Technical limits: at most 100 triggers, one report suite per trigger, rules on report suite data only (not Customer Attributes), and no deterministic mapping on shared browsers or devices, where a trigger may carry several visitor IDs.

    Last checked 2026-09-30

• Triggers interface# Application, limited availability

  Also known as Experience Cloud Triggers new user interface

  The redesigned Triggers app opened from the CX Enterprise application switcher, with a trigger list, a creation form and a detail report of how many times each trigger fired. Adobe is rolling it out progressively; a "Go to classic mode" button returns to the previous interface.

  Last checked 2026-09-30

  • Classic Triggers interface# Application

    Also known as Manage Triggers

    The original Triggers pages, reached from the Data Collection card in CX Enterprise ("Manage Triggers"), where recent trigger activity can also be reviewed.

    Last checked 2026-09-30

  • Trigger activity reports# Capability

    Recent trigger events and fired counts shown per trigger. High-volume implementations may not see every event, and there is no API for verifying trigger activity.

    Last checked 2026-09-30

• Triggers pipeline# Service

  Also known as Adobe pipeline for Triggers

  The Adobe-hosted message queue that carries trigger events from Analytics to Campaign. It works on a supplier and consumer model, keeps a separate read position for each consumer so every Campaign instance gets its own copy, and splits messages across about 15 partitions.

  Last checked 2026-09-30

  • Trigger event payload# Capability

    Each event carries the trigger ID, the Analytics hit summary with the requested dimensions and products as JSON enrichments, the visitor aliases, and its partition and offset in the queue.

    Last checked 2026-09-30

  • Pipeline authentication# Capability

    Consumers authenticate with an OAuth credential from an Adobe Developer Console project that includes the Adobe Analytics API and developer access to the Analytics product profile. The earlier private-key gateway authentication was deprecated with Campaign 20.3.

    Built on: Developer Console

    Last checked 2026-09-30

• Campaign consumption# Collection

  How each Campaign version receives trigger events and turns them into messages.

  Last checked 2026-09-30

  • Triggers in Campaign Standard# Integration

    Also known as Campaign Standard Experience Cloud Triggers

    In Campaign Standard, a CX Enterprise trigger is mapped to a trigger event under Transactional messages, enriched with profile data, given a validity period and published, which creates a transactional message template for email or SMS (not push). Each trigger has its own report of events received.

    Integrates with: Campaign Standard, Transactional messaging

    Last checked 2026-09-30

  • Triggers in Campaign Classic v7 and v8# Integration

    Also known as Campaign pipelined triggers

    In Campaign Classic v7 and Campaign v8, the pipelined process on the marketing server pulls events from the pipeline and hands each one to a JavaScript connector, after which workflows use the events for targeting. Adobe states it can process about a million triggers per hour.

    Integrates with: Campaign Classic v7, Campaign v8

    Last checked 2026-09-30

    • pipelined process# Service

      The always-running Campaign server process that connects to the pipeline, authenticates, retrieves events and processes them with configurable thread counts and retry windows. It requires Campaign 20.3 or Gold Standard 11 and later.

      Last checked 2026-09-30

    • NmsPipeline_Config option# Capability

      The JSON option listing the topics the instance listens to, its consumer name, and which trigger IDs (or a wildcard for all) go to which JavaScript connector; an aliases topic is also supported.

      Last checked 2026-09-30

    • Trigger JavaScript connector# Capability

      A custom processPipelineMessage function that parses each event's XML and JSON and writes it to Campaign tables with the QueryDef and Writer APIs.

      Last checked 2026-09-30

    • Pipeline monitoring# Capability

      A REST status service exposed by pipelined, with indicators such as received, processed, discarded and pending messages and time since the last connection check.

      Last checked 2026-09-30

• Visitor reconciliation# Capability

  Matching a trigger to a Campaign profile through the aliases it carries: the CX Enterprise visitor ID for anonymous visitors who already have a profile, or declared IDs (hashed or encrypted allowed) for signed-in visitors, with the alias defined as a Customer Attributes data source and mapped in Campaign.

  Built on: Visitor ID Service

  Integrates with: CX Enterprise Customer Attributes

  Last checked 2026-09-30

• Requirements and licensing# Capability

  Adobe activates Triggers for an organisation on request. It needs an Adobe Analytics package, an Adobe Campaign licence (required since 30 January 2025), the visitor ID service deployed through tags, and a website on the same domain as the Campaign sending domain; Analytics and Campaign must be in the same organisation.

  Integrates with: Tags, Campaign integration

  Last checked 2026-09-30

Sources 5

• experienceleague.adobe.com/en/docs/core-services/interface/services/triggers
• experienceleague.adobe.com/en/docs/experience-cloud/triggers/home
• experienceleague.adobe.com/en/docs/experience-cloud/triggers/overview
• experienceleague.adobe.com/en/docs/core-services/interface/services/overview
• experienceleague.adobe.com/en/docs/analytics/release-notes/previous/2025