Quick answer
KitForge attributes revenue when order line items include private _kitforge_* properties added by widgets at add-to-cart time. Manual cart builds or checkout-only discounts may not attribute.
- Attributed revenue requires widget-initiated add-to-cart.
- Inspect order line properties to debug mismatches.
- Widget-only discounts explain checkout price differences for manual adds.
- Added revenue is directional, not a guaranteed uplift metric.
Verify attribution on a test order
Complete a purchase using the widget's add-to-cart button. In Shopify admin order details, inspect line item properties for _kitforge_ prefixes.
If properties are missing, the customer path bypassed the widget — common with direct /cart links or buy-now from non-widget buttons.
When revenue legitimately won't attribute
Same SKU added from collection pages, reorder flows, or POS will not carry widget properties. That is expected — analytics measure widget-driven purchases.
Launch checklist
Reproduce why bundle revenue is not appearing in kitforge analytics on a known product with a clean browser session after confirming the app embed is active.
Confirm variant coverage, mobile layout, and that the discount only applies through the intended path so shoppers are not surprised at checkout.
- Preview the offer on a real product page and on mobile.
- Place a test order that exercises the discount and inventory path.
- Brief support on what is included and what is not.
- Document the success metric before you scale the offer.
Mistakes that quietly kill conversion
Debugging discounts before confirming the widget mounts wastes time. Network responses from the Kitforge offers proxy should be the first technical check.
For “Why bundle revenue is not appearing in KitForge analytics,” keep the page focused on one primary next step. Extra widgets, stacked badges, and unclear exclusions increase bounce more often than they increase AOV.
- Do not hide eligibility rules until checkout.
- Do not bundle unrelated leftovers without a customer story.
- Do not skip mobile QA on choice-heavy widgets.
- Do not launch without a rollback plan for the discount.
How to measure whether it worked
A fix is complete only when the storefront, cart line properties, and checkout total all match the intended offer.
If the metric moves but support volume rises, fix presentation or inventory rules before cloning the offer across more SKUs.
- Attach rate on treated product pages
- AOV and contribution margin after discounts
- Refund or fulfillment exception rate
- Time for a teammate to edit the offer safely
Final recommendation
Align shopper path with widget interaction before expecting analytics revenue. Attribution is a feature of how items enter the cart, not automatic for all bundle SKUs.
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
Can I attribute all bundle SKU sales?
Not automatically. KitForge attributes widget-path purchases. For full-catalog attribution you would need separate reporting outside widget properties.
What should I do before publishing changes related to Why bundle revenue is not appearing in KitForge analytics?
Preview on mobile, place a test order, and confirm inventory and discount behavior match the storefront promise. Only then activate for all traffic.
When is Kitforge Bundles the wrong tool?
If you only need a simple Buy X Get Y or free-gift discount with no product-page merchandising, native Shopify discounts may be enough. Kitforge is built for fixed kits, FBT, and quantity-break widgets with inventory validation.
How long should I wait before judging the offer?
Give the offer at least one to two weeks of normal traffic, or enough orders to see attach rate stabilize. Seasonal spikes can distort a shorter window.