matomo-org / matomo-org/developer-documentation

List of Events: Information Missing?

Open
#782 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
PHP
Stars
58
Forks
88
Avg merge
6d 3h
Merged PRs (30d)
13

Description

I'm currently developing a custom plugin to enhance the functionality of my Matomo setup, particularly around ecommerce tracking. My goal is to extend the ecommerce tracking capabilities by hooking into the event(s) fired when a new ecommerce order is captured. This functionality is crucial for my project's requirements, as it would allow for real-time processing and analysis of ecommerce data.

After thoroughly reviewing the Matomo documentation and community forums, I've encountered a roadblock. It appears that there might be a gap in the documentation regarding events related to ecommerce tracking, or possibly, such events do not exist within the current Matomo framework.

Specifically, I'm looking for:

An event that is fired when Matomo captures a new ecommerce order.
Documentation or examples on how to hook into such an event with a custom plugin.
My questions are as follows:

Are there any existing events within Matomo's ecommerce tracking that would allow a plugin to hook into the moment an order is captured?
If such events exist, could you please point me to the relevant documentation or provide an example of how to utilize these events within a custom plugin?
In case there are no such events currently available, could you advise on the best approach to achieve similar functionality? Would there be a consideration for including this feature in future updates?
Understanding these aspects is crucial for the development of my plugin and the enhancement of ecommerce tracking within my Matomo setup. Your guidance and insights on this matter would be immensely appreciated.

Thank you for your time and all the work you do with Matomo. Looking forward to your response.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no file, test, or entry point. First determine whether Matomo exposes an ecommerce-order event for custom plugins, then document the relevant hook and usage example if it exists; otherwise clarify the requested feature and recommended approach.

Written by the indexing model from the issue text.

Assessment

Tech stack
php
Domain
documentation
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.