HI
As mentioned in the global.ini.php, for the following setting "create_new_visit_after_midnight , ONLY CHANGE THIS VALUE WHEN YOU DO NOT USE MATOMO ARCHIVING, SINCE THIS COULD CAUSE PARTIALLY MISSING ARCHIVE DATA "
Can someone please provide more details on why this would cause partially missing archive data .
Will using auto archiving using cron job…(How to Set up Auto-Archiving of Your Reports - Analytics Platform - Matomo ) help in not causing the missing archive data.
Thanks
Lukas
February 17, 2018, 11:45am
2
Hi,
You can find some background information here:
opened 12:40PM - 15 Sep 14 UTC
closed 01:29AM - 22 Jan 15 UTC
Enhancement
Personally I don't think it is something we should add to Piwik by default, but … this could be an option for users who would like to compare Piwik and GA.
Here is a short quote from GA FAQ:
> Time-based expiry (including end of day):
> After 30 minutes of inactivity (default Piwik setting)
> At midnight (the topic of this ticket)
> Campaign change: (see https://github.com/piwik/piwik/issues/2624)
> If a user arrives via one campaign, leaves, and then comes back via a different campaign.
**Idea:**
Add a setting to Piwik to be able to force new visit after midnight (using site's timezone that will be cached in tracker's cache).
opened 12:17PM - 03 Nov 15 UTC
closed 03:35AM - 23 Dec 15 UTC
Refs #6217 - I disagree with the statement, that we shouldn't make a config sett… ing for forcing a new visit at midnight as there are clearly many use cases where day change after midnight is irrelevant and should not force a visit to be new. We need this flexibility for piwik to not exclude certain industries or IoT tracking.
For example:
- Users who run campaigns at night for their target groups get very confusing results (e.g. TV spots or campaigns for certain industries). For them, it's the timespan of the traffic peak that counts, not the day change at midnight.
- as we approach the IoT space, we face the fact that for many "things" (gadgets, machines, idk), midnight is not relevant, because they're running around the clock and define their own timeframes and new visit triggers. Therefore the analyst should have the option to force a new visit at any time, even if it's after e.g. 3 days.
How's your opinion on that?