Inconsistent activity delivery in the experience targ...

[Knowledgeseeker98]

Hi Experts,

I have an issue in delivering activity when I created few experiences in target.

In my scenario ,the activities are inconsistent in the delivery. When the user logged we will be displaying recommendation in the home page. But it is inconsistent and sometimes it will delivery.

What would be the reason?

Can anyone help on this?

[surebee · Accepted solution]

Hi @Knowledgeseeker98,

Thanks for reaching out!

There could be several reasons why there is inconsistent content delivery- how are you authenticating a user? What is the use case? Are you using mbox3rdPartyId? How is the audience set up?

Is a logged in user meeting the audience condition? Are there any error messages displayed on the console when you append ?mboxDebug=1 to the URL you are testing on?

I invite you to try the debug tools outlined here to see if that leads to some answers: https://docs.adobe.com/content/help/en/target/using/activities/troubleshoot-activities/content-troub...

Please feel free to open a Client Care ticket with us by emailing customercare@adobe.com as well so we can take a closer look. Hope this helps!

[Knowledgeseeker98]

Appreciating your response.

Answers to your question

Authenticating a user? - Normal password authentication methods used in AEM

What is the use case? - We have to deliver a personalized content to the logged in user. Aim is to Identify Guest purchasers.

How we construct this ? and Is a logged in user meeting the audience condition? - We capture user id in a data element and then it is mapped with profile parameter "profile.login" Once the parameter is passed to the profile.login we use them into vistor profile- with the following condition if parameter value present then bucket those user as logged in user. ignore if it empty(when unauthenticated)

Are you using mbox3rdPartyId? How is the audience set up? - No we are not setting this mbox3rdPartyId, Does it required? if yes can you please guide with exact steps. Are there any error messages displayed on the console when you append ?mboxDebug=1 to the URL you are testing on? yes we are getting following error AT:[page-init] Adobe Target content delivery is disabled. Ensure that you can save cookies to your current domain, there is no "mboxDisable" cookie and there is no "mboxDisable" parameter in query string. but we have validated there is no mboxdisable in cookie and URL. Still notsure why this is coming

[Knowledgeseeker98]

Appreciating your response @surebee 

Answers to your question
Authenticating a user? - Normal password authentication methods used in AEM

What is the use case? - We have to deliver a personalized content to the logged in user. Aim is to Identify Guest purchasers.

How we construct this ? and Is a logged in user meeting the audience condition? - We capture user id in a data element and then it is mapped with profile parameter "profile.login"
Once the parameter is passed to the profile.login we use them into vistor profile- with the following condition if parameter value present then bucket those user as logged in user. ignore if it empty(when unauthenticated)

Are you using mbox3rdPartyId? How is the audience set up? - No we are not setting this mbox3rdPartyId, Does it required? if yes can you please guide with exact steps.

Are there any error messages displayed on the console when you append ?mboxDebug=1 to the URL you are testing on? yes we are getting following error

AT:[page-init] Adobe Target content delivery is disabled. Ensure that you can save cookies to your current domain, there is no "mboxDisable" cookie and there is no "mboxDisable" parameter in query string.
but we have validated there is no mboxdisable in cookie and URL. Still not sure why this is coming.

Your response will be appreciated.

Thanks

[surebee]

Hi @Knowledgeseeker98, thank you for the note. Do you have a URL and test credentials I could take a look at? It would help understand your use case better. Thanks!

[karandhawan]

@Knowledgeseeker98 You can troubleshoot the delivery using mboxTrace. Trace information reflects the outcome of a Target call and any additional data that may help in determining why this particular outcome happened, such as a set of available branches among which the selection was made in a campaign. 

https://experienceleague.adobe.com/docs/target/using/activities/troubleshoot-activities/content-trou...

Regards,

Karan