@niklasternstedt opened this Issue on March 2nd 2022

Expected Behavior

I would be able to compare two segments regarding conversions and see if search, direct traffic, web pages etc are converting.

Current Behavior

When I choose to compare two segments like computer vs mobile and go to the report goals everything seems fine. But when I scroll down to see how search, direct traffic, web pages etc perform regarding conversions there are no data for conversions, only for visits. It works fine if I only choose one segment.

I succeeded to replicate the bug in your demo environment.

Steps to Reproduce (for Bugs)

  1. Choose a segment and then choose a another one to compare it with.
  2. Go to the report goals.
  3. Scroll down to channel type.
  4. You will see there is no data for conversions, only for visits


I'm trying to compare different segments with each other to try to gain more insights in how one of our clients web is performing.

Your Environment

  • Matomo Version: 4.7.1
  • PHP Version: 7.4.28
  • Additionally installed plugins: custom reports and search engine keywords performance
  • Browser: Brave
  • Operating System: MacOS Skärmavbild 2022-03-02 kl  08 31 18
@sgiehl commented on March 2nd 2022 Member

Thanks for creating the issue. I am able to reproduce that on our demo:
This seems to be a bug in compare mode, as both segments that are compared have conversions when viewed without comparing.
@tsteur that is something we should investigate. Not sure if that is a regression, or maybe never worked correctly.

@niklasternstedt commented on March 2nd 2022

I think it has worked before.

@tsteur commented on March 2nd 2022 Member

This might be a duplicate of https://github.com/matomo-org/matomo/issues/15849 ? My understanding was it never worked in the first place (and at least seems to have been broken since April 2020 unless it's a different issue)

@sgiehl commented on March 3rd 2022 Member

That seems to be the same issue, indeed.

@sgiehl commented on March 3rd 2022 Member

I think I found the problem. will prepare a PR to fix that.

This Issue was closed on March 4th 2022
Powered by GitHub Issue Mirror