Capping logic inconsistencies across placements in AEP offer decisioning
This article addresses an issue in Adobe Experience Platform’s Offer Decisioning feature, where the capping logic behaves inconsistently between 1:1 message and email placements. To resolve the issue, use the correct namespace case in the IMS Org.
Description description
Environment
Adobe Experience Platform
Issue/Symptoms
When offers are configured with a daily capping limit of two decisions, the system should cap the offer after two decisions—regardless of placement—and display the next offer based on priority. However:
- Email placements ignore the capping logic and continue to show high-priority offers beyond the cap.
- 1:1 message placements enforce the cap correctly and display the next eligible offer as expected.
Cause
The issue is caused by case sensitivity in the identity namespace used during decision event processing. Specifically:
- The IMS Org is configured with the namespace “MyNamespace” (with uppercase “M” and “N”).
- Using “MyNamespace” works correctly and enforces capping as expected.
- Using “mynamespace” (all lowercase) leads to inconsistent behavior, especially in email placements.
Resolution resolution
- Ensure that the identity namespace in payloads exactly matches the allowed list for your IMS Org, using the correct case (for example, “MyNamespace”) in all calls to avoid inconsistencies.
- Modify payloads to include the correct case-sensitive namespace value (“MyNamespace”). For example:
{` "xdm:identityMap": {`"MyNamespace": [` {`"xdm:id": "<profile_id>"` }`]` }`} - Test both 1:1 message and email placements to confirm consistent capping behavior, and verify that decision events are correctly recorded in datasets and align with the configured caps.
- Monitor datasets such as ODE DecisionEvents to ensure decision events are logged accurately, and verify that profile-level counts increment correctly based on the configured caps.
If the issue persists after correcting the namespace values, escalate to Adobe Support with detailed information, including the offer name or ID, campaign name or ID, and the profile ID along with the associated namespace.