New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow to group by user_id in Live plugin (both API & interface) #7732
Comments
+1 |
the Live API with For other APIs, it's possible to use |
I tried something similar with:
It then returned I assume an array of visits, where you can also see userId. So the data could be aggregated I guess. Is there another way to get something similar like the profile, but aggregated by userId? |
You could do something like In Matomo 4 we may be adding a new API |
In general you want to use the In the Live API the data isn't grouped though when you apply a userId segment fyi. It returns basically only individual visits from visitors that had a userId |
nope, I don't really need the list of users. My master DB will have them.
But for a specific User ID, not |
If you pass the segment |
Thanks, but since then I realised that the User ID is not suitable for us,
as setting it changes the Visitor so Matomo reports them like two separate
unique visitors. I am trying to solve it with Custom Dimension (Visit
scope). I am basically recording what would be User ID as custom dimension
values and then viewing them under Visitors as well as querying raw SQL
data.
Do you see any potential issues with that?
…On Mon, 29 Jul 2019 at 21:12, Thomas Steur ***@***.***> wrote:
If you pass the segment userId=XYZ then this should work.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#7732?email_source=notifications&email_token=ALIFVZK4XIJPHAVJGOVWKITQB5FMVA5CNFSM4BAU7XN2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3B3YUI#issuecomment-516144209>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ALIFVZOEC5QK2OV6NLYRNE3QB5FMVANCNFSM4BAU7XNQ>
.
|
Currently we can use API or the UI to access data on visitor_id level.
Since Piwik has a user_id field that is used more often (e.g AdTruth integration), it makes sense also to allow users to access the data grouped by User ID on both API and UI level.
The text was updated successfully, but these errors were encountered: