Users Flow - Segmentations Not Populating

Premium Features
1

When viewing a segmentation of users with a specific event, the user flow shows no data, while the visitor log shows interactions for the same segment. Is there something we’re missing in order to get a segment to show in the users flow plugin?

piwik-error
piwik-error1864×902 266 KB

2

Hi,

It is not possible to view a user-flow based on a segmentation of event actions. An alternative method to achieve this would be to create a goal based on your event action. Then apply a Segment based on the visitor converting on that goal. This can be viewed in user-flow.

GOAL

SEGMENT

3

This appears to be the case for custom variables as well; is there any documentation available for what segmentations are supported by the User Flow extension? Without some of these segmentations available, it very quickly loses value for our use-case.

4

In this case it might be better to use a Custom Dimension in the action scope to achieve the result. Most segmentation should work except those filters that remove page views from the actions.

5

I think something is wrong with the user flow plugin besides just segmentation not working as advertised, for a number of dates the User Flow plugin shows no visual data while reporting a large number of visits; with no segmentation selected:

piwik empty
piwik empty1660×831 76.9 KB

Any debug actions we can take to get this plugin working properly?

7

Hi there,

Would it be possible to give us a View access to the website? If you can email a link to this forum post, and the username/pwd+ Matomo URL at shop at innocraft.com that would help us troubleshoot this. Thanks,

8

No, we deal with medical information, and due to regulations we are unable to provide external access to the system.

9

Can you maybe see any error in the developer tools console when you open the Users Flow report?

10

Yes there is 1 error in the console from JS

js_error
js_error2830×1234 429 KB 

TypeError: Cannot read property 'push' of undefined
    at index.php?module=Proxy&action=getNonCoreJs&cb=6a10410b3d97b712de23ab0e99bea2e9:60
    at Array.forEach (<anonymous>)
    at computeNodeLinks (index.php?module=Proxy&action=getNonCoreJs&cb=6a10410b3d97b712de23ab0e99bea2e9:60)
    at Object.sankey.layout (index.php?module=Proxy&action=getNonCoreJs&cb=6a10410b3d97b712de23ab0e99bea2e9:54)
    at drawSankeyChart (index.php?module=Proxy&action=getNonCoreJs&cb=6a10410b3d97b712de23ab0e99bea2e9:204)
    at index.php?module=Proxy&action=getNonCoreJs&cb=6a10410b3d97b712de23ab0e99bea2e9:257
    at index.php?module=Proxy&action=getCoreJs&cb=6a10410b3d97b712de23ab0e99bea2e9:255
    at m.$digest (index.php?module=Proxy&action=getCoreJs&cb=6a10410b3d97b712de23ab0e99bea2e9:266)
    at m.$apply (index.php?module=Proxy&action=getCoreJs&cb=6a10410b3d97b712de23ab0e99bea2e9:269)
    at l (index.php?module=Proxy&action=getCoreJs&cb=6a10410b3d97b712de23ab0e99bea2e9:221) "Possibly unhandled rejection: {}"
11

HI,

We have investigated this problem and have now released an update to the plugin.

Can you upgrade your plugin to the latest version (3.1.5) and see if it resolves the JS error.

Thanks

12

Sorry for the long reply, it took a while for the change request to go through to upgrade this plugin. We have upgraded to 3.1.6, and are still seeing an error in user flow, unsegmented.

js_error
js_error1735×804 203 KB 

index.php?module=Proxy&action=getCoreJs&cb=a40894f3945b0aacb566d3db9247b7f9:242 TypeError: Cannot read property 'push' of undefined
    at index.php?module=Proxy&action=getNonCoreJs&cb=a40894f3945b0aacb566d3db9247b7f9:60
    at Array.forEach (<anonymous>)
    at computeNodeLinks (index.php?module=Proxy&action=getNonCoreJs&cb=a40894f3945b0aacb566d3db9247b7f9:60)
    at Object.sankey.layout (index.php?module=Proxy&action=getNonCoreJs&cb=a40894f3945b0aacb566d3db9247b7f9:54)
    at drawSankeyChart (index.php?module=Proxy&action=getNonCoreJs&cb=a40894f3945b0aacb566d3db9247b7f9:205)
    at index.php?module=Proxy&action=getNonCoreJs&cb=a40894f3945b0aacb566d3db9247b7f9:259
    at index.php?module=Proxy&action=getCoreJs&cb=a40894f3945b0aacb566d3db9247b7f9:255
    at m.$digest (index.php?module=Proxy&action=getCoreJs&cb=a40894f3945b0aacb566d3db9247b7f9:266)
    at m.$apply (index.php?module=Proxy&action=getCoreJs&cb=a40894f3945b0aacb566d3db9247b7f9:269)
    at l (index.php?module=Proxy&action=getCoreJs&cb=a40894f3945b0aacb566d3db9247b7f9:221) "Possibly unhandled rejection: {}"
13

Hi,

Sorry about this but it looks like you are not running the latest version of Matomo which we have based the plugin update on.

You will need to update to the latest (3.5.0) to see if the update has solved the issue.

Please upgrade your Matomo and let us know the outcome.

Thanks