Skip to main content
B
Bansari
Level 2
June 2, 2026
Question

Namespace Change in API Triggered Campaign

  • June 2, 2026
  • 1 reply
  • 13 views

We have an ongoing requirement where API triggered campaign will be triggered from CDS source system when they make the API call. The namespace we are using is EID - which is the profile identifier for the existing users within company’s system. Now, we need to integrate another namespace which will be non-profile identifier for new first-time users which are not present in the source system. The source system integration with AJO API triggered campaign is based on campaignID value which is unique per campaign. Now, we cannot add 2 namespaces within same campaign and creating multiple campaign versions based on namespace is not a viable solution. 

Is there any way we can accommodate the requirement of non-profile identifier and profile identifier both within same campaign? As the campaigns will be relevant for new & existing users both. Another caveat is that in AJO we cannot store the JSON data for API triggered campaigns, only the event-based data will be available in profile store.

 

Please do guide on how we can take this ahead within AJO itself, whether this will be possible or not.

1 reply

Anuhya-Y
Community Advisor
Anuhya-YCommunity Advisor
Community Advisor
June 2, 2026

​@Bansari 

For API Triggered Campaigns, a single campaign can only be configured with one profile namespace for audience resolution. Therefore, using two different identifiers (e.g., an existing profile identifier such as EID and a separate identifier) within the same campaign execution is not supported.

The campaign relies on the configured namespace to recognize the incoming user and resolve the profile . If the incoming identifier cannot be resolved to a profile, the unknow profiles will be rejected.

If your requirement is to engage first-time users who do not yet exist in AEP, Adobe Journey Optimizer provides an option to automatically create profiles at campaign execution time. When this option is enabled, AEP can create a new profile based on the incoming identity and proceed with the delivery. If it is not enabled, requests for unknown profiles will be rejected and no delivery will occur.

Reference:
https://experienceleague.adobe.com/en/docs/journey-optimizer/using/campaigns/api-triggered-campaigns/api-triggered-campaign-audience#activate-profile-creation-at-campaign-execution

Based on the current AJO capabilities, engaging users through the same API-triggered campaign using two different namespaces/identifiers is not supported.

Terms & ConditionsAccessibility statement

Loading footer...