Integrations

One script tag, whatever you run on

Pertento is platform-agnostic by construction: a single tag in the head, an SDK where a test has to run on the server, and nothing to install in your admin.

Integrations

Everything Pertento runs on and reports to

47 platforms, frameworks and tools, in 6 groups: what your storefront is built on, what renders it, and where the numbers go afterwards. Each page says what connecting the two actually involves.

Ecommerce platforms

Client-side on any of them, server-side where you have a backend.

ShopifyAdd the script tag to the theme layout and test any storefront page, whether collection, product, cart or checkout-adjacent, without touching Liquid again.How it connects WooCommerceOne tag in the WordPress header hooks every WooCommerce template, so product, cart and checkout pages are testable without a plugin.How it connects Adobe CommerceClient-side tests across the storefront, and server-side tests through the SDK where the change belongs in the backend.How it connects BigCommerceA script tag in the storefront theme covers every page, with sticky assignment across the catalogue and checkout.How it connects SalesforceClient-side tests on the storefront, and server-side assignment for the decisions that happen before the page is rendered.How it connects PrestaShopOne tag in the theme head covers the catalogue, the cart and the checkout, with no module to keep in step with PrestaShop upgrades.How it connects ShopwareWorks on both Shopware storefronts, the Twig one and a headless build, from the same tag and the same experiment.How it connects WixAdded once through the custom code panel, then variants are built against the published site rather than inside the Wix editor.How it connects SquarespaceOne entry in code injection reaches every page, including pages added later, without touching a template.How it connects

Nordic commerce

The platforms most of our customers already run on.

CentraA headless commerce backend paired with a front end of your choosing. Pertento installs into the front end and tests either side of the API.How it connects LitiumClient-side tests on the storefront, with server-side assignment available where the decision sits inside the commerce backend.How it connects NorceAPI-first, so the tag goes into whichever storefront renders the pages and the SDK covers what the API decides first.How it connects GeinsComposable by design, so Pertento attaches to the storefront you built rather than to the platform underneath it.How it connects

Headless and composable

The front end takes the tag; the SDK decides what the API returns.

commercetoolsThe storefront takes the tag, the SDK decides what the API returns, and one visitor stays one visitor across both.How it connects Shopify HydrogenA React storefront on Shopify, so the tag goes in the document head and variants survive Hydrogen’s client-side routing.How it connects SaleorGraphQL-first, so the storefront takes the tag and the SDK covers anything resolved before the query returns.How it connects MedusaA Node commerce backend with the storefront left to you, so the install is whatever that storefront already does with a script tag.How it connects VendureA TypeScript backend with a separate storefront, so the tag covers the pages and the SDK covers the resolvers.How it connects

CMS and site builders

One tag in the layout, wherever the pages are edited.

WordPressOne tag in the theme header covers the whole site, including pages built by a page builder or assembled from blocks.How it connects DrupalOne tag in the theme’s html template covers every content type, with no module and nothing running in PHP.How it connects UmbracoA .NET CMS with Razor layouts, so the tag goes in the shared layout and is inherited by every page built on it.How it connects Optimizely CMSRunning Pertento on a site built with Optimizely CMS, which is a different thing from Optimizely’s own experimentation product.How it connects ContentfulA content API rather than a renderer, so the tag goes in whichever front end draws the pages Contentful fills.How it connects SanityA content backend with the front end left to you, which is how this very site runs Pertento.How it connects StoryblokComponent-based content, so an experiment can target what a block renders rather than a class name the theme owns.How it connects WebflowPaste the tag into the site-wide custom code head, and test published pages without leaving the visual model Webflow already gives you.How it connects FramerAdded through the site custom code settings, with variants built against the published site rather than the canvas.How it connects

Frameworks and SPAs

Variants survive client-side routing rather than being reapplied per navigation.

Next.jsRender the tag in the root layout so it loads before hydration, and variants persist across client-side route changes.How it connects NuxtOne entry in the app head configuration covers every route, and it lands in the server-rendered HTML rather than after hydration.How it connects ReactA single-page app needs the tag once, in the HTML shell. Variants survive routing rather than being reapplied per view.How it connects VueInstall once in the app’s HTML entry point; targeting is re-evaluated on each route change without reassigning the visitor.How it connects AngularOne tag in index.html covers the whole application, and variants are reapplied as the router swaps views.How it connects SvelteKitThe tag belongs in the app template so it is server-rendered, and assignment carries across SvelteKit’s client-side routing.How it connects AstroStatic HTML on disk, so a variant is applied in the browser and starting or stopping a test costs no rebuild.How it connects RemixThe tag renders in the root route’s head, and the SDK runs inside loaders for anything settled server-side.How it connects

Analytics and tooling

Send exposure events wherever your reporting already lives.

GA4Forward the experiment and variant a visitor was assigned, so every GA4 report you already have can be segmented by the version they saw.How it connects MatomoExposures sent to a Matomo instance you host yourself, so experiment data never leaves infrastructure you control.How it connects Piwik PROConsent-aware analytics with the variant as a custom dimension, which suits regulated and public-sector sites.How it connects Adobe AnalyticsThe variant lands in an eVar or a prop, so outcomes can be read in the reporting the business already trusts.How it connects AmplitudeExposures arrive as an event with the variant as a property, so behavioural funnels can be compared per variant.How it connects MixpanelThe variant is a property on the exposure event, and optionally on the profile, which is a decision worth making deliberately.How it connects SegmentSend exposure events into Segment as a track call, and let your existing destinations fan them out from there.How it connects RudderStackOne exposure event into RudderStack fans out to every destination already configured, without a second integration.How it connects Tag ManagerPush exposure events into the data layer for whichever tags need them, but deliver the Pertento tag itself directly, not through the container.How it connects KlaviyoAttach the variant a visitor saw to their profile, so a campaign can be read against the on-site experience they were given.How it connects SlackAlerts in the channel that already carries the programme: started, stopped, reached significance, or measurement broken.How it connects WebhooksA signed POST to an endpoint you control, for exposures and lifecycle events, when nothing off the shelf fits.How it connects

Apps and connectors

The pieces you install rather than paste: the browser editor, the Shopify app, and the analytics connectors that read your experiments back into the reporting you already use.

Pertento Editor

The Pertento Editor brings real-time on-site editing to your experimentation workflow. Build and preview variants directly in your browser.

Open Pertento Editor

Pertento for Shopify

Connect your Shopify store to Pertento in minutes and unlock real-time experimentation with your actual Shopify metrics. The app syncs orders, revenue, and product data directly to Pertento, giving you accurate, live reporting for every experiment. No custom setup, no code - just a seamless integration that lets you test, optimize, and measure impact using the numbers that matter.

Open Pertento for Shopify

Google Analytics 4

Connect Pertento to Google Analytics 4 and evaluate your experiments using your existing GA4 reporting. The integration sends all experiment events directly to GA4, creates audiences automatically, and lets you analyze performance with the metrics and dashboards you already rely on. Clean data, no manual setup, and full alignment between your experimentation results and your GA4 measurement framework.

Open Google Analytics 4

Matomo

Link Pertento with Matomo to measure experiments using your existing analytics setup.

Open Matomo

Not on the list

If it renders HTML, Pertento can test it

The tag makes no assumption about what produced the page, so the list above is the set we have written down rather than the set that works. Talk to us about server-side and edge delivery, or about a platform you cannot see here.

Ask about your stack Read the install guide