Hi Members,
I recently installed Mautic 5 on my server and connected it with my website so that I can track visitor activity and use that information for future automation. The Mautic installation itself completes successfully, and I can log into the Mautic dashboard and access the normal administrative sections without any obvious installation error. I have also added the Mautic tracking code to the website and confirmed that the relevant pages are loading the tracking script when I inspect the page source and browser requests. The problem is that visitor activity is not being recorded consistently after the installation. Some visits and interactions appear to reach Mautic correctly, while other visits from the same website do not result in the expected contact activity or page-hit information. This makes me unsure whether the issue is related to the Mautic 5 tracking configuration, the way the tracking requests are being processed by the server, or something specific to the installation environment. I am not dealing with a situation where Mautic is completely inaccessible or where the tracking code is entirely missing; the important issue is that tracking works intermittently, which makes it difficult to trust the visitor data being collected from the website.
I have already checked the website integration several times because I wanted to make sure that the tracking code was actually present on the pages where visitor activity should be monitored. The same general tracking implementation is being used across the website, and when I inspect the browser developer tools, I can see the tracking-related request being generated during testing. However, the corresponding activity does not always become visible in Mautic afterward. In some cases, a test visit eventually appears as expected, while another visit performed under seemingly similar conditions does not appear in the contact timeline or visitor information. I have allowed some time between testing and checking the Mautic dashboard because I understand that server-side processing may not necessarily happen at the exact moment the browser sends the request. Even after waiting, though, the results remain inconsistent. This is why I am starting to suspect that the problem may be somewhere in the Mautic 5 installation or its server-side processing rather than simply being a browser display issue. I would like to understand which Mautic components are responsible for receiving and processing website tracking requests and how I can verify that those components are operating correctly after installation.
The installation is running as a normal Mautic 5 instance on my own server, and I am trying to troubleshoot it without making several unrelated configuration changes at once. The website and Mautic installation are reachable through their expected URLs, and I have checked that the tracking endpoint being used by the website points to the correct Mautic installation. What I have not yet been able to establish is whether every tracking request reaching the server is actually being processed by Mautic. A request can appear in the browser’s network panel without necessarily telling me what happens after it reaches the server, so I would like to know which Mautic logs or server logs should be checked when investigating missing tracking activity. I am particularly interested in whether Mautic 5 has specific requirements around scheduled tasks, queue processing, or other background processing that could affect when tracking information becomes available. I do not want to assume that the problem is caused by cron or background jobs without evidence, but I also do not want to overlook an installation requirement that is necessary for website tracking to work reliably. If there is a standard post-installation checklist for verifying that Mautic 5 is correctly processing website tracking requests, that would be very useful.
Another part I am trying to understand is the relationship between the tracking request received by the Mautic installation and the contact activity eventually displayed in the dashboard. During testing, I can generate activity from the website and observe the corresponding request leaving the browser, but I do not always see the expected result inside Mautic. Because the installation is new, I want to make sure that the server environment is correctly handling the Mautic application rather than assuming that the website integration is at fault. I have checked the basic webserver configuration and confirmed that the Mautic application can serve its normal pages, so the installation is not generally unavailable. The problem seems much more specific to processing website tracking data. I am wondering whether there is a particular PHP configuration, Mautic 5 dependency, database permission, or scheduled process that needs to be verified for tracking to work consistently. I also want to make sure that the Mautic cache is not causing an old configuration or tracking behavior to remain active after installation changes. If there are recommended Mautic commands for clearing cache, checking application health, validating dependencies, or confirming that the installation can communicate properly with its database, I would appreciate knowing which checks should be performed before making any deeper changes.
For troubleshooting, I am trying to reproduce the behavior using controlled tests rather than relying on normal visitor traffic. I open the website in a clean browser session, visit the pages where the Mautic tracking code is installed, perform the same basic interactions, and then check Mautic afterward to see whether the activity is recorded. I compare successful tests with unsuccessful ones and try to record the approximate time of each request so that I can correlate them with the Mautic and webserver logs. The difficulty is that there is no obvious failure presented to the visitor, so the website itself gives no indication that Mautic has failed to process the tracking information. I would therefore like to know which log files and Mautic diagnostic commands are most useful for identifying a tracking request that reached the server but was not ultimately recorded. If Mautic 5 has a specific log entry or error that appears when the tracking endpoint cannot process a request, knowing what to look for would help me narrow this down considerably. I am also interested in whether the installation has any recommended health checks for confirming that PHP, the database, background processing, and the Mautic application are all functioning together correctly after a fresh Mautic 5 installation. My goal is to identify the exact point where the tracking process stops instead of simply reinstalling Mautic or changing server settings without understanding the cause.
Has anyone experienced a similar issue with a fresh Mautic 5 installation where website tracking is technically installed and requests appear to be generated by the browser, but visitor activity is only recorded intermittently in Mautic? I am mainly looking for the correct troubleshooting sequence for determining whether the problem originates in the website tracking request, the Mautic tracking endpoint, the server-side application processing, or the installation’s background processing. Since some tracking activity is recorded successfully, I do not want to treat the entire installation as broken or reinstall everything without first identifying what is different about the requests that are missing. I would especially appreciate guidance on which Mautic 5 logs, console commands, cron or queue checks, PHP settings, and database checks should be performed first when investigating inconsistent tracking after installation. If there is a recommended way to verify that a tracking request has reached Mautic and has been processed successfully from beginning to end, that would give me a much clearer way to diagnose this. The main goal is to get the Mautic 5 installation reliably recording website activity so that I can trust the visitor data and build automations around it, rather than having some legitimate website activity disappear without an obvious explanation. Thanks!