Quick answer
KitForge analytics tracks added revenue as sales attributed to bundle offers when shoppers interact with widgets and complete purchases through the KitForge discount path. It helps merchants isolate bundle campaign performance from overall store trends.
- Added revenue = bundle-attributed sales in KitForge analytics.
- Requires widget add-to-cart path with line properties.
- Distinct from Shopify total sales reporting.
- Use per-offer metrics to compare kit vs FBT vs QB performance.
Why attribution requires the widget path
Widget-only discount design means discounts and analytics attribution align when shoppers use KitForge widgets. Manual add-to-cart of the same products may not receive bundle pricing or attribution — by design.
Troubleshooting empty analytics
Confirm app embed active, offers live, and shoppers adding via widget. Check that theme cart preserves line properties through Ajax cart drawers.
Allow 24 hours for dashboard population after first live orders.
Launch checklist
Apply what is added revenue in kitforge analytics when briefing your team so admin settings and storefront copy use the same language.
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
Mixing terms — kit, bundle, BOGO, free gift — creates wrong expectations for shoppers and for support.
For “What is added revenue 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
If the definition is clear, a new teammate can configure the offer without asking which Shopify surface owns the rule.
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
Added revenue in KitForge analytics shows bundle-specific lift — track it per offer, ensure widget ATC path works, and compare campaigns without conflating total store sales.
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
Why is added revenue lower than expected?
Shoppers may add products manually outside the widget, stripping attribution. Theme cart issues can also drop properties before checkout.
Does added revenue include shipping and tax?
Attribution focuses on product revenue from bundle lines — confirm exact definitions in your KitForge analytics dashboard labels.
What should I do before publishing changes related to What is added revenue 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.