For ecommerce & performance agencies

Catch revenue leaks before your clients do.

Safeliant runs repeatable browser journeys across your client portfolio and alerts your team when conversion, measurement, attribution or checkout behaviour breaks.

Scan a client storefront See what we prove

Protect more client revenue without manually checking every account.

Free scan, no card, no meeting required.

The revenue journey

The revenue journey your agency is responsible for

Safeliant walks this funnel in one real browser session — accepting the consent banner first, then home → product → add to cart → cart → checkout entry — recording every analytics beacon, error and screenshot per step. It stops at checkout entry: no payment details are entered and no order is ever placed. This Shopify example comes from a reference storefront. Each merchant setup must be assessed separately. On WooCommerce, full checkout-entry coverage is not yet guaranteed; a blocked step is reported as unassessed.

01HomeTested now

Storefront loaded in a real browser; tags, consent, errors and timing recorded.

02ProductTested now

A product page is discovered and loaded; view_item and product schema are checked.

03Add to cartTested now

The add-to-cart control is located and clicked; add_to_cart is checked.

04CartTested now

The cart is loaded and verified to actually contain the product.

05Checkout entryTested now

Checkout is reached and begin_checkout is checked. The run stops here.

06Payment / completed purchaseNot tested now

No payment details are entered and no order is ever placed, so the purchase event itself is not verified.

Steps marked Not tested yet are shown so the picture is complete, not because Safeliant covers them. They are excluded from every finding, and their absence is never reported as a pass.

What a finding looks like

Real findings, with the evidence behind them

Every finding states what was tested, what was observed, and what was expected — so your developer can act on it and your client can see it was not guesswork. Each example below is a real Revenue Guard rule, named by its rule id.

Highevents_missing_value_or_currency

Ecommerce events sent without value or currency

Tested: Walked the storefront from home to checkout entry in one browser session, decoding every GA4, Google Ads, Meta and TikTok beacon into event name, value and currency.
Observed: Some of the ecommerce events recorded during the journey were sent with no value, no currency, or both.
Expected: Every revenue-bearing ecommerce event should carry a numeric value and a currency code.
Interpretation / risk: Value-based bidding and ROAS reporting silently treat these events as zero. Revenue measurement risk — how much it costs depends on the merchant’s actual order data, which a scan does not have.

Criticalcart_empty_after_add

Cart is empty after adding a product

Tested: Located and clicked the add-to-cart control on a product page, then loaded the cart page in the same session and checked whether the product was present.
Observed: The add-to-cart action reported success, but the cart page did not contain the product.
Expected: A product added to the cart should be present when the cart is loaded.
Interpretation / risk: This is a silent failure — the shopper sees no error and simply leaves. Common causes are SameSite cookie policy, a cart token not persisting, or a failed XHR.

Highmissing_add_to_cart_event

No add_to_cart event when a product was added

Tested: Added a product to the cart and recorded every analytics beacon and dataLayer push across that step, mirroring pushes into sessionStorage so events fired just before navigation are not lost.
Observed: The product was added successfully, and across that step no GA4 add_to_cart beacon and no add_to_cart dataLayer push were observed.
Expected: A GA4 add_to_cart event with items, value and currency should fire when an item is added to the cart.
Interpretation / risk: Mid-funnel signal is missing, which degrades both reporting and smart bidding.

Mediumduplicate_ecommerce_event

Duplicate ecommerce events fired in one journey

Tested: Recorded every ecommerce event across a single browse-to-checkout session and grouped them by event name and step.
Observed: The same ecommerce event was observed more than once within one journey.
Expected: Each ecommerce event should fire once per step.
Interpretation / risk: Duplicated mid-funnel events inflate conversion rates and mislead bidding. The usual cause is a theme-level push plus a tag-manager tag doing the same job.

Mediummeta_pixel_funnel_gap

Meta Pixel missing funnel events that GA4 recorded

Tested: Compared the events recorded by GA4 against those recorded by the Meta Pixel at each step of the same journey.
Observed: The Meta Pixel is installed but did not fire one or more funnel events that GA4 did record.
Expected: Both vendors should record the same funnel steps for the same session.
Interpretation / risk: Meta optimisation and audience building are running on partial signal. Cross-vendor comparison is possible here because both were observed in one session.

Hightags_fire_before_consent

Tracking fired before any consent interaction

Tested: Loaded the storefront with a clean profile and recorded all outbound tracking beacons BEFORE any interaction with the consent banner.
Observed: Advertising or analytics beacons were sent before consent was given.
Expected: Non-essential tracking should not fire until the visitor has made a consent choice.
Interpretation / risk: Platforms increasingly discard or discount pre-consent hits, so this degrades measurement quality as well as being a consent defect.

Why there is no euro figure on any finding. Safeliant reports revenue measurement risk, because a scan can prove that a conversion event did not fire — it cannot prove how many orders that cost you without your actual order data. Findings that state a number you cannot verify are worse than useless in front of a client.

Independent layer

This is assurance, not another tracking install

Safeliant does not install tracking and does not replace any of these. It is the independent layer that keeps asking one question none of them answer about themselves: does the revenue journey actually work right now? It answers by walking the funnel and reading the beacons that actually fired.

Does the revenue journey actually work right now?

Still makes sense if the account already runs

Native Shopify integrations
Elevar
Littledata
Analyzify
Google Tag Manager
Server-side GTM
Meta Conversions API

Journey coverage by platform

ShopifyLIVE

Real browser journey in one persistent session
Product discovery and purchasability assessment
Add to cart, verified by cart state rather than by the click
Cart page recognised from the storefront's own markup
Checkout entry through the cart's own checkout control
Measurement and ecommerce event analysis across the journey
Consent state and tag-timing analysis
Screenshots, network and interaction evidence for every finding
Portfolio checks across many client stores

Validated end to end against a live Shopify storefront on 2026-08-22 and again on 2026-08-23: add to cart moved the cart from 0 to 1, and checkout entry was reached by pressing the cart's own control, landing on a tokenised Shopify checkout. No payment details were entered and no order was placed.

WooCommerceLIMITED

Platform detection and passive storefront analysis
Measurement, consent, schema and page-error findings
Journey attempted wherever the storefront serves the scanner

The full add-to-cart through checkout-entry journey is not yet guaranteed on WooCommerce.
A store whose WAF, bot protection or rate limiter refuses the scanner is reported as unassessed. It is never reported as broken, and its absence of findings is never a pass.

Detection and passive analysis run against live WooCommerce storefronts. The add-to-cart primitive has succeeded on a live WooCommerce store; a complete journey through to checkout entry has been proven against reproduced storefront fixtures but not yet against a live WooCommerce store, because every approved candidate refused the scanner or degraded first.

No guessing

What Revenue Guard checks today

Every item on the left is a rule in the Revenue Guard engine or a shipped platform behaviour, and anything constrained says so. Current coverage is on the right.

Available now

No web analytics detected on the storefrontno_analytics_detected
GA4 absent while other analytics is presentmissing_ga4
Deprecated Universal Analytics tag still installeduniversal_analytics_still_present
Multiple GA4 measurement IDs on one pageduplicate_ga4_properties
Multiple GTM containers loadedduplicate_tag_manager_containers
Meta Pixel loaded without a resolvable pixel IDmeta_pixel_missing_id
GTM present but no dataLayer activityno_datalayer
Google Ads traffic with no conversion tag on the pages sampledLimitedads_spend_without_conversion_tag
Only fires when the landing URL carries paid-click parameters such as gclid, and only for the pages actually sampled.
Ecommerce events sent without value or currencyevents_missing_value_or_currency
No view_item event on the product pagemissing_view_item_event
No add_to_cart event when a product was addedmissing_add_to_cart_event
No begin_checkout event at checkout entrymissing_begin_checkout_event
Duplicate ecommerce events inflating reported performanceduplicate_ecommerce_event
Meta Pixel missing funnel events GA4 did recordmeta_pixel_funnel_gap
No product page reachable from the storefrontproduct_page_not_discoverable
Add-to-cart control not found or not clickableadd_to_cart_control_not_found
Cart empty after a successful add — silent revenue failurecart_empty_after_add
Checkout entry could not be reachedcheckout_unreachable
JavaScript errors on the storefront and inside the funneljs_errors_during_funnel · js_errors_on_homepage
Failed or 4xx/5xx script and XHR requestsfunnel_request_failures · broken_asset_requests
Slow storefront load and slow funnel stepsslow_funnel_step · slow_first_load
No cart route foundno_cart_detected
Journey steps the scanner could not measure, reported as coverage gapsjourney_coverage_gap
Tracking fired before any consent interactiontags_fire_before_consent
Advertising pixels present with no consent manager detectedno_consent_manager_eu_stack
Consent accepted but tracking still did not fireLimitedno_tracking_after_consent_accepted
Scanned from a single country, so a geo-gated consent banner shown only in other regions would not be observed.
Per-step screenshots and network evidence captured for every finding
Every finding states what was tested, observed and expected
Portfolio scanning — many clients, one ranked report
Cross-client patterns — issues shared by several clients
Change-only alerting between runs
First-seen, resolved and regression tracking across scans
Suppress a finding you have judged out of scope
Scheduled scans you run in your own CI or cronLimited
Safeliant generates the cron, GitHub Actions or systemd schedule; the schedule runs on infrastructure you control. There is no hosted scheduler yet.
Alert delivery to Slack/Teams-compatible webhooks, a digest file, or stdoutLimited
Webhook, file and stdout only. Safeliant does not send email.
Platform detection — Shopify, WooCommerce, Magento and others
Product structured-data completeness for AI and search discovery

Preview — being validated

AI Commerce — how AI shopping assistants describe and recommend a store

Preview. The structured-data and sitemap checks that feed it run today, but the assistant-response testing has not been validated against a live model provider, so its output is not presented as a production finding.

Current coverage

Shopify revenue journeys are validated through checkout entry. Safeliant does not place customer orders. WooCommerce journey coverage is more limited today, and some storefronts may also restrict automated access; those checks are reported as unassessed rather than passed or failed.

If a specific capability decides whether Safeliant is useful to you, ask us and we will tell you honestly where it stands.

Start with one client site

The free scan checks one client URL for consent-evidence issues. Revenue Guard walks the purchase funnel across your portfolio, and you run it repeatedly from your own CI, cron or server. For a price, get a quote — five questions, priced on how many client accounts you manage, and no sales call.

Scan a client site Get instant quote

No card for the scan. No meeting to start a plan. Prefer to talk it through first?