We have been tracking our website data in Matomo for a few months.
1 Like
Hi @Lorenzo_Crippa
Unfortunately, no planning yet:
opened 02:37AM - 05 Aug 19 UTC
Currently each GA data import will create a new website in Matomo. Instead it wo… uld be great to let users choose, while preparing to import GA data, whether:
* to create a new website to import the GA property
* to import the data into an existing website ID in Matomo (eg. showing our website selector)
This will be valuable because often people want to migrate their Google Analytics web data after migrating from GA to Matomo. So they're already tracking data in both GA and Matomo. And having the GA historical data in a separate website makes analysis complicated (row evolution does not work, evolution graph, etc.).
Challenges with letting users import data into an existing site is how to decide what to do with:
* Goals
* Custom dimensions
The goals/custom dimensions may be present in both GA or Matomo, or just in GA. When present in both, we need a way to map the GA goals to Matomo Goals, maybe
* letting users choose from a list what to do each with each goal "Create a new goal in Matomo" or "Track this GA goal data into this existing Matomo Goal"
* or matching them by name. And show users "This goal has the same name in GA and Matomo so the data will be imported in the existing Goal" or "A goal with the same name does not yet exist in Matomo, please rename the goal in GA (or Matomo) so they match and try again. Or proceed and a new Goal will be created in Matomo".
_Notes: one thought that one could use roll-up reporting to aggregate together the old GA site and the new Matomo site, but that unfortunately wouldn't work because Roll-Up reporting aggregates the data from the logs._