Cross-site reporting across SGEN sites
How to roll up traffic, leads, and conversions across your portfolio
The SG-Dashboard's cross-site reporting view aggregates the key metrics from every site under your account into one place. It is built for operators who manage two or more sites and want a single view of "how is the whole portfolio doing" without opening each site individually.
This guide explains what the cross-site view shows, how it relates to per-site analytics, and the patterns that make portfolio reporting useful day-to-day for brand operators, agencies, and multi-region businesses.
What is this for?
Cross-site reporting answers three questions a portfolio operator asks repeatedly:
- What is total traffic across all our sites this period? Sessions, visitors, page views aggregated.
- Which site is growing fastest, which is flat, which is declining? Trend per site, ranked.
- Where are our leads and conversions coming from across the portfolio? Form submissions, sign-ups, sales rolled up.
The cross-site view sits at the account level. It is not a replacement for per-site analytics — each site still has its own deep analytics page with full visitor sessions, page-level reports, and campaign attribution. The cross-site view is a roll-up layer on top, optimized for the "how is the portfolio doing" question.
Three visual modes:
- Summary cards. Headline metrics: total sessions, total leads, total conversions, with a small spark line for the last 30 days.
- Per-site table. Each site as a row, with metrics as columns. Sortable. Click a row to drill into that site's analytics.
- Trend chart. Time-series chart of total portfolio traffic, with optional per-site overlay.
Good use cases
The brand director opens SG-Dashboard each Monday and reviews the cross-site summary. Sessions across all three sites, top-performing site, biggest week-over-week movers. A 30-second glance answers "where do I need to look closer?"
Before a quarterly business review with a client, the agency lead opens the cross-site table, filters to that one client's site, and pulls the 90-day trend. The same view rolled up across all clients shows the agency's overall portfolio.
Acme Coffee US and Acme Coffee UK are on separate sites for SEO reasons. Cross-site reporting puts them side-by-side. The brand director sees that UK is growing 12% week-over-week and US is flat — a signal to dig into what is working in the UK.
The CEO needs a single number for "total digital traffic across our brands this quarter." The cross-site summary gives it. CSV export feeds it into the board pack.
The cross-site table ranks sites by conversion rate. The site at the bottom of the rank gets the next round of conversion-rate-optimization attention.
A marketing campaign drives traffic to multiple brand sites. The cross-site referral breakdown shows total campaign traffic without you stitching together per-site reports manually.
What NOT to use this for
The cross-site view is metrics-by-site, not metrics-by-page. For specific page performance, open the relevant site's individual analytics page.
The cross-site view updates on the standard analytics cadence — usually within an hour of activity. For real-time monitoring (active visitors right now), use per-site analytics, which is more current.
Custom events you have set up are scoped per site. The cross-site view does not aggregate custom events. Use per-site analytics or external analytics tools for custom-event roll-ups.
SGEN's analytics is a first-party visitor and conversion view. For deep funnel analysis, multi-touch attribution, or sophisticated segmentation, pair SGEN with a dedicated analytics tool.
The current cross-site view shows one period. To compare two periods, export both as CSV and compare offline.
Customer-level analytics (which individuals visited which sites) is not part of the cross-site view. Customer accounts on each site live in that site's customer-management area.
How this connects to other features
Each site has its own deep analytics page. The cross-site view rolls up from those per-site stores.
Visibility into cross-site reports depends on account role. Account admins see every site; per-site-only members see only their site (and the cross-site view shows only the sites they have access to).
New sites auto-appear in the cross-site view once they have collected at least one session.
The view supports a per-site filter so you can isolate one site's roll-up or compare two specific sites without seeing the full portfolio.
Snapshot the cross-site report for offline analysis, board reports, or sharing with stakeholders.
Reads of cross-site reports do not log. Exports do — the audit log records who exported what and when.
Before you start
A short checklist before relying on cross-site reports:
- Confirm all your sites are sending analytics. New sites take a day or two to start showing meaningful aggregates. If a site shows zero sessions across the board, check that the public site is publishing visitors and that the site's analytics setting is enabled.
- Check permission scope. Your view of the cross-site report reflects only sites your account role grants access to. If you expected a site to appear and it does not, check whether you have access to it.
- Decide on the comparison period. Cross-site reports default to last 30 days. Pick a period that matches the question you are asking — weekly trends need 7 days, quarterly business reviews need 90.
- Know your top-line metric. Sessions, visitors, leads, or conversions — pick the one that matters most for your roll-up question and frame the analysis around it.
- Decide on the granularity. Site-level roll-up is the default. You can drill into a specific site for page-level data, but the cross-site layer itself stops at site as the unit.
Where to go
The cross-site report lives at the account level on SG-Dashboard.
SG-Dashboard → Analytics → Cross-site Report
The view opens with the last-30-days summary by default. The period selector at the top right switches to 7, 30, 90, or 365 days.
The per-site table is sortable by any column — sort by sessions for traffic ranking, by conversion rate for performance ranking, by trend for who is moving fastest.
Steps — Use cross-site reporting end-to-end
1. Open the cross-site report
Click SG-Dashboard → Analytics → Cross-site Report at the top of the account-level menu.
The view loads with the last 30 days summary across all sites your account has access to. The summary cards at top show total sessions, total visitors, total leads, and total conversions. Below the cards, a per-site table lists each site with the same metrics as columns.
If you see an empty state with "No sites found" — check that the account has at least one site that has collected analytics. New sites need at least 24 hours of activity before aggregates show.
2. Pick the comparison period
Use the period selector in the top right. Available choices: 7 days, 30 days, 90 days, 365 days. The whole view recalculates when you change the period.
For weekly check-ins, 7 days. For monthly reviews, 30 days. For quarterly reviews, 90 days. For year-over-year analysis, 365 days.
The "Compare to previous period" toggle adds a delta column — last 30 days vs the 30 days before that, shown as a percentage. Useful for spotting acceleration or deceleration.
3. Sort the per-site table
Click any column header to sort. Common sorts:
- By sessions, descending. Shows your largest-traffic sites at the top.
- By trend, descending. Shows fastest-growing sites at the top.
- By conversion rate, ascending. Shows lowest-performing sites at the top — the ones to focus optimization on.
- By leads, descending. Shows the sites generating the most pipeline.
The sort is local to the view; refreshing the page resets to the default (sessions descending).
4. Drill into a specific site
Click any row in the per-site table to open that site's individual analytics page in a new tab. You stay in the cross-site view in the original tab, with the new tab opened on the per-site detail.
This is the typical pattern: spot something interesting in the roll-up (a site growing faster than expected, a site losing leads), drill in, investigate the per-site detail.
5. Filter to a subset of sites
Use the Sites to include filter to narrow the view. Uncheck sites you do not want in the current analysis. The summary cards and trend chart recalculate to reflect only the selected sites.
Common filters:
- Just one site to use the cross-site view as a focused per-site dashboard with the simpler summary layout.
- Two sites for a head-to-head comparison — e.g., US vs UK regional sites.
- All client sites for an agency while excluding the agency's own portfolio site.
6. View the trend chart
Below the per-site table, the trend chart shows total portfolio traffic over the selected period as a line chart. Hover for daily values.
Toggle Show per-site overlay to add one line per site to the chart. Useful for spotting whether one site is driving the total trend or whether multiple sites are moving together.
The chart is a quick visual of "is the portfolio growing, flat, or declining?" — usually faster than reading numbers.
7. Export to CSV
For offline analysis or sharing with stakeholders who do not have admin access, use Export CSV at the top right.
The export includes:
- Period selected.
- One row per site.
- All available metrics (sessions, visitors, leads, conversions, conversion rate, trend).
- Period-comparison columns (if Compare to previous period was on).
The CSV opens in spreadsheets cleanly. Pull it into your board reports, monthly updates, or whatever offline format your organization uses.
8. Save a custom view (if your plan supports it)
Some plan tiers support saving custom cross-site views — the period, sites filter, and sort preserved as a named view you can re-open with one click.
Useful for:
- Daily check-in view — last 7 days, all sites, sorted by trend.
- Monthly board view — last 30 days, all sites, sorted by sessions.
- Client check-in view (agencies) — last 90 days, filtered to one client's site.
Saved views appear on SG-Dashboard's Analytics menu under the cross-site report.
9. Set up a recurring digest (if your plan supports it)
Some plan tiers support recurring email digests of the cross-site report. Configure at Account → Notifications → Cross-site Digest.
Options:
- Cadence. Weekly, monthly, or quarterly.
- Recipients. Up to five email addresses per digest configuration. Multiple configurations for different audiences supported.
- Period covered. Match the cadence (weekly digest covers last 7 days, monthly covers last 30).
Useful for stakeholders who do not log into the admin but want a heads-up on portfolio performance.
What success looks like
A useful cross-site reporting setup feels like: For a brand-portfolio operator: weekly review takes five minutes. Surprising movers get flagged for investigation. Steady-state sites get a quick acknowledgment and move on. For an agency: client check-ins prepare in minutes instead of an hour. Each client's site has a clean, exportable snapshot. For a multi-region operator: the regional director sees both regions at once instead of switching between admins.
- You can answer "how is the portfolio doing this week?" in under 30 seconds.
- Trend spotting happens at the cross-site level before you drill into specific sites.
- Stakeholders who do not have admin access get the relevant numbers via CSV export or scheduled digest.
- The data feels current — most-recent-period numbers reflect what is happening, not week-old data.
- Drilling from cross-site into per-site is one click, not a fresh navigation cycle.
- The per-site table sort matches your actual mental model of "what to look at first."
What to do if it does not work
Less-obvious cases:
Check three things: your account role grants access to that site, the site has been collecting analytics for at least 24 hours, and the site's analytics is enabled in its site settings. If all three are true, refresh the cross-site view.
Small differences (under 1%) are expected due to roll-up timing — the cross-site view aggregates on a slightly slower cadence than per-site. Differences over 5% are worth investigating; check the date range and time zone settings.
First check whether one site went offline or had a publish error during the period. Open that site's analytics directly. If the drop is real, the cross-site view is correctly reflecting it.
Check that at least one site has data in the selected period. Empty period + empty CSV.
Cross-site reports with 10+ sites can take a few seconds. If load is consistently over 30 seconds, contact support — performance should be subsecond for most accounts.
Some plans support custom colours per site. Otherwise, the chart auto-assigns colours; filter to fewer sites for clearer visuals.
Permission-scoped views differ legitimately. Your view aggregates the sites you have access to; theirs aggregates a different subset. Compare the per-site tables to confirm the difference is in site coverage, not in metric calculation.
Worked example — Acme weekly portfolio review
Every Monday morning, Acme's brand director runs a five-minute cross-site check:
- Opens SG-Dashboard → Analytics → Cross-site Report. Default 30-day period loads.
- Glances at the summary cards. Total sessions: 22,530. Lead count: 337. Conversion rate: 1.5%. All within expected ranges.
- Sorts the per-site table by trend descending. Notes Acme Wine is up 18% this week — biggest mover. Acme Bookstore is flat at zero week-over-week.
- Drills into Acme Wine. Per-site analytics show a referral from a wine review site that linked to Acme Wine's homepage. Decides to thank the reviewer.
- Drills into Acme Bookstore. Sessions are flat but conversion rate held steady. Decides to schedule a marketing campaign next month rather than dig into a non-issue.
- Exports CSV for the operations team. Drops it into the team's Monday update channel.
Total time: four minutes. The cross-site view did the heavy lifting; the brand director's time went to interpretation and decisions, not data wrangling.
Worked example — Agency quarterly review prep
A small agency prepares for a quarterly business review with one of its clients. The agency lead's workflow:
- Opens cross-site report. Sets period to last 90 days.
- Filters to just the client's site. Other client sites are hidden — only this client's data shows.
- Toggles Compare to previous period on. Quarter-over-quarter comparison shows up.
- Exports CSV. The CSV becomes the data section of the QBR slide deck.
- Drills into per-site analytics. Pulls top traffic sources, top landing pages, and top exit pages for context. Adds them to the QBR deck.
The whole prep takes 20 minutes instead of the hour it took before cross-site reporting was wired into the agency's workflow.
Notes on what cross-site reports do and do not show
A few details worth memorizing so you do not chase ghosts:
Aggregation cadence. Cross-site reports aggregate from per-site stores. The aggregation runs on a regular schedule; expect numbers to lag per-site analytics by up to an hour during high-activity periods.
Time zone. All cross-site reports use the account's primary time zone setting. Per-site time zones may differ, which can cause slight day-boundary differences in some metrics.
What counts as a session. A session is a continuous period of activity by one visitor on one site. Cross-site sessions are summed across sites — if one visitor visits two sites, they count as two sessions in the cross-site total.
What counts as a lead. A lead is a form submission flagged as a lead-capture form in the site's settings. Newsletter sign-ups, contact form submissions, demo requests typically count; comment submissions do not.
What counts as a conversion. A conversion is a completed conversion event as defined in the site's analytics settings. Each site can define its own conversion events. Cross-site conversion totals sum across sites.
Privacy and consent. Cross-site analytics respects each site's privacy settings. If a site has consent-gated tracking, only consented visitors count in the cross-site roll-up.
Data retention. Historical data is retained per the site's plan tier. The cross-site report can show data going back as far as any one site's retention allows. Older periods may be unavailable for some sites.
Reading order and rhythm tips
A few short habits make cross-site reporting actually stick as part of weekly work rather than a tool you opened twice and forgot about:
- Same day, same time. Pick Monday morning or Friday afternoon and protect the slot. The cross-site view rewards routine inspection; an irregular cadence makes trends harder to spot.
- Read summary first, then drill. Open the summary cards before the per-site table. Drill into specifics only after you have noticed something at the roll-up level.
- One question per session. Pick one question to answer ("which site is growing?" or "where are leads coming from?") and answer it cleanly rather than reading everything every time.
- Export when you find something. A CSV of the moment you noticed a trend is a useful artifact for later — drop it in a shared notes folder so you can compare against a snapshot weeks later.
- Match the period to the question. Weekly check-ins on 7-day window; monthly reviews on 30-day; quarterly on 90.
Building the routine takes two or three Mondays. After that, the cross-site view is the single dashboard that keeps you honest about how the portfolio is actually doing.
Common questions
Can I see real-time visitor counts in the cross-site view? Not in the cross-site view. For real-time visitor counts, open the per-site analytics page on the site you want to see.
Does the cross-site report support custom date ranges? The current view supports 7, 30, 90, and 365 days. Custom date ranges are on the roadmap. For now, use CSV export and filter offline.
Can two sites have overlapping conversion definitions that get double-counted? Each site defines its own conversion events. The cross-site total sums conversions per site. A visitor converting on two sites counts twice. The cross-site view does not deduplicate visitors across sites.
Can I see how many unique visitors hit any of my sites? Cross-site visitor counts sum per-site visitor counts. There is no cross-site deduplication — a person visiting two sites counts as two visitors in the total.
Is there an API for cross-site reports? Some plan tiers expose a cross-site reporting API. Check your plan's API documentation for endpoints. Typical use: pulling cross-site data into an external dashboard.
Can I add custom metrics to the cross-site view? Custom metrics are per-site. The cross-site view shows the platform's standard metrics. For custom-metric portfolio reporting, export per-site reports separately.
How does account-level permission affect the cross-site view? Your view shows only the sites your account role grants access to. Per-site overrides do not affect cross-site visibility — only account-level scope does.
Can scheduled digests be sent to non-team members? Yes — digest recipients can be any email address. They do not need an account to receive the email. The digest is read-only; it includes the summary numbers but no live drill-down.
Will adding a new site to the account auto-include it in scheduled digests? Existing digest configurations have a fixed sites list. To include a new site in a digest, edit the digest configuration and add it.
Does CSV export include trend data? The CSV includes period totals. Trend data (day-by-day breakdown) is not part of the standard CSV; some plan tiers support a separate trend export.
Can I compare three or more periods in the same view? Not natively. Use CSV export across multiple periods and compare in a spreadsheet.
Does the cross-site report show campaign attribution? The view shows referral and channel breakdowns aggregated across sites. Deep multi-touch attribution requires dedicated analytics tooling alongside SGEN.
Related reading
Cross-site reporting is the answer to "how is the portfolio doing?" — a single question that used to require five tabs open. Spend five minutes on Monday morning and you will spot most things worth spotting. The next read is the agency client portfolio setup guide, which depends on cross-site reporting being part of your weekly rhythm.
Add a second site to your account — the provisioning entry point.
Cross-site template sharing — reuse design across the sites in your portfolio.
Multi-site permissions and roles — scope who can see what data.
Agency client portfolio setup — agency reporting patterns.