Personyze Wiki Personyze Wiki docs
English
Open Personyze
Docs/ Start Here/ Installing Personyze on TYPO3
Start Here

Installing Personyze on TYPO3

The Personyze extension for TYPO3 12.4 and 13.4 puts the tag on every front-end page from one backend field — no template edits, no TypoScript, no cache flush. Install, configure, verify and troubleshoot.

3 min read Updated 59 minutes ago

The Personyze extension for TYPO3 adds the Personyze tag to every page of a TYPO3 site, configured from one field in the TYPO3 backend. No template edits, no TypoScript, and nothing for a developer to do.

Supports TYPO3 12.4 and 13.4, and needs PHP 8.1 or newer.

Installing

composer require personyze/personyze-typo3

That is the whole installation — TYPO3 activates the extension automatically.

Configuring

  1. In the TYPO3 backend go to Admin Tools → Settings → Extension Configuration.
  2. Open personyze.
  3. Enter your Personyze account ID and save.

Your account ID is in Personyze under Settings → Tracking Code — it is the number that appears in the snippet there (see Activating Personyze on your site).

The tag is live on the next page load. You do not need to clear the TYPO3 cache, and you will not need to clear it when you change the account ID later either.

Why there is no cache flush. The obvious way to add a script in TYPO3 bakes it into the page cache, where a changed account ID would not appear until somebody flushed the cache by hand — so saving the setting would look like it did nothing. This extension adds the snippet as the response goes out instead, on every request, cache hit or miss. The tag always reflects the current setting.

There is a second field, Tracking domains. Leave it empty. It is only needed when one Personyze account tracks several domains, and only with the value Personyze support gives you.

What gets tagged, and what does not

  • Every front-end page of the site.
  • Not the TYPO3 backend. The extension registers itself in TYPO3’s front-end middleware stack only, so the backend is never tagged and your editors’ own clicks are never reported as site traffic.
  • Not error pages. Only a normal, successful HTML page is tagged — a 404 or an error response is left exactly as it was.
  • Nothing at all until an account ID is set. An empty setting means no tag, rather than a tag reporting to account 0.

Verifying

Open any front-end page and view source. You are looking for one script block containing stat-track-lib.js and a _S_T.setup( call with your account ID in it. Then check Personyze — the site should start reporting traffic within a few minutes.

Troubleshooting

I saved the account ID and pages still have no tag. This should not happen: the setting takes effect on the next request, with no cache flush. If it does, check the extension is active under Admin Tools → Extensions, and remember that a CDN, reverse proxy or Varnish in front of TYPO3 has its own cache that TYPO3 cannot clear.

No tag in the TYPO3 backend. That is intended — see above.

The tag is there but Personyze reports no traffic. Check the account ID matches the one under Settings → Tracking Code, and that you are looking at the same account in Personyze.

Did this page answer your question?
Thank you — that goes to whoever maintains this page.
Previous Installing Personyze on Joomla in Start Here