Quick answer
An empty KitForge analytics dashboard usually means no active widgets received views yet, no orders carried KitForge line properties, or you are filtering by placement in a way that only affects events — not revenue.
- Preview alone may not populate analytics — use live storefront sessions.
- Attributed revenue requires _kitforge_* line properties on cart lines.
- Placement filters change event views, not order attribution rules.
- Compare attach rate only after meaningful view volume.
Funnel stages KitForge tracks
Typical funnel: widget view → interaction (tier select, add-on check) → add to cart → order. Each stage requires the prior step on a live storefront session.
Admin preview may not fully simulate analytics beacons. Send a test session on the live storefront after activation.
- Views
- Interactions
- Add to cart
- Attributed orders
- Added revenue
Generate your first data
Activate one bundle, enable embed, open the trigger or component PDP in an incognito window, interact with the widget, complete a test order with widget add-to-cart.
Allow a few minutes for order webhooks to attribute revenue.
Final recommendation
Empty analytics almost always means no storefront traffic through active widgets yet. Run one full test purchase before assuming tracking is broken.
If you want this kind of offer to feel native to the buying journey, Kitforge Bundles is built around that exact problem: turning related Shopify products into clearer bundle offers before the shopper reaches checkout.
FAQ
Does KitForge track checkout without widgets?
Revenue attribution is tied to widget-initiated line properties. Manual adds of the same SKUs may not attribute to the bundle offer.