Traffic report emails
Schedule the traffic summaries that the pixel makes possible.
Lightweight analytics
One pixel for page-level signals
The LoopAware traffic pixel is built for teams that need practical page-level analytics, not a full analytics migration. It records visits and visitor context, then feeds top pages, trends, devices, locations, and CSV export.
Small install, useful output
- Records page URL, referrer, browser timezone, locale, viewport, screen resolution, and stable visitor ID.
- Accepts only configured origins for the site, matching the feedback and subscriber boundaries.
- Supports a plain image pixel fallback for environments that cannot run JavaScript.
- Feeds selected-site and all-sites reports for operators who manage several properties.
<script defer
src="https://loopaware.mprlab.com/pixel.js?site_id=YOUR_SITE_ID">
</script>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 lightweight analytics guide?
Install the LoopAware lightweight analytics pixel to record page visits, visitor IDs, referrers, device context, and top pages with one small script tag. 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.