Hello,
is there way to display the number of a special goal per page?
I want to see on which page we get most user registrations. The registration is available via an dialog on every page.
So I want to see how many of these goals (or events) are generated on the different pages.
I didn’t find a way to get this data.
Is this possible with “Custom reports” or any other extension?
Best regards,
Timo
Hi @iparker ,
Triggering an event every time a visitor complete the registration and convert a goal. By this way, you could keep track of user registrations. As you have mentioned registration is available in each page, it’s better to name the event accordingly in a way to identify the event of a particular page.
Thanks for your reply - but this is not really an answer for my question ;-).
I trigger an event and I convert this event to a goal. But my event has no information about the page.
Does Matomo really don’t know on which page an event/goal appears? It’s hard to believe that…
Thanks for your reply. I ordered the custom reports plugin and created a some reports. Also I have re-processed the data so older data should be in these reports.
I created a report like this:
Also I created a variant with action url (like on your screen).
Currently I have 2.331 konversions for my goal “Profil registriert” (registered user).
But in the custom report with the page-url I see a total of 4.654 goal-conversion (seems like factor 2?), and in custom report with action-url I see a total of 1.586 goal-conversions.
Both numbers are not correct. Where is the mistake? Why are the number of conversion is not equal to the number of conversion I see in the goal-detail-report?
Next to this it seems that the url when we track the event is not correct. I checked it very detaillied by passing the visitor log: The page-url and also the action-url in the custom report is not correct.
Thanks for some help!
Best regards,
Timo
Hi @iparker ,
Could you please get in touch with our support team at shop@matomo.org, so that this request can be managed efficiently.
I have exactly the same requirement. Is there a solution for this?
My guess is that within the custom report the number is wrong because it counts the visits that contains the goal AND the page url. The conversion rate seems to be calculated based on the number of visitors who reached the goal at any page in their visit and where the URL was accessed within their visit.
Hi @utrautma ,
Could you please get in touch with support team at shop@matomo.org
@iparker can you share with us whether and how you managed to solve this?
Hi @mp1
I think you have to reach support team (as this is a custom plugin)
Then don’t forget to share the needed configuration! 
Maybe @utrautma has also a clue?
Hi @mp1 ,
according to my current knowledge, the only workaround is to additionally track an event with a path information (e.g. event name with {{pagePath}}, which can be easily solved with the Matomo Tag Manager) and to work with this event information in the custom report.
Regards Udo
Hi Udo, i’m struggling with the same. So could you explain your solution with events more in detail and beside using the tag manager?
Beside or instead of the goal you send an event like this:
_paq.push(['trackEvent', 'GoalEvent', 'Application Form', document.location.href]);
And then you build a custom report with:
Do you do it like this or somehow similar?
In this video, someone is sending a custom dimension together with a goal. He is using a custom dimension on visit level, as it doesn’t work on action level (as described in this thread).
The matomo docs shows this example to attach a custom dimension to a certain action:
_paq.push(['trackGoal', idGoal, customRevenue, {dimension1: 'DimensionValue'}]);
I’m wondering if that would work and someone has tested this already. A side effect would be properly be, that the last send dimension value is also attached to the visitor, like you can see in the video. But i’m wondering if a custom report would give correct numbers.
Hi @bavarianbytes ,
yes, I completely agree with your first suggestion. It should work exactly as you described.
However, I would recommend tracking the goal and event so that you have both advantages in reporting later.
In the Tag Manager, the event would be configured as follows, for example:
Regarding the second approach with the custom dimension:
This can also work. It is important that it is a custom dimension at the behaviour level (“actions dimension”). Only if it were a custom dimension at the visit level could the problem you describe occur.
The advantage of sending goal and dimension together is that the set dimension value will be only used for this particular action and you do not have to delete the value after a tracking request.
In the Tag Manager, the tracking would be configured as follows, for example:
Regards Udo
Thank you Udo for confirmation.
I did it now via events. And i configured my goals, that they are fired based on the occurance of the events. So always both will happen, or nothing. With this the numbers in my custom reports (based on the events) and the numbers of the (native) goal report are always in sync.
A not to the second approach: the Matomo support said, that it won’t work as the last value of a custom dimension on visitor level will override early ones. So, if you want to allow that goals can be archived multiple times, it won’t work.
That’s correct.
The visitor level only applies for the duration of the entire visit.
In your case, however, the action level should work because there you can bind the custom dimension to a single action (in your case, a goal).
