Hi, my company has implemented matomo as a google analytics replacement. Many of the features are similar however my acquisition reports are only collecting data from a handful of campaigns and are missing our biggest online ad campaigns. We have a landing page that leads to an authentication page which logs into a single page load application. Google had me put a configuration snippet on each page. I’m doing the same with my matomo snippet, but am worried that it could be losing some acquisition data by resetting it each time. Anyone dealt with anything similar?
1 Like
It sounds like you’ve made a smooth transition from Google Analytics, but I can understand the concern with missing acquisition data, especially for your major campaigns.
Based on what you’ve described, the issue might be related to how the tracking snippet is handling the transition from your landing page to the authentication page and then to the single-page application (SPA). SPAs can sometimes cause tracking challenges since they don’t trigger traditional page loads.
Here are a few things you might consider:
- Use Matomo’s JavaScript Tracker for SPAs: Make sure that your Matomo snippet is configured to track page views dynamically in your SPA. Matomo provides specific documentation on how to do this, which might involve using
trackPageView
manually when the user navigates within the SPA. - Persistent Campaign Parameters: Ensure that your campaign parameters (like UTM tags) are being passed through each step of the user journey. If these are lost during the transition from the landing page to the SPA, Matomo might not be able to attribute the session to the correct campaign.
- Check Session Handling: If the session is being reset during navigation, this could also be causing the loss of acquisition data. You might want to look into how sessions are being managed and ensure that they persist across the different stages of the user flow.
If these steps don’t resolve the issue, it might be helpful to reach out to Matomo support or check their forums for similar cases. There’s a good chance someone else has encountered this and found a workaround.