Expand my Community achievements bar.

SOLVED

AJO Email journey creates a Campaign as well

Avatar

Level 2

Hi,

I recently have noted (mainly after Feb 19 2025) in AJO that if we create a AJO email journey and publish it then another campaign also gets created (like a email campaign with same email HTML) which is not visible in campaign browse list in the UI we have to check the contact history using the profile ID in the journey and campaign datasets.

The email gets sent out only single time from the journey.

 

Has anyone also faced similar issue.

Is it a feature that Adobe has enabled.

How do I stop it from happening.

 

Any help would be appreciated as it skews the reporting based on the profiles.

Topics

Topics help categorize Community content and increase your ability to discover relevant content.

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

Hi @mohit_khare,

 

It's not an issue. It's an Adobe backend process which create a read only campaign using the channel as prefix.

As a reminder, ajo_entity_dataset purpose is to store entity metadata for messages sent to the end user.

An entry for a message is created only after journey or campaign is published. You may see the entry 30 minutes after the publication of the campaign/journey.

 

If it's impacting the OOTB reporting, then you can open a ticket with Adobe Support. If it's a custom reporting, then you need to adjust the criteria to not include them

 

Thanks,

David



David Kangni

View solution in original post

4 Replies

Avatar

Level 1

Hi Mohit, Last week I created a couple of journeys and didn't face any campaign creation. Please let  know if you are facing the issue still.

Avatar

Level 2

Hi @jerlinlourds,

Thanks for getting back.

The campaign i am talking about is not visible in the Campaign list UI. You cant even search by this campaign name.

You will have do something like this:

1) use a query like this:
SELECT
_experience.customerJourneyManagement.entities.campaign.campaignVersionID,
_experience.customerJourneyManagement.entities.campaign.name
FROM
ajo_entity_dataset
WHERE
_experience.customerJourneyManagement.entities.campaign.name ILIKE 'email-%'

mohitkhare123_0-1742807099642.png

 

2) Open a random campaign and replace the campaign version ID you got from the query result in the address bar to open the auto generated campaign.

mohitkhare123_1-1742807153225.png

 

 

It opens the campaign with the same email being used in the journey and has the same count as well (PS the journey should have sent email to profiles in actual).

 

Please let me know if you see the same in your instance.
You could also use a query like this:
SELECT
_experience.customerJourneyManagement.entities.campaign.campaignVersionID,
_experience.customerJourneyManagement.entities.campaign.name,
_experience.customerJourneyManagement.entities.journey.journeyName,
_experience.customerJourneyManagement.entities.timestamp.lastModifiedAt
FROM
ajo_entity_dataset
WHERE
_experience.customerJourneyManagement.entities.campaign.name ILIKE 'email-%'
order by
_experience.customerJourneyManagement.entities.timestamp.lastModifiedAt DESC

 

May be its something that we did in out instance that creates the campaigns automatically.

Based on you answer i will get in touch with Adobe.

Avatar

Administrator

Hi @mohit_khare,

Were you able to resolve this query with the help of Adobe support or was this something you were able to figure out on your own or do you still need help here? Do let us know.

Thanks!



Sukrity Wadhwa

Avatar

Correct answer by
Community Advisor

Hi @mohit_khare,

 

It's not an issue. It's an Adobe backend process which create a read only campaign using the channel as prefix.

As a reminder, ajo_entity_dataset purpose is to store entity metadata for messages sent to the end user.

An entry for a message is created only after journey or campaign is published. You may see the entry 30 minutes after the publication of the campaign/journey.

 

If it's impacting the OOTB reporting, then you can open a ticket with Adobe Support. If it's a custom reporting, then you need to adjust the criteria to not include them

 

Thanks,

David



David Kangni