TYPO3 extension

Personalization on TYPO3, without a TypoScript project

Q: How do I install Personyze on TYPO3?

Run composer require personyze/personyze-typo3, then enter your Personyze account ID under Admin Tools → Settings → Extension Configuration → personyze. The tag is live on the next page load, on every front-end page. There is no TypoScript to write and no cache to flush.

Adding a personalization platform to a TYPO3 site normally means a TypoScript change, a deployment, and an agency to do both. The official Personyze extension removes all three: one Composer command, your account ID in one field, and the tag is live on every front-end page — through template changes and TYPO3 upgrades, because it is not part of your templates.

Start Free →Or get it from the TYPO3 Extension Repository

+Personyze

Extension Configuration

composer require personyze/personyze-typo3

Personyze account IDfrom Settings → Tracking Code

saved

Tracking domainsleave empty unless support gives you a value

empty

Front endtag on every page

TYPO3 backendnever tagged

No cache flush. The setting takes effect on the next request — when you first save it and every time you change it.

Why it matters

TYPO3 runs the site. It was never meant to decide what each visitor sees.

TYPO3 is built for structured content and editorial control, and it is very good at both. What it does not do is change a page for the visitor in front of it — the headline for a returning customer, the case study for their industry, the offer for someone who came from a paid ad. That is a different job, and on most TYPO3 sites it ends up as a ticket for whoever owns the TypoScript.

The extension makes that job a setting instead. Once the tag is on the site, every campaign, recommendation and A/B test is built in Personyze and published from there — no deployment, no editor touching a template, and nothing that a TYPO3 upgrade can undo.

What you get

What TYPO3 + Personyze unlocks

One command, one field

composer require personyze/personyze-typo3 and TYPO3 activates it. Then the account ID under Admin Tools → Settings → Extension Configuration, and that is the installation finished.

No cache flush, ever

The setting is read on the request, so saving the ID takes effect on the next page load — and so does changing it later. Most TYPO3 extensions cannot say that. Your CDN or reverse proxy still has its own cache, which no extension can clear.

The backend stays clean

The extension registers in the front-end middleware stack only. The TYPO3 backend is never tagged, so your editors’ own clicks never arrive as site traffic — and error pages are not tagged either.

Everything Personyze does, on TYPO3

Personalize any page by audience, behaviour, source, company or history; recommend content and products; run A/B tests without a deployment; trigger banners, pop-ups and slide-ins from Personyze’s editor rather than from a TYPO3 content element.

How it works

Connect it in four steps

Install it with Composercomposer require personyze/personyze-typo3. TYPO3 activates the extension automatically; there is no TypoScript to add and nothing to include in a template.

Enter your account IDAdmin Tools → Settings → Extension Configuration → personyze. The ID is the number in your Personyze snippet, under Settings → Tracking Code. Leave Tracking domains empty unless support gives you a value for it.

Check the tag onceOpen any front-end page, view source and search for stat-track-lib.js; you should find one block with _S_T.setup( and your account ID. Personyze starts reporting traffic within a few minutes.

Build campaigns in PersonyzeAudiences, banners, recommendations and A/B tests are built and published in Personyze from then on. Nothing goes back into TYPO3, and nothing needs a deployment.

FAQ

Common questions

How do I install Personyze on TYPO3?

Run composer require personyze/personyze-typo3, then enter your Personyze account ID under Admin Tools → Settings → Extension Configuration → personyze. The tag is live on the next page load, on every front-end page. There is no TypoScript to write and no cache to flush.

Which TYPO3 versions does the extension support?

TYPO3 12.4 and 13.4, on PHP 8.1 or newer. TYPO3 11 and older are not supported; on those sites, add the Personyze snippet to your template instead — everything on this page works the same way once the tag is on the site.

Do I really not need to clear the TYPO3 cache?

No, and that is tested rather than hopeful: the account ID is read per request, so it takes effect on the next page load, both when you first save it and when you change it. A CDN, reverse proxy or Varnish in front of TYPO3 keeps its own cache, which TYPO3 cannot clear and neither can we.

Does it add content elements or a feed of TYPO3 pages?

Not in this release. It adds the Personyze tag; TYPO3 content elements and a content feed from TYPO3 pages are planned. Neither is needed for what this page describes — Personyze renders banners, recommendations and tests on the page itself, wherever you place them.

Is the TYPO3 backend personalized too?

No, deliberately. The extension registers in the front-end middleware stack only, so the backend is never tagged. Personalizing a CMS backend is never wanted, and it would report your own editors’ clicks as site traffic.

Where does the extension come from?

Personyze publishes it in the TYPO3 Extension Repository as “Personyze Personalization” (extension key personyze) and on Packagist as personyze/personyze-typo3. Composer is the usual install route.

One command, and TYPO3 starts personalizing.

Install the extension, paste your account ID, and build the first campaign in Personyze the same afternoon. Or book a demo and we will show it on a site like yours.

Start Free →Or book a demo