Basic request context
The image request can record the server-observable visit context.
Fallback tracking
No-JavaScript traffic pixel fallback
LoopAware includes an image pixel fallback for pages where JavaScript is unavailable, blocked, or intentionally minimized, while the JavaScript pixel still provides richer context when it can run.
Why a fallback matters
Some sites intentionally keep scripts minimal, and some visitors block JavaScript. The fallback gives teams a basic visit signal without requiring a full client-side runtime on every page.
<noscript><img src="https://loopaware.mprlab.com/public/visits?site_id=YOUR_SITE_ID&url=https%3A%2F%2Fexample.com%2F" alt="" width="1" height="1" /></noscript>What changes without JavaScript
Less browser detail
Viewport, screen, and richer client-side fields require the JavaScript pixel.
Same site dashboard
Fallback visits still support the same site-level traffic reporting surface.
Limitations
- The image fallback cannot collect every browser detail that JavaScript can provide.
- It is not a replacement for product event analytics.
- Public endpoint origin and site configuration still matter.
Best fit
Use this when a site values minimal script usage but still wants a baseline traffic signal in LoopAware.
Implementation checklist
- Install the traffic snippet or no-JavaScript fallback on one public page before expanding to the full site.
- Confirm top pages, attribution, device, location, or export views show the context the team needs for decisions.
- Use the dashboard summaries or scheduled emails to decide which pages deserve copy, feedback, or uptime follow-up.
Common questions
When should teams use this no javascript traffic pixel guide?
Use LoopAware's image pixel fallback to record basic traffic when JavaScript is unavailable or intentionally disabled. It works best when the team needs practical page-level traffic context inside the same LoopAware site workspace.
What should teams verify after setup?
Confirm the workflow is tied to the correct LoopAware site, then check the first dashboard records with the people who will act on them.