Setup & testing guide

01 — Before you start

Requirements

• A Shopify store on any plan. The Free app tier (Basic Insight) is enough to run and test the core feature — no billing approval is asked for at install.
• No theme changes needed. Revenue Radar has no Theme App Embed; it installs a Shopify web pixel automatically.
• Best tested on a development store. A "Generate test traffic" button in the Overview header only appears there. It writes marked test events for the last 14 days and summarises each of those days at once, which makes the app testable without waiting for real customer traffic. See For reviewers.

02 — One step

Installation

Revenue Radar activates from your Shopify Admin. No code, no developer, and no theme step.

1. Install the app from the Shopify App Store listing and approve the two requested scopes: write_pixels and read_customer_events. No order data is ever requested. You land in the embedded admin, on the Overview page. The default plan is Free (Basic Insight).
2. Nothing else to enable. The web pixel installs itself automatically the first time Overview loads with zero events recorded — there is no Online Store → Themes → App embeds step for this app.
3. Done. As soon as a visitor adds a product to their cart, Revenue Radar has something to measure.

03 — Plans

Configuration

Revenue Radar has no merchant-configurable settings today, so the app has no Settings page. What changes by plan is measurement scope, not behavior:

Basic Insight is not a Shopify billing plan you approve — it is the absence of one, so installing the app never asks for payment up front. Plan changes are reflected automatically through Shopify's own subscription events; this app does not have a separate in-app upgrade flow of its own.

04 — Verify it works

Testing

Producing a measurable event

1. On the storefront, add a product to the cart. Login is not required — Revenue Radar measures Shopify's own pseudonymous visitor ID, not a customer account.
2. Browsing product pages on their own never counts, by design: the pixel subscribes only to product_added_to_cart, cart_viewed, checkout_started and checkout_completed.

Seeing the figures without waiting a full day

1. Figures are summarised once a day, after midnight in the shop's own timezone. An event collected today normally appears in the figures tomorrow.
2. On a development store, Overview → Generate test traffic summarises the last 14 days immediately after writing their test events, instead of waiting.

05 — Shopify App Review

For reviewers

The short version of what to test and where to look. Core features are on the Free plan — no charge needed to review them. Test on a development store, where the test-traffic button below is available.

1. Install and open the embedded admin. The first screen asks you to accept the Terms; nothing is collected before that. After "I accept", with zero events recorded, Overview shows this message. This is intentional, not a broken app:
   Shown verbatim in the app

   "No events yet. Revenue Radar measures from the moment it was installed; it cannot see what happened before that. Measurement starts when a visitor adds an item to a cart: browsing product pages on its own does not produce an event, so an empty dashboard here is normal until then. The first meaningful picture usually takes 3 to 7 days of normal traffic."

2. Produce an event, either by adding a product to the storefront cart yourself (no login needed), or by clicking "Generate test traffic" in the Overview header (development stores only). It writes a marked funnel of cart and checkout events for each of the last 14 days, today included, without touching real data, then summarises each of those days immediately instead of waiting for the scheduled job. It takes a few seconds; the button shows a spinner meanwhile. The confirmation names how many events were written and which days they cover.
3. Read the Overview. The "Last 30 days" figures, the "Revenue loss over time" view, and the bot-traffic comparison are now populated. If you generated test traffic, a "Test traffic included" notice states exactly how many of the shown events are synthetic.
4. Optional — Products page (embedded nav): ranks products by measured lost value the same way. A per-product rate only appears once at least 10 checkouts have started for that product; below that, the count is shown and the rate is deliberately withheld rather than computed from too small a sample.
5. Optional cleanup: Overview → Test traffic included → Clear test traffic removes only the marked synthetic events and summarises the last 14 days again; real traffic on the store is never touched by it.

06 — Compliance

Data & privacy

• No personally identifiable information. The app stores only Shopify's own pseudonymous visitor client ID, a one-way hash of the browser's user agent (never the raw string), and aggregate counters. No customer name, email, phone or address is stored anywhere.
• Minimal access scopes: write_pixels and read_customer_events only — no read_orders, no advanced DOM pixel events. The app never reads a customer-linked Admin object.
• Customer Privacy API: the web pixel is declared for analytics purposes only and does not run for a visitor who has declined analytics tracking.
• GDPR webhooks implemented: customers/data_request, customers/redact, shop/redact. Because no data stored is linked to a customer identity, a data request currently has nothing to compile; a shop redact deletes every row tied to that shop.
• Retention: raw pixel events are kept for 30 days and deleted by a daily job; the daily aggregates built from them (used for the dashboard) are kept.
• Full policies: Privacy · Terms · Cookies.