You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a client who uses Jetpack and their analytics functions.
They are a successful eCom business and have 100k website views over 5 years and use that as social proof on social media posts.
I want to remove Jetpack and install Koko but want to show the previous analytics from previous years.
Is there a way to modify the database entry for 'all-time' views in Koko? Or a way to start counting from a certain value so that the previous total is maintained?
Any ideas?
Many thanks!
Johnny
The text was updated successfully, but these errors were encountered:
Sorry it took this long for me to respond. Ideally, data would be migrated properly and inserted into the database in the format that Koko Analytics expects. But as that is quite some work, an easier method would be to simply insert the historical number on a given day if all you care about is that the total number of visitor matches over time.
That could be as simple as running the following query:
That would tell Koko that 100K visitors and 100K pageviews occured on 2023-08-30. This will mess up the comparisons over week/month/year views though, but a simple way to improve upon the above query is to insert a row per year. That way the comparisons will only be off for the first month.
Hope that helps a bit (or anyone reading this by now).
Hi all,
I have a client who uses Jetpack and their analytics functions.
They are a successful eCom business and have 100k website views over 5 years and use that as social proof on social media posts.
I want to remove Jetpack and install Koko but want to show the previous analytics from previous years.
Is there a way to modify the database entry for 'all-time' views in Koko? Or a way to start counting from a certain value so that the previous total is maintained?
Any ideas?
Many thanks!
The text was updated successfully, but these errors were encountered: