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
Action URL segment could filter both (Page URLs OR Event URLs) #11131
Comments
Results of investigation done on my side: If such an entry will have idaction.type changed to 1 (page url) then segmentation by Page URL will properly segment Events report. This change was made on Nov 30, 2015: ea9ac05#diff-49022a94ed8c0e968b315e2d98fd1ef7L64 Earlier, the the returned value type was hardcoded in function 'getUrlAndType' as "self::TYPE_PAGE_URL" = 1 After the change, there is used a function 'getActionType' which returns hardcoded "Action::TYPE_EVENT" = 10 To sum up: Maybe it is intended behaviour, but just wasn't implemented fully properly? Maybe this association is proper, but for some reason, segmentation cannot pick up Action URL by "Action::TYPE_EVENT" = 10 ? ping @mattab as I think this may be pretty important (is for me as well 😄 ) |
Thanks for the information! I think this could be categorised as a bug. @tsteur do you have any thought? |
type 10 is correct. I would say the problem is the same as #8854 which eventually needs to be solved generally but like easily 4-5 days of work |
without digging deep or looking in the code, I'm thinking as @mgonera suggests that Action URL segment could filter both (Page URLs OR Event URLs). Is this correct? if so, I would leave this issue opened and welcome a pull request from PP for this 👍 |
Yes exactly, I see this as expected behavior, Event is an Action, so if it has an URL, should be segmented by Action URL. 👍 |
Useful for many use cases for example: * Creating Custom Reports such as "Top page URLs by Event action" * Segmenting by Event URL and view events triggered on a specific Page URL * Fixes #11131 Action URL segment could filter both Page URLs OR Event URLs (as advertised originally in the 2.16.0 changelog but it wasn't actually fully working yet)
Useful for many use cases for example: * Creating Custom Reports such as "Top page URLs by Event action" * Segmenting by Event URL and view events triggered on a specific Page URL * Fixes #11131 Action URL segment could filter both Page URLs OR Event URLs (as advertised originally in the 2.16.0 changelog but it wasn't actually fully working yet)
Useful for many use cases for example: * Creating Custom Reports such as "Top page URLs by Event action" * Segmenting by Event URL and view events triggered on a specific Page URL * Fixes #11131 Action URL segment could filter both Page URLs OR Event URLs (as advertised originally in the 2.16.0 changelog but it wasn't actually fully working yet)
Useful for many use cases for example: * Creating Custom Reports such as "Top page URLs by Event action" * Segmenting by Event URL and view events triggered on a specific Page URL * Fixes #11131 Action URL segment could filter both Page URLs OR Event URLs (as advertised originally in the 2.16.0 changelog but it wasn't actually fully working yet)
) * New "Event URL" segment `eventUrl` to segment on any Segment URL Useful for many use cases for example: * Creating Custom Reports such as "Top page URLs by Event action" * Segmenting by Event URL and view events triggered on a specific Page URL * Fixes #11131 Action URL segment could filter both Page URLs OR Event URLs (as advertised originally in the 2.16.0 changelog but it wasn't actually fully working yet) * fix typo no capital letter * remove column type to prevent new column being created in the log_link_visit_action table * set correct action type for segment eventUrl * modify test * eventUrl needs action data * fix suggested values for eventUrl * update test files * event url is stored without protocol * update test file
This issue has been mentioned on Matomo forums. There might be relevant details there: https://forum.matomo.org/t/difference-between-action-url-and-page-url/40622/21 |
After recording an event, it also has idaction_url field (log_link_visit_action) filled with ID of URL it took place on. This URL is saved with idaction.type=10
Unfortunately, when later segmenting using "Action URL", events report won't be segmented, despite proper data residing in the database.
Confirmed on 2.16.2 and 3.0. Also confirmed proper behaviour on 2.15. I will be grateful for information if this should be treated as a bug, or maybe this behaviour can be explained.
The text was updated successfully, but these errors were encountered: