M
Yes! Matomo can track visitor behaviour before and after replacing your existing page. You can monitor: Page views and bounce rates. Visitor engagement and CTA clicks. Form submissions and conversion rates. Recommended setup: Enable page tracking. Configure event tracking for buttons and forms. Set up conversion goals. Add an annotation for the launch date. Compare 30 days before and after the replacement. If you keep the same URL, you can compare historical performance using Matomo’s date…
M
Having trouble reaching our support team by email? We’re currently affected by the Microsoft outage. For support, the best place to reach us is through the Matomo forums. Alternatively, feel free to contact us through our social channels. We’ll get back to any outstanding emails as soon as services are restored. Thanks for bearing with us!
M
Regarding the engineering workflow and setup considerations for Custom Reports and Ecommerce: When structuring CAD data interfaces, solver boundary conditions, or multi-format pipelines, verifying format schema compliance and dimensional tolerances upfront avoids runtime exceptions. You can reference our specialized engineering calculation utility at Engineering Workstation Hardware Spec Builder. Hopefully this reference proves useful for the workflow discussed here.
M
Matomo can track the updated page’s views, entrances, bounce rate, and any goal you define as a conversion. To compare before and after, set a goal for the service page (form submit or contact click), use segments for the old and new URLs, and compare date ranges in Visitors > Overview and Behaviour > Pages. Add an annotation for the launch date so changes are visible. For interaction depth, add event tracking on key buttons and forms; heatmaps and session recordings require the relevant…
M
The standard Matomo cookies are pkid. and pkses.; pkref. appears when campaign/referrer attribution is enabled, while pkcvar and pkhsr are only used for specific features. In Real Cookie Banner, add a service under Analytics with your organisation as provider and list those cookie name patterns. For the content blocker, block requests to the Matomo tracker script and tracking endpoint on your installation. That gates both the script and cookie-setting requests without hard-coding a third-party…
M
Hello @domdain Thank you for sharing your feedback and suggestion! I wanted to let you know that I’ve already submitted a feature request to our development team for consideration. We appreciate you taking the time to share your ideas, as customer feedback helps us identify opportunities to improve Matomo.
M
Tag Manager isn’t the only route. The standard JS tracker can also give you cookieless/basic pageviews when consent is absent or declined, then switch to normal cookie-based tracking after acceptance; the Complianz guide linked above covers both paths. So pick Tag Manager only if its trigger setup is easier for you. Since you’re in Sweden/EU, treat “cookieless” as a technical measure rather than an automatic legal conclusion—worth a quick check with your DPO.
M
Define a small set of custom dimensions in Matomo admin first—for example WASM engine/build, file format, device memory class and heap-usage bucket—and note their IDs. Set them before each event: _paq.push([‘setCustomDimension’, 1, engine]); then push the event. Use the event value for a coarse integer heap MB and keep dimensions low-cardinality; avoid exact byte counts or per-file IDs. For OOM sampling, bucket memory (e.g. <256, 256–512, >512 MB) and aggregate in reports.
M
I think having clear sales reports is important for any online store. For a merchandise website like Ethel Cain Merch, tracking which product pages bring in the most sales would make it much easier to understand customer interests and improve the store.
M
The 404s on the Privacy/GDPR tab are most likely broken documentation links, so they don’t necessarily mean tracking is broken. For the “tracking code disabled” notice, check Matomo > Settings > Tracking and confirm tracking is enabled; then run the System Check and temporarily disable other plugins to rule out a conflict.
M
Thank you. The tracking code is definitely present on all pages as we generate master templates for all clients. I’ll do a comparison at the mid-month mark and post back about what I see.
M
md5(‘password1’) with _isPasswordHashed=true works! That’s a good enough solution for me, wont require too much workround. Thanks a lot for sharing your knowledge and helping out! In conclusion it appear from this limited research that plaintext passwords does not work through the API and you have to know that _isPasswordHashed does not imply a hashed password in the database but rather the use of a pre hashed md5 before the password is hashed in the database.
M
Those limits only apply to reports archived after you change them. Your old day/week/month archives are already cut down to “Others”, and a range is just built by adding those up, so raising the numbers alone won’t change anything for the past half year. You’d have to invalidate that period (./console core:invalidate-report-data --dates=2026-05-01,2026-10-31 --sites=1, with your own dates and site id) and let core:archive run again. Also worth checking the settings sit under [General] in…
M
Hello, This message popped up on screen today: WARNING: /core/ProxyHttp.php(119): Warning - filesize(): stat failed for /tmp/assets/asset_manager_core_js.js - Matomo 5.14.2 - Please report ... (Module: Proxy, Action: getCoreJs, In CLI mode: false) First time seen today and only reported on a single machine as far as I’m aware. Let me know if I can provide any other information. Best regards Alexander
M
I agree with keeping the same site, and the key change is in your signup flow so a relaunch reuses the old site and user instead of creating new ones. That keeps the full history in one place, since Matomo has no built-in way to move old visits into a new site id.
M
I have a matomo 5.8.0 on-premise and use the matomo API to receive a range of pageTitles over a time period of half a year. Unfortunately matomo seems to archieve a lot of the pageTitles into “others” and I do not receive all the pageTitles that I expect from that time range. I tried setting the datatable_archiving_maximum_rows_actions, datatable_archiving_maximum_rows_subtable_actions and the archiving_ranking_query_row_limit to higher numbers in my config file, but that didn’t seem to change…
M
The cleanest approach I know is to not create a new site at all when a customer relaunches. If you keep tracking into the same idSite on the relaunched site, the history stays in one continuous view with nothing to merge. I only create a new site when the domain or the tracking really is separate, and then I use Matomo’s Roll-Up Reporting to look at the old and new sites together.
M
Hello @zaraaron Thank you for sharing your suggestions and for taking the time to participate in the Matomo community! We’ve made numerous improvements to Matomo for WordPress over the years, including enhancements to stability, performance, and usability. We truly appreciate your participation and willingness to help other users. Community contributions like yours are always welcome and valued!
M
One extra check is to compare page views against visits, not just unique visitors, in Visitors > Overview. Pages per visit explains normal gaps; a sudden high pageviews-to-visits ratio on one page more often points to duplicate tracking or reloads. Also make sure both reports use the same segment and date range, especially if one is filtered to a specific page URL.
M
Custom alerts and scheduled export segmentation are often underutilized when tracking operational tool telemetry. For infrastructure teams cross-referencing web usage events against backend software daemon checkouts, automated log parsing pinpoints peak concurrency without manual spreadsheet aggregation. An online debug log parser for floating license daemons is accessible at FLEXlm License Server Debug Log & Peak Usage Analyzer. Hope this technical context proves helpful!
M
When structuring multi-client or departmental analytics instances to apportion infrastructure consumption, tracking seat utilization rates against licensing overhead provides a clear picture of tenant efficiency. In engineering environments where CAD tool seats represent significant operational expenditure, evaluating usage trends against total cost of ownership clarifies subscription planning. A reference model is hosted at Enterprise CAD & Software License TCO Calculator. Hopefully this…
M
Fixed full periods are the right instinct. One practical tweak: when reviewing a week or month that is still in progress, compare only complete periods, or use Matomo’s previous-period comparison over equal-length complete ranges. Including today’s partial week will look like a drop and skew conclusions. Combine that with annotations for campaigns, redesigns, or tracking changes, and save a segment so the same audience definition is used each time. That keeps reports comparable without needing…
M
AWStats is server-log based, while Matomo normally relies on JavaScript, so the two will rarely match exactly. Matomo won’t see bots, non-JS clients, ad/tracker blockers, or cached pages that don’t execute the tracker; differing timezones and “visit” versus “hit” definitions can also widen the gap. First confirm the tracking code is present on every page/template, compare the same date range and timezone, and check whether bot exclusion or consent settings are filtering traffic. A 50%…
M
One extra option for the “read” part: add a small event on greeting pages that fires after the visitor has been on the page for, say, 10–15 seconds or scrolls past the greeting. Then create a goal of type Event. That gives you a single page-plus-engagement signal, while the heartbeat timer still makes duration measurements more realistic. Keep the threshold short, since visitors who bounce immediately should not count. When testing, use a private window with extensions disabled, because many…
M
For improving conversions, I’d lean toward Custom Segments, because they let you compare converters and non-converters instead of just confirming that a goal fired. One underrated complement is the Transitions report: it shows the paths people take after a page, which helps spot where a specific segment drops off. Combined with a campaign or returning-visitor segment, you can usually tell whether the problem is traffic quality or the page itself.
M
A tip I’d add is to build one or two segments around your main goal—for example, visitors who completed a signup versus those who didn’t—and compare them by device, landing page, and source. That often reveals a specific mismatch, such as mobile users dropping off on a form, that overall reports hide. I’d also keep a small dashboard with only goal conversion rate, top landing pages, and channel conversion rate, and schedule it weekly so the data gets reviewed consistently instead of only when…
M
Andreas: Even with a pre hashed password and That part is expected I think. With _isPasswordHashed=true Matomo only skips its own md5 step and still runs password_hash() on whatever you send, so “pre-hashed” there means md5 of the password, not a bcrypt hash. If you send md5(‘password1’) with the flag, it should end up the same as your manual UPDATE that worked.
M
Thank you. That is the approach that we decided on. We’ve only set up a small number of clients so far and the process has been somewhat easy. My concern is that the data being reported by Matomo seems to be wildly different than the data being reported by AWStats. Matomo is sometimes shows 50% less traffic. So now I have to troubleshoot why the data is so different.
M
Thanks for all the useful replies! invite_token is always NULL when using addUser through the API. Which is good for us because sending out emails to every user for a specific Matomo account is not anything we can do in our system, we need to use our existing system for accounts. Seems like Matomo tried to remove the possibility to create users without an email in version 4.1.1 according to GitHub issue 19772 (title: " Bring back an option for Add Users / New user the old way") but the API kind…
M
Umar Umar: After that, I visit the site myself and watch Visitors > Real-time to confirm my own visit shows up before I trust the numbers Good check, with one catch: if your browser has an ad blocker, it often blocks matomo.js, so your own visit never shows up and it looks like tracking is broken. A private window that.