Skip to content
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 any plugin to extend and display data in the Visitor Log and Visitor Profile #6111

Closed
tsteur opened this issue Sep 3, 2014 · 11 comments · Fixed by #11579
Closed

Allow any plugin to extend and display data in the Visitor Log and Visitor Profile #6111

tsteur opened this issue Sep 3, 2014 · 11 comments · Fixed by #11579
Assignees
Labels
Enhancement For new feature suggestions that enhance Matomo's capabilities or add a new report, new API etc.
Milestone

Comments

@tsteur
Copy link
Member

tsteur commented Sep 3, 2014

Follow up for #6045 where we made it possible for any plugin to add data to the API. Now we want the plugins to extend Live widget, Visitor Log and Visitor profile.

This can be quite complex as we probably do not want loads of events there. Maybe we can start using AngularJS for this as a proof of concept. As they do not use the dataTable it is easier to rewrite this component. Maybe there are other, better solutions as well.

@mattab
Copy link
Member

mattab commented Sep 3, 2014

Example use case: Provider plugin to extend Visitor Log and Visitor Profile, covered #5341

@tsteur
Copy link
Member Author

tsteur commented May 4, 2015

This will be important for #7131 and #4734 . When a type (eg Website or MobileApp) disables some reports/dimensions, the related information should not be shown in the Live plugin. For example if referrers information are disabled by a type "MobileApp", no referrer information should be displayed in the Live reports.

@KaanErturk
Copy link

This would be very much useful in order to extend visitor profile popup for additional information. Right now the only hacky way seems to be to add the data to the $visitor['customVariables'] array, even though the values are limited to 50 chars in the template.

Eventually, it would be great to have a way to add new rows (under the avatar) to the visitor profile popup, like Summary, Location, etc. That would give plenty of space to use there.

@mattab
Copy link
Member

mattab commented Mar 21, 2017

Adding tentatively to 3.0.3 milestone, to be fixed along with:

Ideally we'd make both Visitor Log and Visitor Profile use same logic so that extending one extends the other too!

@mattab mattab changed the title Let any plugin extend the Live plugin templates Allow any plugin to extend and display data in the Visitor Log and Visitor Profile Mar 21, 2017
@hpvd
Copy link

hpvd commented Mar 23, 2017

+1

@hpvd
Copy link

hpvd commented Mar 23, 2017

would be perfect if this solution not only works for plugins but also for Piwiks "own" base data,
e.g. Content-tracking: display content views and interactions in the Visitor log #6416

@hpvd
Copy link

hpvd commented Mar 23, 2017

for reasons, details, ideas regarding extending informations in visitorlog see also #6416

@hpvd
Copy link

hpvd commented Mar 23, 2017

when extending information in visitorprofile one maybe should take this into account to give new information the right position:
visitor profile: built image of vistor is distorted #9507

@hpvd
Copy link

hpvd commented Sep 13, 2017

does this also cover a possibility to extend visitor summary in visitor profile?
would be pretty handy for things like this one:
advanced-online-marketing/AOM#12

@sgiehl
Copy link
Member

sgiehl commented Sep 13, 2017

Actually yes, that should be possible by implementing a VisitorDetails class in the plugin and adding a ProfileSummary.

@hpvd
Copy link

hpvd commented Sep 13, 2017

many thanks, awesome!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Enhancement For new feature suggestions that enhance Matomo's capabilities or add a new report, new API etc.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants