PomeloAnalytics
Menu

Category: Multi site

All blog posts in this category.

Marketing site, blog, docs and SaaS app: what to measure separately

Marketing site, blog, docs and SaaS app: what to measure separately

A B2B SaaS business operates a marketing website, a blog, a documentation hub and an authenticated product. It asks for "one dashboard for everything." The request sounds sensible but bundles questions with different answers. Pricing pages help prospects evaluate an offer. Documentation helps existing users solve problems. The application is where customers do their work. Blog articles may create awareness without producing immediate sales requests. Adding all pageviews together is rarely enough to guide those decisions. The goal should be consistent team reporting, adapted metrics for each surface and no unnecessary individual tracking across properties. A fictional portfolio makes the problem concrete Consider "North Workshop", an illustrative B2B SaaS company serving European SMBs. It runs four properties:a commercial site with product, pricing and demo-request pages; a blog publishing guides and industry analysis; a documentation hub explaining setup and product use; an authenticated application where customers carry out tasks.Marketing, engineering and support share reporting responsibilities. There is no dedicated business-intelligence department. The system therefore needs to answer ordinary questions without becoming a data infrastructure project. This company is fictional. The following model is design guidance, not a claim about any current vendor's capabilities. Marketing: understand acquisition and accepted demand The primary question is whether relevant visitors reach relevant pages and can complete intended actions. Useful starting indicators include entry pages, detectable sources, important page consultations and requests actually accepted by the application. A pricing page with many views is not automatically effective if visitors misunderstand the offer. A low-volume page may yield a few well-qualified accounts. Metrics must connect to questions, not exist just because they are easy to capture. State the denominator of each conversion rate. Accepted inquiries divided by visits is different from accepted inquiries divided by pricing-page views. Our acquisition page guide provides a practical framework. Lead qualification belongs primarily in the business process. Raw form contents need not be copied into audience analytics to count completed requests. Blog: measure discovery and understanding A B2B blog should not be judged only by immediate conversions. An educational article can help a technical decision-maker long before a commercial conversation. Review entry pages, content trends, detectable discovery sources and carefully selected actions such as a resource download. Google Search Console provides a separate perspective on Google Search impressions, clicks and queries under its own definitions. Search impressions are not website visits. Do not merge the two into one unlabeled traffic count. A useful editorial decision might be updating a high-value article, adding a missing answer raised by support, or improving links between related guides. Documentation: support problem-solving Documentation serves a different purpose. Teams want to know which articles are used, which explanations need improvement and whether readers can find useful instructions. A troubleshooting page may receive more traffic because it ranks well or because a product defect has spread. The direction of change is not intrinsically good or bad. Interpret it with support tickets and release information. Documentation also attracts crawlers and AI agents. Automated requests should not automatically be treated as human reading sessions. Avoid inventing a "resolution rate" from pageviews alone. Reliable resolution measurement requires a meaningful signal, such as explicit feedback or a carefully defined service outcome. SaaS application: adoption, retention and operations Inside an authenticated product, the questions change. Do customer organisations activate important features? Does useful work recur? Which operations fail? These often require product analytics, operational diagnostics and business events beyond ordinary public-website pageviews. PostHog, for example, documents a web analytics view centred on traffic and a product analytics view focused on events, adoption, funnels and retention. That distinction does not prove that two separate software tools are always required. It shows that the questions and data models are different. Teams should explicitly separate service operations, product usage and public audience measurement. A single indistinguishable event stream can easily become more invasive than necessary. A four-surface measurement mapSurface Main decision Starting metrics Avoid in audience reportingMarketing Improve acquisition and inquiries Entry pages, sources, accepted requests Free-form contact fieldsBlog Prioritise content and revisions Article entrances, trends, sources Individual reading profilesDocumentation Improve help resources Frequently used pages, justified outcomes User secrets and personal queriesProduct Understand activation and usage Defined business events, adoption, incidents Blanket copies of application payloadsThe map is a contract between owners, not a vendor-feature checklist. Centralised dashboards are not cross-site identity tracking Multi-site teams often need property-level comparisons, common date ranges and shared reporting. Those goals can be met with aggregate metrics without identifying the same person across every property. Linking individual activity across sites raises separate questions about purpose, lawful basis and transparency. The CNIL's narrow conditions for audience-measurement exemptions should not be extended by assumption to cross-site identity linking. Keep reporting centralisation distinct from personal behaviour linkage. The former can strengthen governance without requiring the latter. A shared metrics dictionary Harmonise concepts that can genuinely be compared: timezone, reporting period, entry page, observable source and selected event definitions. Conversions are often surface-specific. A documentation download, a marketing demo request and first successful product use cannot responsibly become an interchangeable "conversion" metric without further context. Document for each measure its source, definition, unit, calculation, filters, owner and limitations. Our multi-site dashboard guide describes how to organise portfolio and property views. Assign collection and access owners Who may add a script to documentation? Who approves marketing conversion events? Who can export product data? These are governance decisions as much as reporting questions. Assign an owner to each surface and a shared owner for collection principles. Review access when staff or contractors change. The CNIL recommends least-privilege permissions and regular reviews. A lightweight process can work: write the purpose, choose necessary fields, test with synthetic input, update the dictionary and review periodically. One tool or several? One product may fit when permission models, reporting definitions and required analytical depth are compatible. Several products may make sense when purposes, sensitivity or event types differ materially. Avoid multiplying tools for fashion. Also avoid forcing everything into one platform just because a single dashboard looks convenient. Compare total administration, maintenance, data quality, export and training costs. The measurement map should precede vendor selection. Where Pomelo fits Pomelo focuses on privacy-first audience measurement intended to remain readable for teams managing several properties. That makes its position relevant to public-facing sites and shared web reporting. Web reporting does not necessarily replace product analytics, business intelligence or application diagnostics. Authenticated product usage may require complementary instrumentation, depending on verified needs and available functionality. A practical ownership ritual for four surfaces A short quarterly meeting can keep the measurement map useful. Ask each surface owner to bring one decision made from reporting, one metric whose definition caused confusion, and one collection operation that may no longer be necessary. The marketing owner might show that a pricing-page redesign changed the number of accepted inquiries. The editorial owner might identify a guide that needs updating, supported by Search Console and observed entrances. Support might explain why documentation traffic increased after a release. The product team might report that a feature's activation event was redefined, making historical comparisons less straightforward. Do not force those stories into a single performance score. Record the distinct decisions and the evidence limits, then identify any shared reporting changes that would genuinely benefit the whole organisation. Governance also requires someone to challenge a proposed new event. Before it is added, the requesting team should explain the decision it will support, the minimum fields needed and what happens if the event is never collected. This simple exercise can prevent an expanding set of unused identifiers and arbitrary dimensions. The result is a portfolio report that respects differences among surfaces. A shared language becomes possible without demanding that each website or application adopt identical instrumentation. Conclusion: map decisions before dashboards The best system is not the one that puts everything on the same chart. It is the one that assigns every surface a useful decision, defensible metrics and accountable owners. Start with a four-surface map. Harmonise what deserves comparison, separate different purposes and resist equating centralised reporting with cross-site personal tracking. FAQ Can all four surfaces use one analytics product? Yes, where definitions, permissions and analytical depth fit. Reporting goals still need to differ by surface. Must users be identified across blog and product? Not for most traffic and content decisions. Any individual linking requires a distinct justification. Does Search Console replace blog analytics? No. It reports Google Search visibility and interactions, not all website use. How can documentation success be measured? Start with content demand and support questions. Add a credible resolution signal only if it can be defined and tested. Pageviews alone do not prove resolution. SourcesPostHog, web analytics dashboard PostHog, product analytics PostHog, retention analytics Google Search Central, getting started with Search Console CNIL, audience-measurement tool conditions CNIL, managing permissions

Multi-site analytics dashboard: manage 5, 10 or 30 websites without losing clarity

Multi-site analytics dashboard: manage 5, 10 or 30 websites without losing clarity

Tracking one website is a measurement problem. Tracking ten becomes a governance problem. Each team initially creates its own analytics property, event names and dashboard. Months later, the group has ten definitions of “conversion”, three time zones, incompatible campaign taxonomies and accounts with unclear ownership. The missing piece is not another chart. It is a shared structure. A useful multi-site dashboard must support two movements:compare properties on a consistent baseline; drill into each site without erasing its business context.Combining everything creates an abstract average. Separating everything hides the portfolio. The right architecture preserves both levels. Start with a property map List every site and its role before choosing metrics.Property Role Main audience Meaningful conversion OwnerCorporate site Trust Prospects, partners Qualified contact CommunicationsProduct A Acquisition SMBs Demo request Growth AProduct B Acquisition Mid-market Meeting booked Growth BHelp centre Support Customers Self-service resolution SupportBlog Discovery B2B audience Signup or product visit ContentSites with different purposes should not be ranked only by traffic. A help centre can perform well by reducing support demand even when it generates no demos. The map should also record:domains and subdomains; production environment; analytics tool and property ID; time zone; currency where relevant; creation date; business owner; technical owner; access list; collection mode; retention; active, migrating or archived status.This becomes the reference inventory. Define a common measurement contract The multi-site baseline is not a dashboard. It is a compact measurement contract applied to every property. Common dimensions Use shared definitions for:page or path; referrer domain; source, medium and campaign; country or region; device class; date and time zone; primary events; conversion status.Apply one URL parameter policy and one UTM taxonomy. Common events A small library is enough: form_submitted demo_requested signup_completed download_completed outbound_clicked search_usedEvery event needs a definition, trigger, allowed properties, owner, test and version. One name must not represent different actions. Conversely, three names for the same contact request prevent comparison. Common quality rules Document:test-environment filtering; bot handling; internal-domain handling; consent and collection modes; path normalisation; time zone; deployment process; alert thresholds.The data collection summary can hold the shared baseline and property-specific exceptions. Separate three reading levels A sound multi-site system does not put every chart on one page. Level 1: portfolio view This answers management questions:Which sites gain or lose useful traffic? Where are conversions moving? Which property has an anomaly? Which team needs investigation? Which site stopped sending data?Keep it short. A table with one row per property is often more useful than twenty small charts.Site Visits Change Useful conversions Rate Main channel Data statusCorporate 24,500 +6% 132 0.54% Organic OKProduct A 18,100 -4% 284 1.57% Paid search ReviewProduct B 9,600 +12% 96 1.00% Partners OKHelp 41,000 +2% n/a n/a Direct OKFigures are illustrative. Data status matters: a fall means something different when collection broke. Level 2: property view Each site retains its business dashboard:acquisition; landing pages; content; conversions; events; trends; data quality.A SaaS property may track trials, while a help centre tracks unsuccessful searches or support escalation. Level 3: diagnostics Analysts and engineers need:events by version; collection errors; unknown parameters; client/server discrepancies; time-series breaks; unexpected domains; test traffic; ingestion delay.Keep diagnostics out of executive reporting, but do not omit them. Otherwise every anomaly becomes a manual investigation. KPIs that can be compared Visits and page views They show scale but naturally favour larger sites. Always include trend and context. Common meaningful conversions A shared conversion group can include demo requests, qualified contacts, verified signups or confirmed purchases. Preserve the conversion mix too. A total can hide a shift toward lower-value actions. Conversion rate Rates compare different property sizes only when the denominator is identical. Document whether it uses visits, visitors, sessions or landing-page entries. Channel share Organic, paid, email, partner, referral and direct shares reveal dependence. This requires one campaign taxonomy. Collection health Add technical KPIs:time of last received event; event-volume change; rejected-event share; unknown parameters; pages missing path or title; abrupt direct-traffic movement.Data reliability is a governance KPI. What not to add naively Unique visitors The same person can visit several domains. Adding each site's unique visitors counts them more than once. A global identifier for deduplication materially changes collection. The CNIL notes that using the same identifier across several sites for global tracking falls outside the French consent-exemption conditions it describes for certain audience-measurement trackers. A lightweight report can instead use:visits by property; a clearly labelled non-deduplicated reach sum; or an aggregate method that does not require a person-level cross-site identifier.Heterogeneous conversions A brochure download is not automatically equal to a sale. Show a common total and its composition. Simple averages An average of ten conversion rates gives equal weight to a site with 100 visits and one with 100,000. Use a weighted overall rate or show the distribution. Unaligned periods Time zones and campaign calendars can move events between days or weeks. Normalise time before comparison. Compare without punishing small sites Multi-site views easily become rankings. That is rarely helpful. Use four axes:current level; change over time; local target; measurement confidence.A niche site can have low volume, healthy growth and high-value outcomes. A large site can hide paid-channel dependence or broken tracking. Trends and comparison bands are more useful than a podium. Structure access Multi-site operations increase excess-access risk. Define roles:portfolio owner: sees all properties and manages standards; site owner: administers one property; analyst: views and exports as needed; contributor: sees reports without changing collection; agency or partner: access limited to contracted properties; technical support: temporary, logged access when required.Avoid shared accounts. Review access quarterly, remove access at contract end and apply least privilege. Establish a governance cycle Weekly: monitor health Automate simple alerts for no data, abnormal shifts, unknown domains, rejected events and sudden direct-traffic changes. Monthly: discuss decisions Ask property owners:What changed? What action follows? Which hypothesis will be tested?Reporting should not become a reading of numbers. Quarterly: review the contract Check common events, UTM naming, inactive properties, access, retention, vendors, configuration differences and business goals. At launch: use a checklist Before adding a site:assign owners; set time zone; apply the collection baseline; configure filters; test events; verify consent behaviour; add it to the portfolio; document exceptions; create alerts; schedule the first review.Choose an architecture One property per site This is usually clearest for access, retention and configuration. It requires a portfolio layer for comparison. One shared property with a site dimension It can simplify some reports but mixes permissions, configurations and collection risks. One mistake affects the full dataset. One property per site plus a consolidated view This is often the best compromise: operational separation with portfolio aggregation. Some vendors provide roll-up or consolidated views. Verify plan requirements, deduplication method, permissions and exactly which data are combined. The key factor is not only the number of sites. It is their independence across teams, brands, purposes, regions, access and privacy settings. A one-page dashboard model Top stripportfolio visits; useful conversions; weighted overall rate; healthy property count; open anomaly count.Central table One row per property with trend, conversion, channel and status. Acquisition block Channel shares by site. Content block Top landing pages and rising pages, filterable by property. Quality block Missing data, rejected events, access reviews and recent deployments. Each block links to a detailed view. The portfolio dashboard signals; it does not explain everything. Conclusion Multi-site measurement works when governance comes before visualisation. You need:a clear property map; a common measurement contract; documented exceptions; three reading levels; comparable indicators; restricted access; a review cycle; consolidation that does not force person-level cross-site tracking.The best dashboard does not make every site identical. It gives them a shared language while preserving their role. FAQ Should every website have its own analytics property? It is often the clearest way to separate access and configuration. A consolidated view can compare them. A shared property can work when purposes and permissions are genuinely shared. Can unique visitors be added across sites? Not as deduplicated reach. One person can appear in several properties. Label the number as non-deduplicated or use an appropriate aggregate approach without introducing a global identifier by default. How many KPIs belong in the portfolio view? Five to eight well-defined columns are usually enough: volume, trend, conversion, rate, main channel and collection health. Details belong in property views. How should different site goals be handled? Keep a small common baseline and add local indicators. Compare each site with its own target and trend, not only with other sites. How often should access be reviewed? Quarterly review is a reasonable practice, with immediate removal when employees or vendors leave. SourcesCNIL, Audience-measurement cookies and consent conditions Google Analytics, Analytics account structure Google Analytics, Roll-up properties Matomo, Roll-Up Reporting Plausible, Consolidated view Regulation (EU) 2016/679, purpose limitation and data minimisation principles

Just the right measure, for all your websites.

Pomelo is opening gradually. Join the first teams measuring right and help shape what comes next.