@sidazhou opened this Issue on November 10th 2015

Piwik 2.15
Please see screen shots below. (1st one is the segmented one, 2nd is the all visits)

My understanding is that a Segment is a subset of your Analytics data.

In piwik dashboard, I go to "Goals" -> "Overview"
I notice that when I use "All visits (default)", it has LESS conversions than if I use some setting on Segment (which supposed to be a subset of All visits) In this case, the segment I used was "Page URL" "contains" "......."

How is this possible?

I've checked http://forum.piwik.org/read.php?2,129751,129751#msg-129751
which is solved by upgrading prototype, however I'm not using prototype nor custom variables.

link to forum:


@mattab commented on November 18th 2015 Member
@tsteur commented on December 13th 2015 Member

I reckon this one could be similar to https://github.com/piwik/piwik/issues/9367 and it might show more conversions etc due do the fact that it goes over any idaction_url. So if we tracked the same idaction_url for events as for pageviews then it might find the same conversion multiple times. I will try to have a look at the database.

@tsteur commented on December 14th 2015 Member

Problem is when segmenting we seem to not respect the setting "goal can be only converted once per visit" see


Eg with query

                piwik_log_conversion AS log_conversion
                LEFT JOIN piwik_log_link_visit_action AS log_link_visit_action ON log_conversion.idvisit = log_link_visit_action.idvisit
                ( log_conversion.server_time >= '2015-01-25 11:00:00'
                AND log_conversion.server_time <= '2015-01-26 10:59:59'
                AND log_conversion.idsite IN (1) )
                ( ( log_link_visit_action.idaction_url IN (SELECT idaction FROM piwik_log_action WHERE ( name LIKE CONCAT('%', '/', '%')  AND type = 1 )) ) )
                AND log_conversion.idgoal = 4

Here I get 49 results, but it should be 22 results which I get when I do eg SELECT distinct log_link_visit_action.idvisit

@xpader commented on November 26th 2019

This happeing again in 3.12.0...

This Issue was closed on December 21st 2015
Powered by GitHub Issue Mirror