Matomo analytics implementation

[kirstenalarsen]

@JbPasquier : Matomo integration: I'm awaiting your feedback, if what I've implemented is enough. I also have to add the filter & text input, I still have to manage it in a way to avoid sending you an event whenever someone type one letter.

[kirstenalarsen]

We think that what we need here is to get Matomo setup in our wordpress, so that once we bring the Blox we can test

Setting up in our global Matomo account

[JbPasquier]

Based on the Mario's list, I've mostly pushed native Matomo's behaviours : trackPageView (With a custom implementation for our router), enableLinkTracking, trackVisibleContentImpressions (On the whole component), and trackContentInteractionNode (For the contact form).

All of these does allows:

• Tracking visible content impressions within a page.
• Tracking navigation events
• Tracking external navigation events (Including external links, eventual downloads, etc.)

I'll add the filtering and input search with the native Matomo's behaviour trackSiteSearch.

Whenever you plug in your Matomo into WordPress, the component will begin sending data.

[kirstenalarsen]

@mariocarabotta and @kirstenalarsen working on strategy etc (both Matomo and Airtable) https://app.mural.co/t/ofnaustralia2368/m/ofnaustralia2368/1680484477610/4a4f78bc9374292d496cc4b081aad15232409989?fromVisitorModal=true&invited=true&sender=kirsten1231

Possibly hiring external Matomo person to set up analytics

[kirstenalarsen]

hey @JbPasquier - just a little nudge on this one - can you add the filtering and input search?

[balessan]

Hey @kirstenalarsen, this one is on me and (one of my) top level priorities so plan to release the new events this week.

[mariocarabotta]

thank you @balessan! FYI, next week Kirsten and I are also talking with an analyst that might be able to help us with in depth testing of each individual event

[mariocarabotta]

List of tracking events:

Global unique visitors (should come out of the box) page views per session (should come out of the box) Funnels (should come out of the box)

Producer list search keywords filters interactions load more

Product list search keywords filters interactions load more

Producer details short intro > learn more (anchor) Assurance Partners > learn more Supporting evidence summary > learn more Supporting evidence summary > clicks on each anchor How to buy > view contact details How to buy > external URLs Contacts > View map Contacts > phone number Contacts > email address Contacts > social links Contact us form > how many people have sent a message Contact us form > “types” Supporting evidence > filters usage Supporting evidence > clicks on Service provider Supporting evidence > clicks on external link Supporting evidence > Downloads

[kirstenalarsen]

@balessan @JbPasquier we have hired a matomo guru to help us get all the tracking set up - say hi to Naser (appearing here shortly)

He is going to do an audit and test of what's there already - it would be great if you could summarise what is done so far so he knows what he's looking at

By the end of this week he will prepare a document that outlines the information he needs in the tracking information for each of the Custom Events outlined above.

I am not sure about the input/filters - perhaps @balessan if you can tell us what you're doing and where you're up to with this, and then Naser can advise if there are any recommended changes / what he needs at matomo end?

[balessan]

@kirstenalarsen @mariocarabotta we just merged the implementation of the filters and keyword search events, and what it triggers are trackSiteSearch Matomo events defined as follows:

• Producer lists filters: window._paq.push(['trackSiteSearch', e.detail, 'Producers list', false]); -> e.detail containing the value of either the keyword entered or the new filter selected
• Products lists filters: window._paq.push(['trackSiteSearch', e.detail, 'Products list', false]); -> e.detail containing the value of either the keyword entered or the new filter selected