Documentation

Retrieve trigger firing statistics using the Triggers Stats API in Adobe Analytics

Last update: Wed Jun 03 2026 00:00:00 GMT+0000 (Coordinated Universal Time)

Use the Adobe Analytics Triggers Stats API to troubleshoot trigger execution behavior by reviewing how often configured triggers fired for your organization. Requests are authenticated with an Adobe Identity Management System (IMS) bearer token and support configurable lookback windows, optional time buckets, and interpretation of common HTTP error responses.

Description description

Environment

  • Adobe Analytics with Triggers enabled
  • Adobe Campaign (configured for Triggers)
  • Triggers API v1
  • IMS-based authentication

Issue / Symptoms

  • Customers require execution statistics for individual triggers and multiple triggers to analyze trigger efficiency, execution behavior, and overall system performance.
  • The current Triggers UI doesn’t provide consolidated analytics, timestamp-level execution insights, or aggregated trigger metrics.
  • Customers must open each trigger in separate tabs and manually inspect execution data, which becomes inefficient and time-consuming at scale.
  • The existing UI doesn’t support advanced analytical capabilities such as bucketing, grouped aggregations, or comparative trigger analysis.
  • Customers have limited visibility into execution frequency trends, trigger firing distribution, and time-based performance patterns.
  • These limitations prevent customers from efficiently analyzing trigger execution behavior using the Triggers UI alone.

Resolution resolution

Trigger Stats API

Content

  • Purpose
  • Base URL and Auth
  • Prerequisites
  • ENDPOINTS (AT A GLANCE)
  • Error Handling

Purpose

The Triggers API is designed to give Adobe Analytics customers with Triggers enabled access to metrics showing how often their configured triggers have fired. It offers multiple Triggers Stats endpoints that break down these metrics at the IMS Organization level.

Base URL and Auth

Base URL: https://triggers.adobe.net/v1/

Authentication: IMS token

Header: Authorization: Bearer <token>

maxValue = 604800
Lookback window must be greater than zero and less than or equal to maxValue.
Bucket value must be less than or equal to the lookback value and greater than zero.

Prerequisites

  • Triggers enabled and configured in Adobe Analytics & Campaign
  • IMS token

Endpoints (at a glance)

1) GET /{imsOrg}/triggers/stats?lookback={seconds}

Description: Count recent triggers fired for the entire IMS Org, broken down by trigger id.

Parameters:

  • imsOrg (path) - Marketing Cloud Org
  • lookback (query) - seconds (e.g. 3600)

Example Request:

curl -H "Authorization: Bearer token" "https://triggers.adobe.net/v1/3817033753EE89720A490D4D%40AdobeOrg/triggers/stats?lookback=3600" | jq

Example Response:

[
        {
        "triggerId": "0207a1b7-c071-47b3-b919-977b8664fd17",
        "imsOrg": "3817033753EE89720A490D4D@AdobeOrg",
        "count": 2,
        "lookback": 3600
        },
        {
        "triggerId": "041c6f0a-dec7-408a-a980-44611fc42b02",
        "imsOrg": "3817033753EE89720A490D4D@AdobeOrg",
        "count": 5,
        "lookback": 3600
        },
        {
        "triggerId": "09457c3b-0b12-4011-a16d-faa60335508a",
        "imsOrg": "3817033753EE89720A490D4D@AdobeOrg",
        "count": 2,
        "lookback": 3600
        },
        {
        "triggerId": "0adf3198-c240-4d5b-a4e5-2fa4c61b5a78",
        "imsOrg": "3817033753EE89720A490D4D@AdobeOrg",
        "count": 3,
        "lookback": 3600
        },
        ...
    ]

2) Get Trended Trigger Fired Stats for Single Trigger ID

Endpoint: /{triggerId}/trended
Method: GET

Description: Get a trended count of recent triggers fired for a specific trigger id.

Parameters:

  • imsOrg (PathParam): Marketing Cloud Organization
  • triggerId (PathParam): Trigger ID
  • lookback (QueryParam): How far to look back in seconds?
  • bucket (QueryParam): Bucketize the lookback window in seconds

Example Request:

curl -H "Authorization: Bearer token" "https://triggers.adobe.net/v1/3817033753EE89720A490D4D%40AdobeOrg/triggers/stats/b4342025-f8d8-4e05-92f3-92962e43b838/trended?lookback=3600&bucket=300" | jq

Example Response:

{
        "triggerId": "b4342025-f8d8-4e05-92f3-92962e43b838",
        "imsOrg": "3817033753EE89720A490D4D@AdobeOrg",
        "lookback": 3600,
        "trended":
            {
                "1718918100": 5,
                "1718917200": 2,
                "1718918400": 1,
                "1718917500": 2,
                "1718915400": 2,
                "1718916600": 10
            },
        "bucket": 300
    }

3) Get Trigger Fired Stats for Single Trigger ID

Endpoint: /{triggerId}
Method: GET

Description: Get a count of recent triggers fired for a specific trigger id.

Parameters:

  • imsOrg (PathParam): Marketing Cloud Organization
  • triggerId (PathParam): Trigger ID
  • lookback (QueryParam): How far to look back in seconds

Example Request:

curl -H "Authorization: Bearer token" "https://triggers.adobe.net/v1/3817033753EE89720A490D4D%40AdobeOrg/triggers/stats/b4342025-f8d8-4e05-92f3-92962e43b838?lookback=3600" | jq

Example Response:

{
        "triggerId": "b4342025-f8d8-4e05-92f3-92962e43b838",
        "imsOrg": "3817033753EE89720A490D4D@AdobeOrg",
        "count": 22,
        "lookback": 3600
    }

Troubleshoot trigger firing statistics using the Triggers Stats API

Use the following steps to validate requests, interpret responses, and isolate common Triggers Stats API issues.

  1. Confirm environment readiness

    • Verify that Triggers are enabled and configured in Adobe Analytics and Adobe Campaign for the IMS organization used in the request.

  2. Authenticate correctly

    • Send requests to the correct base URL:https://triggers.adobe.net/v1/.
    • Include a valid IMS access token in the request header:Authorization: Bearer <IMS_ACCESS_TOKEN>.

  3. Validate required parameters

    • Set lookback to a value greater than 0 and less than or equal to 604800 seconds.
    • For trended statistics, set bucket to a value greater than 0 and less than or equal to the lookback value.

  4. Verify path parameters

    • Use the correct and properly encoded imsOrg value in the request path.
    • Use a valid triggerId when calling single-trigger endpoints.

  5. Select the appropriate endpoint

    • Use the org-level stats endpoint to retrieve counts for multiple triggers grouped by triggerId.
    • Use the single-trigger stats endpoint to retrieve a total count for one trigger.
    • Use the trended stats endpoint to retrieve bucketed counts over time for a single trigger.

  6. Validate response data

    • Compare request parameters (imsOrg, triggerId, lookback, bucket) with the corresponding fields returned in the response to confirm the API processed the intended inputs.
    • For trended responses, confirm that timestamp keys represent Unix epoch seconds aligned to the specified bucket interval.

  7. Diagnose failures using HTTP status codes

    • Use the returned HTTP status code and the endpoint called to determine whether the issue is related to authentication, invalid parameters, or an incorrect resource path.

Error handling reference

  • 400 Bad Request: The request contains invalid or missing parameters.
  • 401 Unauthorized: Authentication failed or the IMS token is invalid.
  • 404 Not Found: The specified trigger ID or resource doesn’t exist.
  • 500 Server Error: A server-side error occurred while processing the request.
recommendation-more-help
3d58f420-19b5-47a0-a122-5c9dab55ec7f