Hi @henrikk My understanding is that you have an A/B test running - at some point you need to change the content of variant B. This needs to happen at a certain day and time - up until this day and time, you still want the 'original' content of variant B to show up until this time. Is that correct u...

@alexthomos22 my understanding is that you have the scenario of a user visiting the site where Target is delivering content. At some point the visitor decides to withdraw consent and you would therefore like to have Target stop delivering content, but without reloading/refreshing the page. Is that c...

Hi @alexthomos22    You can replicate the mboxDisable ( https://experienceleague.adobe.com/en/docs/target/using/activities/troubleshoot-activities/content-trouble ) parameter into a cookie.    From the browser console you can run: document.cookie = "mboxDisable=1; path=/";   You could trigger the sa...

@pradeep_joshi20 tntidtntid is not visible in the first request in the debugger. This is expected as @Vaibhav_Mathur correctly describes. I see the same behaviour across the sites I'm supporting with Target. I would evaluate this to be working as expected.mbox3rdpartyidIf you click on the action in ...

Hi @todd1066    I believe it is the nature of the QA links that you only see the activity the QA links are relevant to.  As an alternative I would apply a QA audience and publish the activity live, while the XT also is live. And validate it that way.    See my description here: https://experiencelea...

@pradeep_joshi20 wrote: @kandersen we are setting mbox3rdpartyid by using Adobe Target v2 Launch extension -> Add Params to All Requests.  But you're not hardcoding it in the extension, right? So you're most likely setting a data element in the extension. And the question is then, where is the data...

Where is mbox3rdpartyid being set from? I assume datalayer > into data element ? Could there be a timing issue with datalayer not beign set until after Target script has executed?

Hi @PrabhatSharma    The correct duration is 2 years and AFAIK it is not possible to change the duration of the cookie.  Kind regards, Kasper

Hi @PrabhatSharma ,   prads is spot on.   The at_geo cookie is set when on-device decisioning is enabled.  During on-device decisioning, when Target initially retrieve the artifact from the Akamai CDN, it also retrieve the user's geo location in the headers. Adobe then create a dedicated cookie cal...

Hey @SoufianeLa Are you making any progress with the TargetTrace debugging?