Are you talking about on an author instance or publish instance (which I assumed)?If you are trying to maintain a session across multiple publish instances, typically you allow the Dispatcher module to handle it. The Dispatcher's configuration allows you to enabled sticky sessions. That means it will ensure that each user is routed to the same AEM instance until his/her session expires, ensuring that your JSESSIONID problem doesn't exist. Are you using the dispatcher for load balancing and stick...

Yogesh,Do you ever run into issues where reverse replicating Impressions in this manner causes data loss for high-traffic sites? It seems that, even if your reverse replication processes run every few seconds, your three instances (two publish) may step on each other a bit. Just curious.By the way, the better approach is definitely to use a dedicated web analytics platform for measurement. Though there is some use in having the up-to-date page impressions in context within AEM.

Thanks Anna!

I don't have an API key on that page; just my name, title, phone number, email address, time zone, and password. Could there be some kind of permission or upgrade issue with our DTM account?

No problem. I figured you probably couldn't answer anyway. Thanks for the quick response all the same.

Paul, I was curious if you were aware of Adobe's plans for this functionality moving forward. It seems to me like there would be a lot of value to allow interactive PDFs to interact with an Adobe model in the same respect as with an XSD. I understand that there are probably technical limitations, though admit that I don't have a clear understanding of what those are. Assuming it is possible, do you know whether Adobe has that functionality on the horizon...perhaps in ES3?