Vistor profile persistent issue | Community
Skip to main content
Ashok_Adiyolil
Ashok_Adiyolil
Level 2
October 29, 2020
Solved

Vistor profile persistent issue

  • October 29, 2020
  • 1 reply
  • 1562 views

Hi experts,


I have created audience using vistor profile. Which will get the input from target profile parameters which is passed via launch target page load rule, order of execution are maintained. Even though everything is perfect I'm facing inconsistency in content delivery.
My scenario is to capture audience who is logged in at least one time. If user logged in one time then this profile will be under logged in user. For more some time I got activity working if I refresh activity content not delivering.
I hope problem would be in vistor profile they're not persist users I believe.
Any solution?

 

Thanks

    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 zach_shearer

    Have you used the mBoxtrace debugging method to ensure that the profile parameter is set when a user logs in at least once? Then, when the user comes back, does the profile parameter still exist? 

     

     https://docs.adobe.com/content/help/en/target/using/activities/troubleshoot-activities/content-trouble.html#section_256FCF7C14BB435BA2C68049EF0BA99E

    1 reply

    zach_shearer
    zach_shearerAccepted solution
    Level 4
    November 2, 2020

    Have you used the mBoxtrace debugging method to ensure that the profile parameter is set when a user logs in at least once? Then, when the user comes back, does the profile parameter still exist? 

     

     https://docs.adobe.com/content/help/en/target/using/activities/troubleshoot-activities/content-trouble.html#section_256FCF7C14BB435BA2C68049EF0BA99E

      Ashok_Adiyolil
      Ashok_AdiyolilAuthor
      Level 2
      November 4, 2020

      @zach_shearerAppreciation your response.Visitor

      Profile persistent issue - We have found the reason for this issue it's due to unavailability of the data element when target loading a rule to pass parameters. so it was fixed by splitting the rule one by load target and another one is to send Page load request.

      But we are facing another issue - We have created orderconfirm mbox to send the order details value to the target.

      When we try to execute the orderconfirm mbox code on thankyou page i'm able to see the parameters passed but those parameters are not picked up by profile scripts.

       

      Mbox code used:

      adobe.target.trackEvent({

      "mbox": "or",

      "params": {

      "param1": "value1"

      } });

       

      Profile script :

      if (mbox.name == ‘orderConfirmPage’) {

      return (parseInt(mbox.param(‘param1’));

      }

       

      Please share your thoughts on this.

      Thanks

      Terms & ConditionsAccessibility statement

      Loading footer...