You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the default view, the Campaign Name is hierarchical, with a subtable available for "Keyword - Content".
Since campaigns very often are run across different channels/sources, I feel that a more relevant subtable would instead be "Source - Medium" instead of "Keyword - Content". Could this perhaps be added as an option somewhere in order for the user to personalize?
Additionally - and I'm not sure how computationally expensive this would be - but ideally, I would love the possibility to drill down in the data, in the following sequence (i.e. with a subtable for each new subtable):
Campaign Name
---
Campaign Source - Medium
--
Campaign Content
--
Entry Page URL
I'm no Matomo expert - and maybe the above could be achieved with a custom report? - but perhaps the above suggestion would be something useful also to other non-powerusers.
The text was updated successfully, but these errors were encountered:
@webberian this could be achieved with a Custom Report and is exactly what it was made for. However, it currently allows max 3 levels in a single report. Meaning you would need to remove one of the layers in your example.
In the default view, the Campaign Name is hierarchical, with a subtable available for "Keyword - Content".
Since campaigns very often are run across different channels/sources, I feel that a more relevant subtable would instead be "Source - Medium" instead of "Keyword - Content". Could this perhaps be added as an option somewhere in order for the user to personalize?
Additionally - and I'm not sure how computationally expensive this would be - but ideally, I would love the possibility to drill down in the data, in the following sequence (i.e. with a subtable for each new subtable):
I'm no Matomo expert - and maybe the above could be achieved with a custom report? - but perhaps the above suggestion would be something useful also to other non-powerusers.
The text was updated successfully, but these errors were encountered: