Join us on September 25th for a must-attend webinar featuring Adobe Experience Maker winner Anish Raul. Discover how leading enterprises are adopting AI into their workflows securely, responsibly, and at scale.
SOLVED
API Triggered Campaigns: Evaluation Scenarios
1 Accepted Solution
Correct answer by
1) Are there any implications if we try to trigger or create more number of new profiles than expected as mentioned in the documentation?
The “create new profiles” option was designed for edge cases (e.g. a small set of unknown records for a transactional message).
If you rely on it for bulk profile creation profile store may get bloated, Processing latency increases, since each API call has to create + validate the profile record before sending.
You may lose data integrity, since profile governance (consent, deduplication, enrichment) works best when profiles come in through standard ingestion pipelines (batch ingestion, RTCDP, streaming connectors).
Some downstream capabilities (segmentation, profile merges, suppression) may behave unexpectedly if profiles are being created ad hoc in huge numbers.
2) Will it affect the overall licensing, if we try to ingest more number of new profiles?
Yes — profile creation does affect licensing.
AJO licensing is tied to addressable audience. Take a look at the entitlements tied to the packages. https://helpx.adobe.com/legal/product-descriptions/adobe-journey-optimizer.html
If your transactional sends keep creating new unique profiles (instead of referencing existing ones), each one will consume the quota.
So, if you unintentionally create a large number of new profiles, it can push you over license thresholds.
3) What qualifies as a "very small volume" profile creation in this context? Are we talking about a specific number or percentage of total profiles?
Adobe hasn’t published an exact number. I believe “Very small” usually means edge-case profiles in the tens or hundreds per day, not thousands, depending on the package licensed.
For example, Event confirmations → guest users who don’t exist in the master database
If you’re talking hundreds of thousands or millions of new profiles created via API — that’s not supported, and you’ll almost certainly run into licensing + performance concerns.
4) Are there any performance or scalability concerns when sending large volumes of transactional emails? Especially when new profiles are being created on the fly.
When you add new profile creation on the fly, each send requires a write operation into the AEP profile store (not just a message dispatch). This introduces latency (slower API response times).
At a very high scale, this may create backlogs in ingestion, and your sends could lag behind your API requests.
For large-volume transactional sends, all profiles should exist ahead of time in AEP. Only use the “create on the fly” flag for rare or incidental cases.
- Recommendation is to pre-ingest known profiles (via batch, RTCDP, streaming connectors) before transactional use.
- Use API-triggered campaigns with profile creation only for exceptions, not the main pipeline.
- Monitor your addressable audience in AEP to ensure you’re not creeping past license thresholds.
- Creating too many new profiles this way can hurt performance and licensing.
Thanks, Sathees
Correct answer by
1) Are there any implications if we try to trigger or create more number of new profiles than expected as mentioned in the documentation?
The “create new profiles” option was designed for edge cases (e.g. a small set of unknown records for a transactional message).
If you rely on it for bulk profile creation profile store may get bloated, Processing latency increases, since each API call has to create + validate the profile record before sending.
You may lose data integrity, since profile governance (consent, deduplication, enrichment) works best when profiles come in through standard ingestion pipelines (batch ingestion, RTCDP, streaming connectors).
Some downstream capabilities (segmentation, profile merges, suppression) may behave unexpectedly if profiles are being created ad hoc in huge numbers.
2) Will it affect the overall licensing, if we try to ingest more number of new profiles?
Yes — profile creation does affect licensing.
AJO licensing is tied to addressable audience. Take a look at the entitlements tied to the packages. https://helpx.adobe.com/legal/product-descriptions/adobe-journey-optimizer.html
If your transactional sends keep creating new unique profiles (instead of referencing existing ones), each one will consume the quota.
So, if you unintentionally create a large number of new profiles, it can push you over license thresholds.
3) What qualifies as a "very small volume" profile creation in this context? Are we talking about a specific number or percentage of total profiles?
Adobe hasn’t published an exact number. I believe “Very small” usually means edge-case profiles in the tens or hundreds per day, not thousands, depending on the package licensed.
For example, Event confirmations → guest users who don’t exist in the master database
If you’re talking hundreds of thousands or millions of new profiles created via API — that’s not supported, and you’ll almost certainly run into licensing + performance concerns.
4) Are there any performance or scalability concerns when sending large volumes of transactional emails? Especially when new profiles are being created on the fly.
When you add new profile creation on the fly, each send requires a write operation into the AEP profile store (not just a message dispatch). This introduces latency (slower API response times).
At a very high scale, this may create backlogs in ingestion, and your sends could lag behind your API requests.
For large-volume transactional sends, all profiles should exist ahead of time in AEP. Only use the “create on the fly” flag for rare or incidental cases.
- Recommendation is to pre-ingest known profiles (via batch, RTCDP, streaming connectors) before transactional use.
- Use API-triggered campaigns with profile creation only for exceptions, not the main pipeline.
- Monitor your addressable audience in AEP to ensure you’re not creeping past license thresholds.
- Creating too many new profiles this way can hurt performance and licensing.
Thanks, Sathees
@Silvio6 Yes. The option to create new profiles may create some delays. Additionally, it is influenced by the number of requests being sent and how many of those are for new profiles. Be sure to check the entitlements and SLA that are associated with the AJO package.
https://helpx.adobe.com/legal/product-descriptions/adobe-journey-optimizer.html
Thanks, Sathees
Related Conversations
