Figgle — A/B Testing For Conversions Wordpress Plugin - Rating, Reviews, Demo & Download
Plugin Description
Figgle tests headlines, calls to action, forms, images, and content sections. It
can identify opportunities and prepare variants, but it never launches a draft
automatically: a user with the appropriate Figgle role must review and start
each test.
Figgle is a subscription service with a free tier. The plugin is the WordPress
interface to that service, so a Figgle account is required to connect a site.
The plugin interface is currently available in German.
What Figgle provides
- Controlled A/B tests with no third-party cookies and no cross-site advertising profiles.
- A main browser script of approximately 16 KB Brotli, size-locked at build time. Optional features load as separate small chunks, and only when a running test needs them.
- A synchronous
<head>installation for anti-flicker behavior; an asynchronous fallback remains available for platforms that require it.
What this plugin does
After an administrator explicitly approves the connection, the plugin links one
WordPress site to one Figgle site and adds the Figgle browser snippet to the
page <head>. The PKCE verifier, one-time authorization token, and revocable
credential remain in the WordPress backend and are never exposed to browser
JavaScript. Tests are managed at app.figgle.de and are
never started automatically.
The plugin does not provide heatmaps, session replay, cross-site tracking, or an
advertising profile. It is not a legal-compliance guarantee. Consent and legal
requirements depend on the enabled Figgle features and the website owner’s setup.
External services and privacy
Before the administrator clicks Connect to Figgle, the new connection flow
sends no data to Figgle. The intentionally selected manual fallback begins when
the Figgle Site ID is saved.
Requests your WordPress server makes
Starting the connection sends the site origin, a random installation ID, a PKCE
challenge, the plugin version, and a callback URL of this site to
https://api.figgle.de/, and opens https://app.figgle.de/ in your browser so
you can approve the domain. No WordPress account, email address, or post content
is part of that request.
While a site is connected, the WordPress server also contacts https://api.figgle.de/.
Some of these requests carry a signed installation credential: the once-a-day
connection check, reading the conversion goals, and — only with the WooCommerce
integration enabled — reporting order and refund events. Disconnecting or deleting
the plugin sends one final signed request that revokes the credential.
The other requests go to public Figgle endpoints and carry no credential: the server
refreshes the embedded configuration for synchronous mode and reads this site’s
public configuration from https://api.figgle.de/api/config/<your-site-id> to check
whether a sorting test is running; it verifies the installation when you press the
button on the settings screen; and, for the WooCommerce product-sorting feature, it
verifies a short-lived edit token.
The WooCommerce product-sorting experiment additionally makes your server load a
page of your own shop — a loopback request to your own site, not to Figgle — to
check whether your page cache serves both test groups the same product order.
Requests the visitor’s browser makes
After connection, the browser loads the snippet from https://cdn.figgle.de/ and
talks to https://api.figgle.de/. Depending on the enabled configuration, it can:
- send approved exposure, conversion, and technical events;
- look up the approximate visitor location, for location-dependent tests or content;
- store the entries listed below.
In the default consent mode, exposure and conversion events and location lookups
happen only after the visitor has agreed in your cookie banner.
Before or without consent, the browser sends at most two anonymous signals: a
sampled technical status (“loaded” or “error”, with the snippet version) and,
only if you switch it on, one anonymous page count with a coarse referrer and
device class. Neither contains a visitor ID or the page address, nothing is
stored on the device for them, and Figgle keeps only daily totals.
If the Google Analytics 4 link is switched on for your site in Figgle, the
browser also adds an experience_impression event (test and variant ID and
name) to your page’s own dataLayer for each measured exposure. Figgle sends
nothing to Google itself; whether that event leaves the page is decided by your
Google Analytics or Google Tag Manager setup and its consent settings.
Every one of these requests carries technically necessary connection metadata,
such as the IP address and the browser’s user agent.
What Figgle stores on the visitor’s device
This list is complete for the snippet this plugin loads. None of these entries is
readable by another website: Figgle sets no third-party cookies and builds no
cross-site profiles. Which entries actually appear depends on what is switched on
for your website.
In the default consent mode, Figgle shows variants and content rules from the
first visit but writes the measurement entries below (_fg, _fgp, _fg_srv,
_fg_sid, _fg_sticky, _fg_apply, _fgq…) only after the visitor has agreed
in your cookie banner. Without consent, existing _fg_srv and _fg_plp cookies
are deleted.
Consent bookkeeping (consent mode only):
_fgcm(browser storage, 13 months): set only after the visitor has agreed,
so that measurement can start on the next page even when your cookie banner’s
choice cannot be read immediately. Contains the date and the detected banner
tool, no visitor data. Deleted when the visitor refuses or withdraws consent._fgdel(browser storage, only after a withdrawal whose deletion request could
not be delivered): keeps the visitor’s pseudonymous ID and its secret only so
that the deletion can be retried on the next visit. Removed once the deletion
succeeded or after repeated failed attempts.
Recognising a returning visitor:
_fg(browser storage, stays until the visitor clears their browser data; some
browsers delete it automatically after a longer period of inactivity): a
random, pseudonymous ID so a returning visitor keeps seeing the same variant
instead of a different one on every visit._fgp(browser storage, stays as long as_fg): a random secret belonging to
_fg. It leaves the device only when the visitor personally requests a data
export or deletion, where it proves that the request is theirs._fg_srv(first-party cookie, lifetime one year,SameSite=Lax,Secureon
HTTPS): mirrors_fgso conversions reported by your server can be attributed
to the same visitor. It is set as soon as the site has an active server
credential — the secure WordPress connection creates one, so this applies to
every connected site, not only to shops. Cleared once the credential is revoked._fg_sid(session storage, deleted when the browser tab is closed): a random
ID that groups the events of a single visit.
Approximate location, only on websites that use location-dependent tests or content:
_fgc(browser storage, 30 days): the approximate location Figgle determined
for this visitor — city, region name, region code, and the time it was stored.
A later visit over a mobile connection, where the location cannot be determined
reliably, then still shows the matching regional content. This entry stays on
the device and is never sent back to Figgle.
Which variant a visitor sees, and showing it without flicker:
_fg_plp(first-party cookie, lifetime 30 days,SameSite=Lax,Secureon
HTTPS): the A/B group of the WooCommerce product-sorting experiment, and only
while such an experiment is running. The cookie is cleared automatically when
the experiment ends._fg_sticky(browser storage, 7 days, one entry per running test): the
variant this visitor was assigned, so the page does not switch between visits._fg_applyand_fg_hide_…(browser storage, 7 days each): the text and
image changes of the last visit, so the correct version appears immediately
instead of the original flashing up first._fg_bm:…(browser storage, no expiry): records which measurement mode this
website uses. Contains no visitor data.
Technical helpers:
_fgq…(browser storage, until delivered): events that could not be sent yet,
for example because the connection dropped. Deleted once Figgle confirms
receipt._fg_cart(session storage, 30 seconds): a short-lived copy of the WooCommerce
cart totals, so cart-dependent content rules do not query the shop repeatedly.
Figgle is an external service operated by Sebastian Klenk (Germany); the full
provider details are in the imprint at
https://figgle.de/impressum. The website owner
remains responsible for the legal basis, notices, and consent configuration for its
specific use. A pre-filled data-processing agreement can be generated in the Figgle
dashboard as a DRAFT (account owners only); it is pending legal review and must not
be signed as-is.
Privacy policy: https://figgle.de/datenschutz
Terms: https://figgle.de/agb
Screenshots
One clear task after activation: connect the WordPress site to Figgle.
Explicit domain confirmation in the authenticated Figgle dashboard.
Connection status and focused cache, CSP, loopback, and builder guidance.
Test management in Figgle; no draft is launched automatically.
