User Interactive Website Tour
Interactive website tours make navigation easier for new visitors. Morocco Fun Tours could use this feature to guide users through tour packages, destinations, and booking steps.
Posts from every feed QUEST has found across the web — blogs, news, podcasts, channels and more.
Interactive website tours make navigation easier for new visitors. Morocco Fun Tours could use this feature to guide users through tour packages, destinations, and booking steps.
That’s an interesting optimization to consider. Saving around 600 MB on a table this large could make a noticeable difference. I’d be curious to know if anyone has tested the change in production and whether it caused any issues with existing Matomo installations.
I run a small single-page site built with a static generator and I’m setting up Matomo to track how people interact with the outbound links in my resource lists. The page doesn’t reload, so I’m unsure how reliable the default outbound link tracking is when content is swapped dynamicly rather than served fresh. My concern is that clicks on links added after the initial load might not be recorded, and I’d end up with a partial picture of what visitors actually use. I’ve been reading third-party…
Microsoft Exchange Outage – Alternative Support Channels A Microsoft Exchange outage can interrupt email services and make it difficult for customers and businesses to communicate with their support teams. When email is temporarily unavailable, it is important to have alternative communication channels so that customers can continue receiving assistance without unnecessary delays. There are several ways to contact a support team during a Microsoft Exchange outage. One of the best alternatives…
I recently faced a similar situation while working on a WordPress website for a window replacement business I wanted to understand how many visitors were viewing service pages, such as window replacement and installation pages, even when they declined statistics cookies through the Complianz plugin. Is there a way to use Matomo’s cookieless tracking or Adaptive Tracking to collect basic, privacy-friendly pageview statistics without tracking visitors through cookies? I would appreciate any…
Thanks for the info, the message cleared after a refresh and was a one-off so no further action is required. Best regards
Hello, that warning means Matomo tried to serve the merged core JS from tmp/assets but the file wasn’t there at that moment. Usually it’s a one-off when the tmp folder gets cleared or regenerated at the same time, for example after an update or a cache clear. If it only happened once I’d run ./console core:clear-caches and reload so it rebuilds the file. If it comes back, check that tmp/ is writable by the web user and that no cron or ephemeral /tmp is wiping it.
Grouping on the whole table is too heavy, so maybe just look at the newest slice, like rows with an idaction above the max id minus a million. If a few URL patterns repeat there (session IDs or search params), you will see it fast and can exclude them in the site settings.
I did a similar move last year and the thing that saved me was the real-time visitor log. Before I switched DNS I clicked through every page on the new build and watched the log to make sure each pageview and goal fired exactly once. It caught two buttons that were firing twice before any real traffic hit it.
Hi, I’m an individual PHP developer in Nepal and I’d like to sell a premium plugin on the Matomo Marketplace. The shop FAQ says to get in touch, but I’ve read that the contact form doesn’t always get a reply, so I’m asking here. Could the marketplace team tell me: What is the revenue share for third-party sellers? How are sellers paid: bank transfer/SWIFT, Payoneer, or Wise? Can an individual in Nepal sell and receive payouts? Which ID documents do you accept? I have a Nepali citizenship…
Regarding the engineering workflow and setup considerations for Error in Matomo for Wordpress: 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 Online STEP to GLB Mesh Converter. Hopefully this reference proves useful for the workflow discussed here.
When migrating from Framer to another hosted/no-code builder while keeping Matomo goals and campaign attribution intact, two specific failure modes usually account for missing or duplicated conversions: Client-side navigation (SPA route changes) vs. hard reloads: If the new builder handles route transitions via client-side history push rather than full document loads, a static Matomo tracking snippet in global custom code only fires trackPageView on the initial landing page. You need an MTM…
Before you truncate anything, check whether the newest rows are mostly one noisy parameter, since a single session id in every URL can bloat this table fast. Once those parameters are excluded, shorten the raw log retention and run the delete logs command again, then check the orphaned rows are actually gone before you touch the table by hand.
Following up on Choosing a no-code site builder that works well with Matomo tracking — when debugging this in production engineering and automated CI/CD pipelines, two deterministic checks help isolate whether the bottleneck comes from schema serialization or runtime state: Verify Object Graph & Symbol Table Serialization: Inspect how persistent entity handles, dictionary pointers (Xrecord / AcDbDictionary), and coordinate transforms are serialized before downstream execution. Keeping…
I moved a small site to a no-code builder and kept Matomo working, but only because the builder let me paste custom code into the site-wide header so the tracker loads on every page. Before I switched, I checked that the builder really puts that code on all pages, not just the homepage, and I tested a goal end to end after publishing. My advice is to keep the same Matomo site ID and goals, and watch the real-time visitor log on day one to confirm every page is being tracked.
I run the website for a small nonprofit in Little Rock and handle our Matomo setup myself. We are considering moving to one of the newer no-code site builders so staff can edit pages without me, but I am worried about tracking. Our current setup lets me add the Matomo container code directly to the page template, and I rely on goals and event tracking for donation form submissions. With some hosted builders, custom scripts are limited or pushed into a settings field I cannot fully control, and…
I run a small nonprofit site in Boston that started on Framer and is now being rebuilt on Wix Harmony, and I need to keep our Matomo goals and campaigns working through the switch. The Framer side was straightforward because I could drop the tracking code into the site settings, and event tracking on buttons behaved the way I expected. With Wix Harmony, I am less certain how the tracking script interacts with its app builder features and whether custom events still fire on dynamically loaded…
One important distinction: Privacy > Anonymize data changes how new visits are stored; it does not delete existing raw logs or archived reports. For a single site, core:delete-logs-data --idsite=... --dates=... can remove raw log rows, but aggregated archives may remain until you invalidate that site’s archives (for example with core:invalidate-report-data --sites=...) and let the archiver rebuild. Back up first. That still is not a one-click per-site erase, so a feature request for…
If you go the truncate route, don’t truncate only log_action. Old rows in log_visit/log_link_visit_action still contain idaction references, and after AUTO_INCREMENT resets those IDs can point at unrelated new actions. For a true fresh start, clear the raw log tables together (after backup), keep the archive_* reports, then reimport. You’ll lose re-archiving, segments and transitions over old raw data, but archived reports should remain. Test on a copy first.
pkid is the visitor ID cookie and defaults to 13 months (393 days); pkses marks an active session and defaults to 30 minutes. In Matomo you can adjust these under [Tracker] in config.ini.php using cookie_expire (days) and cookie_session (minutes), shorten them, or disable tracking cookies entirely. Whether that meets GDPR also depends on your consent/legal basis, so confirm the compliance side with counsel.
Page views being higher than unique visitors is normal, since one visitor usually opens several pages. It only becomes a concern if the gap is extreme, which can point to a tracking code firing twice. For SEO, I mostly check Behaviour > Entry Pages and Acquisition > Search Engines. For bounce rate, open Behaviour > Entry Pages and sort by the Bounce Rate column, since the landing page is where it matters most. For dashboards, the built-in Dashboard lets you add widgets like Visits Overview and…
This sounds like an issue with orphaned action records. I’d check Matomo’s database cleanup options and ask support whether log_action requires a separate cleanup process.
I’d recommend keeping the existing Matomo site ID during relaunches and updating its tracking configuration. That way, historical data stays together without needing to merge sites.
Try reconnecting the Matomo plugin and checking that tracking is enabled in WordPress. The 404 errors might be caused by broken links or a plugin compatibility issue.
Have you checked whether the API is storing the password in the format Matomo expects? It may be worth testing with the official UsersManager API documentation.
Thanks for the update!
You could use custom dimensions to track memory usage and performance metrics alongside events. Keeping the data anonymous and avoiding sensitive file details is also important.
You can check Matomo’s official cookie consent documentation. It should explain the correct cookie names and setup for integrating it with Real Cookie Banner.
You may want to check Matomo’s cookieless tracking settings. It can help collect anonymous page views without storing user-identifiable data for visitors who decline cookies.
It might be a limitation of the Custom Reports plugin. I’d suggest checking with Matomo support to confirm whether this report can be accessed through the API or connector.