rubenv70221477
Here is a summary of some of the things that have been mentioned in this thread along with some additional details:
Is there a technical difference between Inactive and Archived in terms of fired server calls?
In terms of fired server calls no difference. If you have target deployed on a page it will fire 1 server call to Adobe every time the page is loaded irrespective of how many activities you have loaded on the page. Unless you have custom mboxes but even then lets say you have 2 custom mboxes there will always be 2 calls that fire on the page irrespective of how many activities you have in active or inactive state.
And if so, would you advice me to archive all my tests? Currently all ended tests are still in Inactive mode.
Yes I woudl but not because of performance on the site. Rather because of performance with QA URLs. When you attempt to use a QA URL the system checks against a list of activities. Because it's possible to want to QA an activity with state: Active or Inactive but not possible to QA an activity that has been archived. I've seen accounts that haven't archived in such a long time that this starts causing issues with content not displaying for QA URls simply becuase there are so many inactive activities to check.
If this satisfies your query please like, mark as helpful and mark as answer. Otherwise lets keep the conversation going. Hope you have a wonderful day.
Mihnea Docea | Technical Support Consultant | Customer Experience | Adobe | (:: 1 (800) 497-0335
