New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When event (name, action or category) segment is applied, there is no data in some actions report, Inform users why #9796
Comments
Good point 👍 Won't be easy though as depending on segment some reports may still show some data while others not. |
As a new user, I’m really curios about the explanation for this. This limitation makes no sense to me; ff course I’d like to see which URLs are popular among users who triggered the The forum is full of threads with people asking for this (and they all go unanswered). |
Fair enough, marking as |
@Aeyoun maybe you could link to the few forum posts where this was discussed? this could help increase "perceived priority" on our end |
Here is a rough unfiltered list. The first 20 results were all this very issue (didn’t bother clicking through the 100 remaining threads), but your personal Google rankings may yield different results. |
I think this is related to in the case of no data one simply see something like this: "0 different visits counted within selected period and segment. |
Probably a duplicate of #11900 ? |
Duplicate of #11900 which we're planning to implement in Matomo 4 if all goes as planned. |
This should be fixed in Matomo 3.12.0 which will be released tomorrow - if you still experience this issue then, let us know. |
Let's create segment based on event name:
eventName==some name
When browsing 'Actions' reports for this segment, only reports in Actions / Events show some data. Others actions reports show message 'There is no data for this report.' and users think this is an error.
Users should be informed somehow that this is not error and it is logical consequence of using segment based on events.
This is also the case for any segment based on actions or events.
The text was updated successfully, but these errors were encountered: