It's quite limiting not to be able to view conversion metrics in Row Evolution. For example, it would be very valuable to see "Conversion rate" and "conversions" over time, for a particular Campaign name, for a particular goal. Currently, the row evolution popover doesn't let us see any of the goal metrics:

As the issue is not quite clear. What's wanted here is when viewing a goal eg https://demo.matomo.cloud/index.php?module=CoreHome&action=index&idSite=1&period=day&date=yesterday#?idSite=1&period=day&date=yesterday&segment=&category=Goals_Goals&subcategory=6 ,

and in the "by dimension" view click on "row evolution"

then it is showing different metrics compared to the report in the table

It is showing visits and correctly.

Does this mean we want to show the Evolution of 'New Resume Conversions', 'New Resume Conversion Rate', 'New Resume Revenue'..., the data in the table, instead of 'Unique visitors', 'Actions' etc in the graph?

Yes, that's my understanding.

Maybe @mattab can confirm too but I'm pretty sure that's what we're after 👍

I could not find how to do this quickly with only existing code.

Should we

1. create an API hook/endpoint in the Goals API for this that becomes the apiMethod=Goals.someMethod and pass that in a URL so that e.g. this:

/index.php?date=2021-09-19&apiMethod=Referrers.getReferrerType&label=%40Search%2520Engines&disableLink=1&module=CoreHome&action=getRowEvolutionPopover&idSite=1&period=year&colors=...

becomes

/index.php?date=2021-09-19&apiMethod=Goals.someMethod&label=%40Search%2520Engines&disableLink=1&module=Goals&action=getRowEvolutionPopover&idSite=1&period=year&colors=...

and then change the call in the JS on the client side to fetch this URL instead.

In the API call we could return the metrics to the popover render call and reuse quite a bit of code.

2. Alternatively, we could maybe add the metrics to the API call that already exists.

I feel the first approach could be more flexible also for other plugins or core. But this might also be more work.

3. I wonder also, if APIs should be preferred that return JSON and the client side should fetch or already have a template in AngularJS or later Vue and populate that instead. That way the template could be cached and the API call would be cleaner and smaller too.

I haven't looked in detail. But I think what you first will want to do is add the idGoal to the row evolution request which is currently not there. Without this you cannot possible show the metrics for the right goal I'm assuming.

When that idGoal is present then you will probably want to change which columns to display in the row evolution. To make this work you will want to check what the goals visualisation is doing probably https://github.com/matomo-org/matomo/blob/4.5.0-b2/plugins/Goals/Visualizations/Goals.php

I've only had a look for 5 minutes so I'm not too much into this topic but that's how I would likely approach it.