1 item
Trace HTTP redirect chains and verify tracking parameters (UTM, gclid, click IDs, and custom params) survive every hop. FloHop traces HTTP redirect chains and shows whether tracking parameters survive each hop — built for ad ops, affiliates, and analytics QA. WHAT IT DOES • Follow 301, 302, 307, and 308 redirects from a pasted URL or your current tab • Highlight parameters that are present, lost, or changed at each step • Track UTM tags, gclid, fbclid, msclkid, ttclid, native click IDs, and your own custom params WHY USE IT When a tracking link drops click_id or UTM before the landing page, FloHop shows exactly which hop removed it — faster than manual DevTools inspection. KEY FEATURES • Redirect chain visualization with status codes • Color-coded parameter tags (present / lost / changed / absent) • Configurable parameter list with quick presets (UTM, Google, Meta, native ads, and more) • Copy chain summary to clipboard • Works from the toolbar popup on the active tab LIMITATIONS FloHop follows server-side HTTP redirects (Location headers), similar to classic redirect checkers. It does not detect JavaScript redirects, SPA client routing, or parameters stored only in cookies. PRIVACY Checks run when you open the popup or run a check. Redirect URLs you submit are processed locally in your browser; FloHop does not send your URLs to a developer-operated backend.
May 22, 2026
rating_count is the Chrome Web Store ratings count, not a written-review count.
Media assets
Screenshots and videos on the listing.
Has promo video
Whether the listing includes at least one video.
Languages
Declared language locales.
Developer website
Listing exposes a developer website URL.
Contact email
Listing exposes a contact email.
Keyword in name
Case-insensitive substring match in the name.
Keyword in description
Case-insensitive substring match in the description.
Keyword occurrences in description
Count of case-insensitive occurrences in the description.
Category user-count percentile
Share of same-category extensions with fewer users (null if unknown).
These are transparent listing completeness / keyword signals, not a prediction of Chrome Web Store search ranking.