I was wondering if there was a way you’re able to limit analytics to a profile, as in, say you’ve created a profile named ‘microsite’, and this profile limits results according to a padre_opts.cfg gscope.
You’re able to view scoped down Accessibility Auditor and Content Auditor results, but analytics will remain empty as analytics I believe are profile specific, as people will never search against the ‘microsite’ profile, only against the ‘_default’ profile.
Is there a way to configure profiles to source analytics from the _default profile?
If I’m completely wrong about this, please respond in a series of emojis.
If you’re doing a search for the microsite you should use the microsite profile then everything will match up. When you run a search it’s analytics is logged against whatever profile is being queried (ie. whatever the profile parameter is set to in the query). If you’re searching the microsite using the _default profile and scoping that down when you make the query then the analytics are treated as part of the _default profile.
I see what you’re getting at. The case for setting up a profile here is more internal / organizational, the client would like for the profile to provide users with access to a subset of analytics, AA reporting, and Content Auditor reporting only relevant to the users department.
I’ll follow up with a feature request internally, cheers mate.
By all means raise a feature request - but I think it will be pretty much impossible to achieve this for the analytics. AA and CA already should work ok.