AJO Campaign throwing error in Review to Activate Page | Community
Skip to main content
S
SR10
New Participant
June 29, 2023
Solved

AJO Campaign throwing error in Review to Activate Page

  • June 29, 2023
  • 2 replies
  • 1597 views

Hi All,

While trying to create a transactional campaign in adobe journey optimizer, I am getting the below error

 

"The referenced campaign audience type is not allowed for the provisioned channels".

 

I am using

Email as channel and Email as identity for campaign configuration.

 

PFB the screenshot

Could anyone suggest the solution or root cause of this issue?

 

Thanks in advance

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by SR10

Hi @sukrity_wadhwa ,

 

We are not facing the issue currently. Might be a temporary issue.

2 replies

Sukrity_Wadhwa
Sukrity_Wadhwa
Employee
July 7, 2023

Hi @sr10,

Were you able to resolve this query with the help of support? Do let us know your experience and the solution that came out.
Thanks!

Sukrity Wadhwa
S
SR10AuthorAccepted solution
New Participant
July 8, 2023

Hi @sukrity_wadhwa ,

 

We are not facing the issue currently. Might be a temporary issue.

    SatheeskannaK
    SatheeskannaK
    New Participant
    June 29, 2023

    @sr10, Can you verify channel surface has the email type selected as Transactional that you're using in the transactional campaign?

     

    Thanks, Sathees
    S
    SR10Author
    New Participant
    June 29, 2023

    Hi @satheeskannak ,

     

    Yes it is Email.

    PFB screenshot for your reference.

     

     

    I am able to use the same channel surface for email action in journeys. I am not facing any errors there and email is getting delivered successfully.

    But for campaigns, I am getting this error.

    SatheeskannaK
    SatheeskannaK
    New Participant
    June 29, 2023

    @sr10, I can reproduce the issue. In fact, the last time when I was testing it was working. Now it's not. Can you open a support ticket on this issue?

    Thanks, Sathees
      Terms & ConditionsAccessibility statement

      Loading footer...