Troubleshooting

The “Size guide” link doesn't appear on a product page

Three causes cover nearly every case. Check them in this order:

1. No guide is assigned to that product

• In the FitKit admin, check the guide's assignment: is this product covered by a product, tag, collection, vendor, or global assignment?
• Remember the priority order: product > tag > collection > vendor > global. The link only shows when at least one published guide matches the product.
• Assigning by tag? Tags are case-sensitive in spirit: make sure the tag on the product is spelled exactly like the one in the assignment.
• On the Free plan, only 1 guide can be published — if the matching guide is unpublished (e.g. after a downgrade), the link won't render. See billing & plans.

2. The FitKit app embed / block isn't active in your theme

• Go to Online Store → Themes → Customize, and check that the FitKit app embed is turned on (puzzle-piece icon in the left sidebar, “App embeds”).
• If you placed FitKit as a block on the product template instead, open the product template in the theme editor and verify the block is still there — theme updates or template switches can drop app blocks.
• Using multiple product templates? The block has to be present on each template whose products should show the guide.

3. You're looking at an unpublished preview or a different theme

• Check the live, published theme in a private/incognito window — not a preview of a draft theme where the embed may be off.

The link appears, but in the wrong place

By default FitKit positions the link automatically near your size selector. On heavily customized themes, auto-detection can land somewhere unexpected. Two fixes:

• Selector mode: in the guide's display settings, switch the position to a custom CSS selector and point it at the exact element you want the link next to (e.g. your variant picker's class). Growth
• Block placement: alternatively, place the FitKit block manually in the theme editor — the link then renders exactly where the block sits, no detection involved.

The modal doesn't open when the link is clicked

• The modal is lazy-loaded on the first click — that's how FitKit stays at zero impact on page load (4.8 KB gzipped, no network calls before the click). On a very slow connection the very first open can take a beat; subsequent opens are instant.
• Open your browser's console (right-click → Inspect → Console) and click the link. A red JavaScript error thrown by another script can stop the click from being handled — third-party scripts or theme customizations that intercept clicks globally are the usual suspects.
• Content blockers or aggressive privacy extensions can block storefront app scripts. Test in a private window with extensions disabled to rule this out.
• Still stuck? Email us the product page URL — that's usually all we need to reproduce it.

The recommender returns a strange size

Almost always a unit mismatch on input: the shopper typed inches while the guide was set to cm (or the reverse). A chest of “38” read as centimeters will match a child's size — read as inches it's a men's M.

• Check which unit is active in the modal's cm/in toggle when entering measurements. The default follows the visitor's locale (US visitors default to inches, most others to cm) — a shopper can simply switch the toggle and re-enter.
• On the chart side, verify the ranges themselves: a typo (960 instead of 96) or a gap between two sizes' ranges produces odd or empty results. The recommender guide covers how matching works and how to build clean ranges.
• Measurements between two sizes are resolved upward by design (between sizes → size up) — a recommendation one size larger than expected is usually this rule working as intended.

Analytics FAQ Pro

What exactly is counted?

Two things: guide opens (each time a shopper opens the size guide modal) and the add-to-cart rate after opening (the share of guide opens followed by an add to cart on that product), with a per-product breakdown.

Is any personal data collected?

No. Analytics are anonymous daily counters — no emails, no IP addresses stored, no shopper profiles, nothing sent to third parties. That's the whole design. Details in the privacy policy.

Why is my analytics page empty?

• Analytics is a Pro plan feature — on Free or Growth the data isn't collected.
• Counting starts once you're on Pro and the guide is live on your storefront; there's no retroactive data for the period before.
• Give it real traffic: on a low-traffic store, expect the first numbers to take a few days to become meaningful.

Does add-to-cart rate mean attributed revenue?

No — and we'd rather be honest about it. FitKit doesn't track orders or revenue (it only reads products, never orders). The add-to-cart rate after opening the guide is a proxy for purchase intent: a lightweight, privacy-clean signal of whether the guide removes size hesitation, not a revenue-attribution claim.