/api/collect POSTs

[EricWVGG]

I migrated a store from Liquid over to Hydrogen. So far things are going swimmingly (sales up 75% since launch day!).

One things I haven't figured out is, we're still getting POSTs to ourdomain.com/api/collect. I'm pretty sure that Hydrogen analytics are set up correctly… Perhaps there's some browser tabs somewhere with the old site loaded?

Is there a best practice for this? Would 307 redirects to ourdomain.myshopify.com/api/collect suffice?

[ashik4339]

Your own hypothesis (stale open tabs from the old Liquid site) is the most common cause, but it's checkable rather than assumed — a few things to confirm before treating it as "just old tabs":

1. Check the Referer header on those requests (server/CDN logs, or a temporary logging middleware). If every hit's referrer is your old theme's page structure and none are your current Hydrogen routes, that strongly confirms stale clients/cached JS rather than anything currently being served.
2. Grep your Hydrogen app for any leftover classic analytics snippet — ShopifyAnalytics, trekkie, or a raw <script> copy-pasted from the old theme's theme.liquid/checkout.liquid into a custom component during migration. This happens more often than people expect when content gets copied over instead of rebuilt.
3. Rule out third-party apps — some legacy analytics/pixel apps inject their own collector script independent of the theme, and won't get removed just because you swapped the storefront to Hydrogen. Check Settings → Apps for anything still active that predates the migration.
4. Remember checkout is still Shopify-hosted even on Hydrogen (unless you're on Checkout Kit) — Shopify's own Customer Events / Web Pixels can independently fire collection beacons at checkout regardless of your storefront code, so some /api/collect traffic may be entirely expected and not a leak from the old site at all.

If it turns out to be #1, a temporary 307 redirect from /api/collect to ourdomain.myshopify.com/api/collect (your original idea) is a reasonable stop-gap while old caches/tabs die off naturally — just don't leave it permanent, since it'll mask a real leak if one of #2/#3 is also happening.