Limits

Recommended limit: 10,000 active live activities.

Recommended limit: 10,000 active saved (and not ended) activities.

Limit: 50 calls per minute for the Admin, Reporting, and bulk profile update APIs. This limit does not apply to the Delivery and single profile update APIs.

If you make more than 50 API calls per minute, Target returns a “503 HTTP status” error message.

Limit: 100 concurrent Target content delivery requests per user session.

If a customer exceeds 100 concurrent Target content delivery requests for a given user session, all subsequent requests for that user session are blocked. Two or more requests are considered to be concurrent if they are all sent to the Target server before the response is received for any of them. Target processes concurrent requests for the same session sequentially.

• Error behavior:

  • Delivery API and Batch Mbox v2:

    • Error code: HTTP 420 Too Many Requests
    • Error message: “Too many requests with same session ID”

  • Legacy mbox API:

    • Default content with comment “Too many requests with same session ID”

  • at.js:

    • Default content displayed

Limit: 50 mboxes per Target content delivery batch mbox request.

Exceeding 50 mboxes per Target content delivery batch mbox request results in a response error code HTTP 400 with error message size must be between 0 and 50.

Batch mbox requests are processed sequentially, increasing the overall response time with each iteration. The more mboxes on the batch request, the more response latency can be expected, and therefore potential for timeouts. If experience rendering is blocked on these high latency batch requests, the latency could result in a degraded user experience as users wait for experiences to render.

Limit: 60 MB HTTP POST body size for Target content delivery requests.

Exceeding 60 MB on the HTTP POST body size of a Target content delivery request results in a response error code HTTP 413 Request Entity Too Large.

Recommended limit: 50 notifications per Target delivery batch request.

Exceeding 50 notifications per Target delivery batch request likely results in increased response latency and timeouts.

Batch notification requests are processed sequentially, increasing the overall response time with each iteration. The more notifications on the batch request, the more response latency can be expected, and therefore potential for timeouts. Some additional latency on batch notification requests might be acceptable for some customers, but be aware that timeouts and any subsequent retries could cause even more latency.

Custom entity attributes: 100.

Character Limit: The maximum character length depends on the language.

• 15,000 characters (single-value, one- and two-byte languages)
• 500 values, 100 characters per value (multi-value)

The maximum length of single-value entity custom attributes is 15,000 characters (for one-byte and two-byte UTF-8 encoded languages such as English and other Latin-script alphabets) or 10,000 characters (for three-byte UTF-8 encoded languages such as Chinese, Japanese, and Korean).

Multi-value entity custom attributes can contain no more than 500 values. Each individual value is limited to 100 characters. The total number of characters across all values must conform to the limitations for the maximum length of single-value entity custom attributes (see above.)

Limit for implementations that require capturing purchase information: 50 characters.

This limit is enforced because the productPurchasedId mbox parameter captures the entity.ids, which limits the character count to 50.

Limit for implementations that require view-based algorithms only:: 1,000 characters.

View-based algorithms include view/view, most viewed, recently viewed, and so forth.

Limit: 5 KB for POST requests. 2,083 characters minus the length of the URL for GET requests.

For GET requests, although the limit on the back end is 5 KB, due to the fact that Microsoft Internet Explorer limits the URL to 2,083 characters, the realistic limit is 2,083 characters minus the current length of the URL.

Limit: 2,000 experiences per Experience Targeting (XT), A/B Test, Multivariate Test (MVT), and Auto-Target activity.

30,000 experiences per Automated Personalization (AP) activity.

Limit: 256 characters.

Values with more than 256 characters are truncated when using at.js 1.x. You receive an error message when sending values with morethan 256 characters when using at.js 2.x or the Adobe Experience Platform Web SDK. Values are not automatically truncated.

Limit: 250 characters.

For Delivery API (at.js 2.x), Batch mbox V2, and Adobe Experience Platform Web SDK (alloy.js) integrations, mbox names can contain alphanumeric characters (A-Z, a-z, 0-9) and any of the following characters:

- , . _ / = ` : ; & ! @ # $ % ^ & * ( ) _ + | ? ~ [ ] { }

For at.js 1.x integrations, mbox names cannot contain any of the following characters:

' " %22 %27 < > %3C %3E

Limit: The following limits apply to mbox parameters:

For standard mbox calls:

• mbox parameters: 500 parameters per mbox.
• Profile parameters: 500 parameters profile parameters per mbox.
• Other Parameters (URL, referring URL, etc.): 50 per mbox for each other parameter type.

These limits apply unless the request is shortened due to web browser limitations.

If you are using the Batch Delivery API, the limit is 50 mboxes per batch request.

If you are using the Batch Delivery API in the Mobile Services SDK, the limit of 50 mbox parameters, 50 profile parameters, and 50 for other parameter types are limitations of the API itself. It is not possible to send a request containing more that these numbers using the Batch Delivery API. If a request contains more than these limits, the API will return the following error message:

“The number of mboxParameters cannot exceed 50.”

Limits set for endpoints:

Batch mbox v2:

• mbox parameters 100
• mbox parameter name max length 128
• mbox parameter value cannot be null
• mbox parameter value 5000
• profile parameters 50
• profile parameter name max length 128
• profile parameter value cannot be null
• profile parameter value max length 5000

Delivery API endpoint:

• mbox parameters 100
• mbox parameter name max length 128
• mbox parameter value cannot be null
• mbox parameter value 5000
• profile parameters 50
• profile parameter name max length 128
• profile parameter value cannot be null
• profile parameter value max length 5000

Limit: 2,083 characters.

This limit is due to Microsoft Internet Explorer URL length restrictions.

Limit: 150,000 total offers.

Activity sync errors occur if the limit of 150,000 offers is exceeded.

1024 KB for HTML offers.

1024 KB (for each experience) for visual offers from the UI.

1024 KB from the API.

If you are using a global mbox, the limit is for the whole set of content returned for the page. Limiting offer size improves page load times. If the limit is exceeded, the following message appears:

“The content for the experience is too large to deliver. Please modify the experience to affect less page code.”

Recommended limit of active profile scripts (those that are enabled): 300

Recommended limit of total profile scripts per account: 2,000

Recommendations for limiting profile script complexity: Profile scripts can execute a limited number of instructions. For more information, see Best practices in Profile attributes.

Recommended limit: 2,000 characters.

Depends on the size of the encoded string, which could be much longer than the raw string. If the string is too large, it fails before it gets to Adobe Target.

Limit: 2,048 characters.

For performance reasons, we recommend a return value that is no longer than 256 characters.

For a String return value, if the size of the return value exceeds 2,048 characters, the script is disabled by the system.

For an array return value, if the size of the concatenated values of the array exceeds 2,048 characters, the script is disabled by the system.

Recommended limit: 1,000 values.

This refers to the number of line-separated values in the targeting text area. For example, entering 1,000 zip codes into a zip code target.