Hi @at9191
assuming you're talking about Launch rules?
There is no log on the server about the location, but you can easily enable it on the individual browser console for the individual page.
- _satellite.setDebug(true)
- filter the logs for "fired"
- apply more conditions to the filter if needed
- if a rule fired more than once in a row, you will see a numer before the ruls in the log

If you need more specific logging / tracking, this could potentially (haven't done it myself) be done through a list variable in Adobe Analytics. List var because each individual name can be 255 Bytes long
But this comes with a couple of preconditions
- each executed rule has to register itself into your Launch property e.g. in a window scoped array variable when it is executed
- Adobe Analytics must fire after Meta, Google, whichever rule shall be captured
- AA must then send the comma-separated list of executed rules in the tracking call
Things to consider / keep in mind
- this would mean that tags must run in sequence which is a performance aspect I would think about. If you have many requests that shall trigger first, your analytics request is sent last which may lead to lost tracking calls should the user navigate away
- list variables are previous: you only have 3 of them in AA
- instead of AA, you could instead create a webhook and send this information to it via POST at the very end (still, synchronous rule execution is a performance killer)
- AA then has to transform the window scoped variable with rule names into a list var