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

Goal Tracking plugin list of feature requests #1434

Closed
mattab opened this issue Jun 18, 2010 · 8 comments
Closed

Goal Tracking plugin list of feature requests #1434

mattab opened this issue Jun 18, 2010 · 8 comments
Labels
Enhancement For new feature suggestions that enhance Matomo's capabilities or add a new report, new API etc. Major Indicates the severity or impact or benefit of an issue is much higher than normal but not critical. worksforme The issue cannot be reproduced and things work as intended.

Comments

@mattab
Copy link
Member

mattab commented Jun 18, 2010

In #774, the first stable release of the Goal Tracking plugin was released in Piwik. We have other ideas of improvements to the plugin:

Create Goal options

  • Currently, only one goal conversion can be triggered per visit. Add an option, per goal, to allow recording multiple conversion per visit for this goal. (Implemented in Add a setting to allow a Goal to trigger multiple times per visit #2258.)
    • it could be possible to trigger a goal based on a Page title (currently done on URL) (implemented in Allow Goal to trigger based on Page Title (Event like Goal trigger) #2293)
    • There should be an easy way to test a URL against the regex : When entering the regex to detect as a goal, we could query the piwik API for this regex and autocomplete the list all URLs that match the regex; allows for an easy debug/check that the regex is correct and will be triggered when expected
    • use case for "multiple conversions per visit": if goal is 'add product to cart' then we want to track multiple conversions (with custom revenue) per visit. See Piwik Ecommerce Tracking Plugin #898

As suggested in forum post:

  • Add a new field in the Goal Create form "Also create this goal in the following websites: []" that would let a user select the websites on which to create the same goal, as well as the currently selected website.

Reporting & UI

  • GeoIp compatibility, archive goals by city, country? see archiveDayAggregateGoals and ticket Update jqplot.js #45
  • Add visits with conversion sparkline in the VisitsSummary overview
    • In the Goal Reports, under "Conversions Overview" listing the top 3 converting items in a segment, add a 'view more' link that would
    • load the requested table below
    • move the cursor to the top of the table
    • if possible, have this data in the hash so that the URL can be passed around ("Check out the top keyword for our 'Checkout' goal!")
@robocoder
Copy link
Contributor

The Goals report currently shows:

  • segment
  • visits
  • conversions
  • conversion rate
  • revenue per visit
  • conversion rate (what's this?)
  • value per visit (which looks a lot like revenue per visit... bug?)

Kim Dushinski's "The Mobile Marketing Handbook" gives a more elaborate campaign breakdown that would require ad server integration (to determine the number of ad impressions delivered, and cost of the campaign), and allowing multiple goal conversions per visitor, e.g.,

Ad impressions                                100000
Ad click-through rate (%)                         5%
Visitors                                        5000
Conversion rate (e.g., request coupon)           15%
Conversions                                      750

Conversion rate (e.g., coupon redemptions)       33%
Conversions                                      250

Average revenue per conversion                   $10
Total revenue                                  $2500

Ad cost                                        $1000
Profit (Loss)                                  $1500

@mattab
Copy link
Member Author

mattab commented Aug 26, 2010

Maybe we could disable adding goals as submenus when there are more than N goals (N to be defined) ?

@mattab
Copy link
Member Author

mattab commented Jan 13, 2011

Schema:

  • log_conversion.url could be idaction and link to the lookup table
  • log_conversion.referer_visit_server_date could be removed (unused and duplicate of idvisit)

New report

  • we could easily add a report 'Days to conversion' that would give how many days it takes for a unique visitor from first visit to conversion to a goal. Schema would add a 'referer_days_ago' field

New report (not possible with current data or without a costly query)

See this post to learn more about these reports: http://www.kaushik.net/avinash/2006/08/excellent-analytics-tip6-measure-days-visits-to-purchase.html

@mattab
Copy link
Member Author

mattab commented Jan 17, 2011

Moved some requirements to specific tickets: #2029, #2030, #2031

@mattab
Copy link
Member Author

mattab commented Mar 16, 2011

For "manual goal conversion", we could also put a code snippet that shows how to trigger a Goal on form submit, as it is a common use case, and technical enough to do that many users can't do it out of the box. Would be great to have the help right in the Goal create/edit UI.

@robocoder
Copy link
Contributor

re: onsubmit. Will have to see if Webkit bug 54783 affects this too.

@anonymous-matomo-user
Copy link

For users who have set multiple goals, add an option to assign each goal a different colored flag instead of a default green one so that the user can quickly tell which goal was achieved on the visitor log without having to hover over the flag.

@mattab
Copy link
Member Author

mattab commented Apr 6, 2014

Closing this ticket as it seems mostly empty now that we've implemented most ideas listed here. Feel free to create a ticket for specific improvements to Goal plugin!

This issue was closed.
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. Major Indicates the severity or impact or benefit of an issue is much higher than normal but not critical. worksforme The issue cannot be reproduced and things work as intended.
Projects
None yet
Development

No branches or pull requests

3 participants