@zssoftware opened this Issue on May 9th 2014

When creating a custom segment, it would be helpful to implement the ability to set that as the loaded-on-default segment.
Keywords: segment

@gaumondp commented on May 9th 2014

Interesting.

Should this feature be only available if the segment is also "cron generated" ?

If not, on installation with 50k pageviews a day, Piwik will have to work a lot before showing any data.

I'm just wondering.

Dali

@zssoftware commented on May 12th 2014

Good thinking!

Cron generated.

@mattab commented on May 13th 2014 Member

Great idea!

I think this could be done in a plugin:

  • New setting to choose which segment to load by default
  • When Piwik is loaded, the plugin could automatically redirect to the segment to load by default, if one was set by the user.
@mattab commented on October 30th 2015 Member

from email:

This feature is great but please allow us to set up a default segment for each websites and/or
that the UI remember the previous one when we switch from one website to another.

anyway your product is really good. I use it for a few years and it becomes better and better after each updates. Thank you!

@NanorPiwik commented on August 1st 2019

Hi there,
I recently got a demand about it recently. The need is the following one, the Matomo account is shared between an agency and a client. The internal traffic of the agency is going within the account which is increasing artificially the visits. As the account is in a cloud they cannot install the invalidate reports plugin to delete their traffic. So they need a segment applied by default which will remove their traffic.

@sgiehl commented on August 1st 2019 Member

@NanorPiwik if the agency has a static IP address, you could als exclude the traffic using an ip exclusion

@tsteur commented on August 1st 2019 Member

Wouldn't the cookie exclusion work as well?

@sgiehl commented on August 1st 2019 Member

Wouldn't the cookie exclusion work as well?

But that's something everyone needs to do on his machine in every browser (and do it again after clearing cookies)

Powered by GitHub Issue Mirror