Guardrails for activation data

This page provides default usage and rate limits with regard to activation behavior. When reviewing the following guardrails, it is assumed that you have correctly connected to destinations.

NOTE
  • Most customers do not exceed these default limits. If you would like to learn about custom limits, please contact your customer care representative.
  • The limits outlined in this document are constantly being improved. Please check back regularly for updates.
  • Depending on individual downstream limitations, some destinations might have tighter guardrails than the ones documented on this page. Make sure to also check the catalog page of the destination you are connecting and activating data to.

Limit types

There are two types of default limits within this document:

  • Soft limit: It is possible to go beyond a soft limit, however soft limits provide a recommended guideline for system performance.
  • Hard limit: A hard limit provides an absolute maximum. The Experience Platform UI or API does not allow you to go beyond this limit, or an error is returned if you go beyond this limit.

Activation limits

The following guardrails provide recommended limits when activating Real-Time Customer Profile data to destinations.

General activation guardrails

The guardrails below generally apply to activation through all destination types.

Guardrail Limit Limit Type Description
Maximum number of segments to a single destination 250 Soft The recommendation is to map a maximum of 250 segments to a single destination in a dataflow.

If you need to activate more than 250 segments to a destination, you can either:
  • Unmap segments that you don’t want to activate anymore, or
  • Create a new dataflow to the desired destination and map segments to this new dataflow.

Note that in the case of some destinations, you may be limited to fewer than 250 segments mapped to the destination. Those destinations are called out further below on the page, in their respective sections.
Maximum number of destinations 100 Soft The recommendation is to create a maximum of 100 destinations that you can connect and activate data to per sandbox. Edge personalization destinations (Custom personalization) can make up a maximum of 10 of the 100 recommended destinations.
Maximum number of attributes mapped to a destination 50 Soft In the case of several destinations and destination types, you can select profile attributes and identities to map for export. For optimal performance, a maximum of 50 attributes should be mapped in a dataflow to a destination.
Type of data activated to destinations Profile data, including identities and identity map Hard Currently, it is only possible to export profile record attributes to destinations. XDM attributes that describe event data are not supported for export at this time.
Type of data activated to destinations - array and map attributes support Not available Hard At this time, it is not possible to export array or map attributes to destinations. The exception to this rule is the identity map, which gets exported in both streaming and file-based activations.

Streaming activation

The guardrails below apply to activation through streaming destinations.

Guardrail Limit Limit Type Description
Number of activations (HTTP messages with profile exports) per second N/A - There is currently no limit to the number of messages per second sent from Experience Platform to partner destinations’ API endpoints.
Any limits or latencies are dictated by the endpoint where Experience Platform is sending data. Make sure to also check the catalog page of the destination you are connecting and activating data to.

Batch (file-based) activation

The guardrails below apply to activation through batch (file-based) destinations.

Guardrail Limit Limit Type Description
Activation frequency One daily full export or more frequent incremental exports every 3, 6, 8, or 12 hours. Hard Read the export full files and export incremental files documentation sections for more information about the frequency increments for batch exports.
Maximum number of segments that can pe exported at a given hour 100 Soft The recommendation is to add a maximum of 100 segments to batch destination dataflows.
Maximum number of rows (records) per file to activate 5 million Hard Adobe Experience Platform automatically splits the exported files at 5 million records (rows) per file. Each row represents one profile. Split file names are appended with a number that indicates the file is part of a larger export, as such: filename.csv, filename_2.csv, filename_3.csv. For more information, read the scheduling section of the activate batch destinations tutorial.

Ad-hoc activation

The guardrails below apply to the ad-hoc activation method.

Guardrail Limit Limit Type Description
Segments activated per ad-hoc activation job 80 Hard Currently, each ad-hoc activation job can activate up to 80 segments. Attempting to activate more than 80 segments per job will cause the job to fail. This behavior is subject to change in future releases.
Concurrent ad-hoc activation jobs per segment 1 Hard Do not run more than one concurrent ad-hoc activation job per segment.

Edge personalization destinations activation

The guardrails below apply to activation through edge personalization destinations.

Guardrail Limit Limit Type Description
Maximum number of Custom personalization destinations 10 Soft You can set up dataflows to 10 Custom personalization destinations per sandbox.
Maximum number of attributes mapped to a personalization destination per sandbox 20 Hard A maximum of 20 attributes can be mapped in a dataflow to a personalization destination, per sandbox.
Maximum number of segments mapped to a single Adobe Target destination 50 Soft You can activate a maximum of 50 segments in an activation flow to a single Adobe Target destination.

Destination SDK guardrails

Destination SDK is a suite of configuration APIs that allow you to configure destination integration patterns for Experience Platform to deliver audience and profile data to your endpoint, based on data and authentication formats of your choice. The guardrails below apply to the destinations you configure using Destination SDK.

Guardrail Limit Limit Type Description
Maximum number of private custom destinations 5 Soft You can create a maximum of 5 private custom streaming or batch destinations using Destination SDK. Reach out to a custom care representative if you need to create more than 5 such destinations.
Profile export policy for Destination SDK
  • maxBatchAgeInSecs (minimum 1.800 and maximum 3.600)
  • maxNumEventsInBatch (minimum 1.000, maximum 10.000)
Hard When using the configurable aggregation option for your destination, be mindful of the minimum and maximum values that determine how often HTTP messages are sent to your API-based destination and how many profiles the messages should include.

Destination throttling and retry policy

Details on throttling thresholds or limitations for given destinations. This section also provides information regarding the retry policy for destinations.

Type of destination Description
Enterprise destinations (HTTP API, Amazon Kinesis, Azure EventHubs) In 95 percent of the time, Experience Platform attempts to offer a throughput latency of less than 10 minutes for successfully sent messages with a rate of less than 10 thousand requests per second for each dataflow to an enterprise destination.
In case of failed requests to your enterprise destination, Experience Platform stores the failed requests and retries twice to send the requests to your endpoint.

Guardrails for other Experience Platform services

View guardrails information for other Experience Platform services:

On this page