Analytics and reporting
How to track website visitors and clicks
- Open your profile’s Social Links → Web & Domains, then add or select a webpage under Webpage Tracking.
- Enter the full HTTPS webpage URL, then save it. You can use a homepage or a specific page.
- Copy that profile’s snippet and install it once in your website’s global
<head>, so it runs on every page you want to track. Saving a URL in Central Socials does not install the snippet. - Go to Engagement → Webpages to see page previews arranged by URL depth and domain, including your landing pages and drafts. Previews are kept in device memory briefly so revisiting them is faster; Refresh reloads them. Select a connecting line to see starting views, moves to the next page and conversion. Select a webpage to highlight its incoming and outgoing flows and see them in the information panel. Choose Show Site to open a popup containing the webpage and its original tracking controls. Published landing pages use their existing statistics view; drafts show their saved content without publishing. Use Statistics for the full report, choose a screen size, or toggle click positions and exit depth lines. Close the popup with the button at the top right. If a site prevents embedding, use Open statistics on website.
Domains and page URLs
Tracking recognises the registered domain, including its subdomains. For example, a saved URL of https://www.example.com/contact also accepts tracking from example.com and help.example.com. Different customers on shared hosting remain separate websites.
The full saved URL still selects the page to open. Redirects within the same registered domain are supported, and the statistics use the page that actually loads. Metrics are grouped by page path within the tracked website. Unrelated domains are not accepted.
You can save different webpage URLs on the same domain, such as https://example.com/help and https://example.com/contact. Only an identical saved webpage URL is a duplicate. The domain check restricts data to that domain and its subdomains; it does not limit you to one saved page. Use the same profile snippet. Each entry has its own statistics and removal, so changing one does not erase another entry’s data.
Test your tracking snippet
After installing the snippet, enter your webpage URL and select Test tracking. You can test a URL before saving it. The test opens that page in a new tab and waits up to 60 seconds. Click or scroll in the test tab if your website delays scripts until interaction. The tab closes when the check finishes; Cancel test stops the check.
A successful test means the snippet for this profile ran on the opened page and responded. It does not prove every analytics request can be delivered. No response means the snippet may be missing, blocked or delayed; check the final page after any redirect, cookie-consent settings, browser blockers and JavaScript optimisation plugins. The app cannot reliably tell these causes apart. A snippet belonging to another profile is reported separately.
Testing does not save your URL, change installed snippets, reset statistics or disable active trackers. The test tab closes promptly after a response. Like opening the page normally, a test visit may still be counted if tracking starts before the tab closes.
If the statistics toolbar does not appear
Central Socials waits up to 60 seconds for the installed tracker to respond. The toolbar opens as soon as it responds. If the wait expires, check that the snippet is installed on the page that opened and that your browser allowed the new tab.
Some website performance plugins delay JavaScript until the visitor moves their mouse, scrolls, clicks, taps or presses a key on the website. A snippet can be present in the header but still be waiting to run. Interacting with Central Socials does not release scripts delayed on the customer website.
WordPress and Perfmatters
- Install the copied snippet in the global header using your WordPress theme or header/snippet plugin.
- If Perfmatters delays all JavaScript, open Perfmatters → JavaScript → Excluded from delay and add
app.centralsocials.com/api/track/. If you delay only specified scripts, ensure the tracker is not in that list. - Save the settings and clear the website’s page, optimisation and CDN caches where enabled.
- Reload the website, then open statistics again from Central Socials.
The 60-second wait allows more time for loading; it does not force a delayed script to execute. Excluding the tracker from JavaScript delay also lets normal visit tracking start promptly. Visits made before the tracker runs cannot be recovered.