Hi Darren,Sounds like you are using the adobe experience cloud to login. If the company you are working for hasn't turned off the legacy login method, you can always go to sc.omniture.com, type in your company details, username and password. That way you can retrieve all your "old" reports. However,...

Hi there, the above is not possible as adobe analytics (and other analytics tools) rely on calculating the time based on calls made to server, so if the user came to website and left again, without you sending additional information to Adobe Analytics, this will be considered a bounce and no time is...

Hi there,Have a look at this article. Hit Depth  You will most likely need to use hit depth because you are looking at getting pages per visit. The article explains things quite well. /Waqas

In general, any calls you see in your network tab under "b/ss" is considered a primary server call. Adobe doesn't distinguish between primary and secondary server calls any longer. Assuming you have Adobe Analytics on all your domains, I would strongly recommend that you get this plugin:https://mark...

Hi there, In your case, it will cost you a server call for each event you are sending. The best approach is to send data on the next page to limit the amount of servercalls. The approach you are using is most commonly used in GA implementations but in an Adobe world, this costs you extra money, so n...

Hi Martin,Just came to think of one thing. If you expire your evar on hit, then you can associate any success events with the eVar after. So might be better to go with option 2. /Waqas

Hi Martin,I would use the processing rules and just set the value to "NULL" in the case information is not available. That way you can over time see when the fix has been applied. But as I see it, both of your options should work. Setting the eVar to expire on hit should work perfectly fine as well....

Is the company going to continue using metrics.mydomain.com and smetrics.mydomain.com? If yes, then I would recommend to change your appmeasurement code to the following:s_account = "reportsuiteid" //assuming these are the same across both codess.visitorNamespace = "" //should be the same for both c...

That means the code is working as it should. If you click start application and the event fires, that should be associated with that specific campaign now, without you having to set s.campaign again. And that's not the case at the moment?

Do you mind opening the browser console, going to network tab, filter for "b/ss" and then put in the url with your domain and a random assigned cid, like the example here: YOURDOMAIN.COM?cid=adobeforumtestYou should see the variable V0 being set on the first request to the adobe analytics servers. D...