I don’t think I’m using tags properly, or perhaps Pro Reports is not using them the way I think it should.
I have a bunch of sites and I tag them in two main ways. One tag is a plan level; simple, basic, advanced, pro, etc. Every site falls into one of these and so every site has at least this tag.
I add another tag whenever there is an agency owner or client that has multiple sites, so I can group that client’s sites. E.g. agency1, agency2, client1.
Next, I have multiple templates for the reports. Basic plans have a generic report, and then I may have a Basic plan from agency1 that has a separate report template just for them.
Now to my question.
When I want to bulk export the reports, I need to select them based on having a tag, or lack of having a tag, or containing BOTH tags etc.
If I choose the Basic generic report, I need to print all the tags “Basic” but NOT agency1 or others since they have different templates.
If I want to print Basic agency1 with their custom template, I need to make sure it’s not printing Basic tags that don’t also have agency1.
My problem is, the tagging system seems to work additively. If I select Basic tag and agency1 tag, it prints ALL basic and ALL agency1, rather than printing sites that only have BOTH tags.
Further, since there is no negation, I simply have no way to print Basic tags without it also grabbing every other tag with it.
The bottom line is that it seems like I can’t even use tags at all. I end up having to select every site one by one to make sure they match the right custom template.
I think the logic needs to change in some way so that we can filter tags with more precision and options. E.g. “Has TAG1 and TAG2 and NOT TAG3”. Or “Has ONLY TAG1 and TAG3”. Or “ANY tag EXCEPT TAG1 OR TAG5”. You get the idea. We need a kind of logic builder experience; AND/OR/NOT/ALL/EXCEPT etc.
The only way I can see to do this in the current system is to create tags specific to templates rather than tags specific to business categories and sites or clients. Custom Template 5 matches tag “template5” or whatever. But having the better conditions builder would be much more useful.