Collect visits
Embed `pixel.js` so LoopAware records page visits, stable visitor IDs, referrers, browser context, and supported edge geo signals.
Traffic reports
Traffic report emails for site teams
LoopAware traffic report emails turn visit, visitor, top-page, device, location, and attribution signals into scheduled summaries. Operators can send selected-site reports or portfolio reports without assembling screenshots from the dashboard by hand.
The problem
Traffic data often sits in a dashboard that only one operator checks. Agencies, founders, and small teams need a repeatable way to send useful site context to the people who can act on it, especially when feedback, subscribers, and errors are already tied to the same LoopAware site.
How it works
Choose scope
Use selected-site reports for one property or portfolio traffic reports for a defined set of sites.
Schedule delivery
Set cadence, send time, timezone, and recipients, then send a test report before relying on the schedule.
Feature-to-benefit fit
Recipient modes
Send reports to the manager, whole site team, or selected members without exposing report delivery to unrelated users.
Portfolio definitions
Agencies and operators can define which sites belong in an all-sites traffic report.
CSV export
When email is not enough, operators can still download selected traffic intervals for offline review.
Use-case examples
Weekly client reporting
An agency sends one summary per client site and keeps recipients aligned with the assigned site team.
Launch-page review
A SaaS founder checks subscriber growth and top pages after a campaign without opening the dashboard every day.
Portfolio operations
An operator groups several owned sites into a report library item and schedules a portfolio summary.
Objections and limitations
- Traffic reports depend on the traffic pixel or plain image pixel being installed on allowed origins.
- LoopAware reports operational traffic context, not session replay or advertising attribution workflows.
- Email delivery uses the configured Pinguin path, so local and production environments need that service configured.
For the underlying measurement path, start with lightweight analytics. For client delivery workflows, see agency client sites.
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 traffic report emails guide?
Schedule LoopAware traffic report emails for one site or a portfolio, choose manager, team, or selected recipients, and keep reports tied to feedback. 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.
Put traffic context on a schedule
When the team needs the same site signal every week, schedule it instead of rebuilding the report manually.