Skip to main content

Storefront analytics forwarding: send subscription widget events to your tracking tools

Forward subscription widget events to the Google Analytics, Google Tag Manager, and Meta Pixel already on your storefront. What is sent, what is never sent, and how to verify it.

What is storefront analytics forwarding?

Storefront analytics forwarding connects your Appstle subscription widget to the tracking tools you already use on your storefront. When a shopper interacts with the subscription widget on a product page — loading it, choosing a subscription, changing the delivery frequency, or moving to add to cart — Appstle sends a matching event to your analytics and advertising tools so those actions appear in the same reports you already rely on.

Everything happens in the shopper's browser. Appstle does not install any tracking tools for you; it simply hands each event to the tools you have already set up.

Where to find it

  • Open Widget & Customer Portal > Subscription Widget in the Appstle admin.

  • Find the Storefront analytics forwarding panel and turn on Forward events.

  • Save your settings. The change applies to your live storefront within a few minutes.

The toggle is off by default, so nothing is forwarded until you switch it on.

Which tools it works with

Appstle forwards events to the tools that are already installed and active on your storefront:

  • Google Analytics (GA4 / gtag.js) — events are sent with gtag('event', ...).

  • Google Tag Manager — events are pushed to the dataLayer, so you can build triggers and tags around them.

  • Meta (Facebook) Pixel — events are sent as custom events with fbq('trackCustom', ...).

  • Custom scripts — anything that reads the dataLayer can pick up the same events.

If one of these tools is not present on the page, Appstle simply skips it — no errors and no impact on your storefront.

What actions are forwarded

Four subscription widget actions are forwarded, each with a clear event name:

  • Widget loadsappstle_subscription_widget_initialised

  • Subscription selectedappstle_subscription_plan_selected (and appstle_subscription_plan_deselected when a shopper switches back to one-time)

  • Frequency changedappstle_subscription_plan_changed

  • Add to cart intentappstle_subscription_add_to_cart_intent

What information each event includes

Each event carries the product context so you can segment and report on subscription behavior:

  • Product ID, title, and handle

  • Variant ID and title

  • Selling plan (subscription) ID and name

  • Purchase option — subscription or one_time

  • Price, currency, and quantity

  • The action name and the surface it came from (the product-page subscription widget)

What is not sent

No customer names, email addresses, or payment details are ever forwarded. Appstle only shares the product, variant, selling plan, price, and action details, and only with the tools already running in the shopper's browser.

Good to know

  • Forwarding only happens while the toggle is on. Turning it off stops new events immediately.

  • Appstle does not set up Google Analytics, Tag Manager, or the Meta Pixel for you — those need to be installed on your store first.

  • Repeated identical actions within a very short window are de-duplicated, so your reports are not flooded by, for example, the widget loading more than once on the same page.

  • The feature is built to fail safely. If forwarding ever cannot run, it never blocks the subscription widget, add to cart, or checkout.

How to confirm it is working

  • In Google Analytics, open the realtime or DebugView report and watch for the appstle_subscription_* events while you interact with the widget on a product page.

  • In Google Tag Manager, use Preview mode and look for the events arriving in the dataLayer.

  • For the Meta Pixel, use the Meta Pixel Helper browser extension and look for the custom events.

If you do not see events, confirm the toggle is on and saved, that your tracking tool is installed on the product page, and that you are testing on a product that shows a subscription widget.

Did this answer your question?