Cannot login with new users through web interface
Please check the invite_token column for user1 first and share what you find there. If it is filled in, that pending invite would explain the login error even with the right password.
Posts from every feed QUEST has found across the web — blogs, news, podcasts, channels and more.
Please check the invite_token column for user1 first and share what you find there. If it is filled in, that pending invite would explain the login error even with the right password.
OwlTornado’s invite_token point is the one that fits your setup for me. You created the user through the API and the invite email goes to user1@user1, which can never be delivered or accepted, so the account stays a pending invite and Matomo answers every login with the same generic wrong-password error. That also fits with the superuser password change fixing it, so I would check the invite_token column on that user row first before touching the password hashing again.
One thing from your list: the manual UPDATE can’t work with password_hash(‘password1’), because Matomo doesn’t hash the plain password, it hashes its md5, so it has to be password_hash(md5(‘password1’), PASSWORD_DEFAULT). Worth doing that once directly in the DB to rule out the API part. And have a look at the user row itself: if invite_token is filled in, Matomo treats the user as a pending invite, and those can’t log in until the invite is accepted.
Hi! We would really like to use Matomo in our environment to provide statistics for our customers but I am unable to login to the web interface after creating a new View user (through the API) in my personal test setup of Matomo (for testing before production). Every time I try to login through the web interface I get “Error: Wrong username and/or password”. As I understand it the “Login” plugin in Matomo is used for this. In production we have our own environment where users would be created…
One setup mistake I ran into early on was putting the tracking code on the homepage only, so my inner pages showed no visits at all. I would check that the code is on every page of the site, not just the front page. After that, I visit the site myself and watch Visitors > Real-time to confirm my own visit shows up before I trust the numbers.
For the most read pages, Behaviour > Pages is enough. If all greetings live under one path like /ucapan/ they show up as one folder you can expand. For the goal, Matomo can’t do “visited this page AND stayed X seconds” in one goal, so I’d make two: one “Visit a given URL” goal with your greetings path, and one “Visit duration” goal. The common mistake on a site like that: most visits are a single page, and Matomo counts 0 seconds for those unless you turn on the heartbeat timer in the tracking…
Aligning standard aggregation periods across multi-site dashboards ensures that concurrency peaks are not smoothed out by overly broad weekly or monthly buckets. For server administration teams parsing daemon access logs to correlate concurrent checkout spikes with network telemetry, offline log normalization helps identify orphaned sessions. An interactive log inspection tool can be referenced at FLEXlm License Server Debug Log & Peak Usage Analyzer. Hope this technical reference proves…
When structuring reporting intervals to compare usage patterns without noise, normalizing seasonal spikes against baseline idle capacity provides clearer cost attribution. In engineering departments where seat subscriptions and floating license pools represent significant capital expenditure, evaluating utilization trends directly against total cost of ownership clarifies seat right-sizing decisions. A reference calculation model is organized at Enterprise CAD & Software License TCO Calculator.…
I’d recommend checking whether the tracking code is properly enabled in WordPress and whether the plugin version is up to date. The 404 errors on the privacy links sound like they could be broken documentation links. Hopefully someone from the Matomo team can clarify this.
One thing I’ve found useful with Matomo is focusing on a few key metrics rather than trying to analyze every report at once. Tracking traffic sources, landing-page performance, visitor behavior, and goal conversions can provide a much clearer picture of how a website is performing. For lead-generation websites, I would also recommend setting up goals for important actions such as contact-form submissions, phone-number clicks, and quote requests. This helps identify which pages and traffic…
Hi James, I run a small property inspection business in Birmingham, and I had the same question, so I set it up the way 10XLinks described, and it works well for a small service business. I track three actions as goals in Matomo, not just page views. First, the booking form submission, triggered by the thank-you page. Second, a tap on the phone number, triggered by a click event. Third, a visit to a service or area page followed by a contact, because a lot of people read the service page first…
As far as I can see there is no per-site delete built in, the deletion setting applies across the whole instance. Worth raising it as a feature request with your exact use case, so the team can say if it is planned.
Follow these steps: Log in to your Matomo account. Click the Administration (gear) icon. Navigate to Personal → Settings. Find the Date to load by default option. Select your preferred period: Current week Current month Last 7 days Last 30 days Today Click Save. Matomo will use your selected default reporting period when loading reports, including the All Websites overview. Alternative: If you only want a quick shortcut, you can also bookmark the All Websites page with the desired period in its…
If I replace an existing window on my business website with a new window replacement service page, can Matomo Analytics help me track how visitors interact with the updated page? I also want to understand whether Matomo can identify changes in visitor behavior, page views, bounce rates, and conversion rates after the replacement. Is there any recommended configuration or tracking setup to compare the p
I’ve seen similar issues with Matomo integrations, and sometimes the problem is related to plugin compatibility or tracking configuration. It’s worth checking whether the WooCommerce tracking data is being recorded correctly and whether the plugin is compatible with your Matomo version. Hopefully, you can get it working without having to switch integrations.
You can already do that per site: Privacy > Anonymize data lets you pick one site and a date range. And for old raw logs there’s core:delete-logs-data with --idsite, works fine from cron.
Hi, for the notes part, Matomo already has that built in: annotations on the evolution graph. Click the small icon under the chart, add a note to a date (campaign start, redesign, tracking change) and it shows up for everyone looking at that report. Much easier than a separate doc, and it’s right there when you’re staring at a spike.
Hello everyone, I am new here and just starting with Matomo. I run a small Indonesian birthday wishes site and I would like to understand which greeting pages visitors read most, and how to set up a simple goal for visitors who reach a greeting page and stay to read it. What is the best beginner-friendly way to do that in Matomo, and are there any common setup mistakes I should avoid? Any tips would be much appreciated. Thank you!
I would recommend running a single Matomo instance on your main account and adding each client’s website separately. It will make management, updates, backups, and maintenance much easier than maintaining individual installations for every client. You can also create separate user accounts and assign permissions so each client can access only their own website’s analytics. Just make sure you configure proper access controls, backups, and resource limits as your client base grows. If you…
I ran into the same confusion, and what worked for me was fixing my reporting periods instead of sliding the dates around. I compare full weeks with full weeks and full months with full months, and I use the previous period comparison so I am always looking at the same length of time. I also keep a short note of anything that changed on the site, like a campaign or a redesign, because that has saved me from misreading a spike more than once.
I ran into the same wall when I needed to clear archived data for just one of my sites, since the deletion options in Matomo act on the whole instance rather than a single site. What worked for me was invalidating just that site’s archives and letting the archiver rebuild them, after taking a full database backup first since the delete is permanent. It took a while to re-archive on my busier site, but it kept the other sites’ data untouched.
Steve Wilkinson: Hi everyone, I’ve been using Matomo for a while, and I still come across features that I didn’t realize could make analysis much easier. I’m curious what’s one Matomo feature you think is underrated or doesn’t get enough attention? It could be a report, segment, Tag Manager feature, goal tracking, custom dimensions, heatmaps, scheduled reports, or anything else that has genuinely improved your workflow. I’d love to hear what features have made the biggest difference for you and…
For me it is scheduled reports. I set up a weekly email summary for myself and I stopped logging in every day just to check the same numbers. I also agree with the custom segments replies, as splitting out returning visitors showed me a very different picture from the overall traffic.
I ended up going the Tag Manager route for this on my own WordPress site and it worked well for me. With adaptive tracking, visitors who decline still show up as basic cookieless page views, and once someone accepts you get the full tracking back. It took a bit of fiddling to get the Complianz triggers right, but after that it just ran in the background.
Hi Umar and cartergray24, thank you both, this is exactly what I needed. I am going to start with the simplest route Umar suggested, a goal that triggers when someone reaches the thank-you page after the booking form. That way I can see which service and area pages actually lead to a quote request, without any extra code. If the thank-you page does not work for some reason, I will use Tag Manager to fire an event on the form submit instead, and set that event as the goal, like cartergray24…
Use a Matomo event to track successful form submissions and set it as a goal. This will show which pages generate quote requests without collecting personal information. Keep tracking simple and privacy-friendly.
When running heavy client-side geometric modeling and CAD file parsers in the browser (such as WebAssembly builds of OpenCASCADE or Three.js B-Rep tessellators), client-side memory exhaustion (WASM OOM) and non-manifold topology exceptions often occur silently on edge devices. To monitor client-side CAD engine health in compliance with strict industrial data privacy standards (without placing tracking cookies on customer engineering drawings), Matomo can be configured for cookieless event…
I set this up the same way for a small service site I look after. The simplest route is a goal that triggers when someone reaches your thank-you page after the form, which tells you exactly which service and area pages led to a quote without any extra code. If your form does not have a thank-you page, use Tag Manager to fire an event on the form submit instead, and either way keep names and email addresses out of the URLs and event labels so the goal stays privacy friendly.
I run a small property inspection business in Birmingham, and our website has service pages, area pages, and a booking form where visitors request a quote. Right now I can see page views in Matomo, but I cannot tell which pages actually lead to a quote request. What is the best way to set this up for a small team? Should I use a goal for the form submission page, or track the form submit as an event? And how do I do this without collecting personal data, since we want to keep the setup…
Managing analytics across multiple websites can get complicated, especially when each site has different privacy requirements. I think having website-level data retention and deletion controls would make Matomo much more flexible. It would also help website owners maintain GDPR compliance without affecting data from their other websites. Has anyone found a reliable workaround for this?