By default they wouldn't persist but you can modify that behavior.  The code below creates a window scoped variable.  You can update the code with the additional tokens you want and then push the value to local storage or do the data layer document.addEventListener(adobe.target.event.REQUEST_SUCCEED...

I imagine the variables you want to use are available in the dataLayer, cookie, or Local Storage.   Once you know where that data is, you would need to update Launch (assuming Target is managed there) and tell Adobe Target to use the data you identified in the server-call.   

I misread the question and jumped the gun on content rules!  Apologies.  What Ryan said!  

Create a profile that increments with clicks and use that in your audience.  This will help: https://www.miaprova.com/blog/offer-impression-capping/

You can't use the 'target-global-mbox' name server-side.  That mbox name is special and reserved for client-side use.  Best to use a different name but to answer your question, you can consolidate all offers into a single mbox, just like you can client-side.   

Pass the publish date or event date as an mbox parameter to the Target server call.  Then use that in your Audience criteria 

You probably are grabbing the incorrect selector to track clicks.  You will be so much better off, for many reasons, to track clicks when the visitor LANDS on the page that the click brings them to.  Add a special URL parameter to the links being used (for example, www.link.com/?s=1) where s=1 means...

Yep yep...excited to geek out on CDP and Target!  

In AP, you can set rules in the set up to coordinate what can and can't show with each other.    

Question 1:  You can access DOM elements with javascript, jquery or CSS.  There is nothing special you need to do.  Here is an example of DOM manipulating code here;https://www.miaprova.com/blog/adobe-target-technical-interview-questions/ Question 2:  Adobe Target is a 1st Party Cookie solution and ...