matomo-org / matomo-org/plugin-GoogleAnalyticsImporter
Importing into an existing website in Matomo (not creating a new one)
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 29
- Forks
- 16
- Avg merge
- 15h 12m
- Merged PRs (30d)
- 14
Description
Currently each GA data import will create a new website in Matomo. Instead it would 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._
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named in the issue. Start by locating the current Google Analytics import flow and how it creates websites, then clarify the behavior for importing into an existing website and mapping goals and custom dimensions; done requires an agreed, testable design for these cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- analytics
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100