This website update extends the private reporting system beyond Didga. A central owner page uses the existing Didga login; the other websites do not receive copies of its password or authentication files.
Measure the websites that exist.
All nineteen registered websites now have reporting installed: Didga’s existing report and eighteen new website installations, including Magivolve and Magisoft Games. Domains beginning with A and unbuilt or parked placeholders are excluded. Sites that were unreachable during the inventory were left untouched because their content could not be verified. A registration alone does not establish a working website.
The new tracker reports anonymous browser sessions, first observed referral domains and short campaign labels, and a boolean hint that a trusted interaction occurred. A session is counted at most once per website per Eastern calendar day. The same person can use multiple browsers or return on another day, so these figures are not a count of identified people.
Finish the application integrations.
Magivolve: its reviewed response adapter is active after a scoped reload of the existing application. Anonymous HTTP checks found one shared module on the public page, no module on the login page and the original public content after removing only the injected script. The sampled existing asset stayed unchanged.
Magisoft Games: its browser integration is active after comparison with the running source, an isolated Next application build and activation through the observed process manager. This application needs a browser integration because its proxy does not apply the ordinary page-response filter.
The Next integration handles page changes that happen without a full reload. It checks the current route before interaction hints or queued requests and can begin on a later eligible public route without creating a second tracker for the document. Recognized account, cart, developer and other private routes remain excluded.
The selector now identifies the two applications by name. An empty report does not establish that nobody visited; collection begins with received events and older visits are not reconstructed.
Keep the game report distinct.
Didga’s existing game report retains its game-start sessions and estimated active play time. Other websites receive website-level visit and interaction estimates when their tracker is installed and active. This does not add game-state adapters, play-time measurements, completed-level counts or verified player counts to their games.
Existing public visitor charts and their history remain separate. The rollout preserves each site’s existing counter and cookie rather than resetting its totals or filling older days with new detail.
Use one private report.
The owner signs in at Didga and opens the website report. Its site selector changes which registered website’s aggregate report is shown. The collection endpoint accepts small requests from the registered origins; it does not expose those reports to the contributing websites.
The script uses a separate first-party cookie on each participating website. Its requests omit cross-site credentials. A site’s random cookie value is received transiently, then keyed daily digests support deduplication in private storage. There is no shared cross-site browser identifier.
Make estimates and exclusions explicit.
Likely-human, unverified, known-bot and declared-automation categories describe signals, not proof of a person. Bots can imitate interactions, and real visitors can block scripts or provide no referral information. Coverage is limited to requests that reach the collector.
Signing in at Didga does not sign the owner in on unrelated domains. The website report offers a per-site Visit without tracking link. Its exclusion is stored in that browser on the selected website; separate browsers and sites need their own choice. Marked QA tabs and recognized private routes are also excluded.
Keep the collection small.
The tracker does not read form values, typed text, pointer coordinates, recordings, microphone audio or screenshots. It sends source domains and short campaign labels rather than complete page or referral URLs. The analytics feature stores no raw IP addresses, raw user-agent strings or raw session tokens. Anonymous daily digests retain thirty days, while aggregate reports retain ninety days; earlier activity is not retrospectively reconstructed.
See the shared website analytics notice for cookie, exclusion and reporting details. Didga’s recording and game privacy page continues to explain its existing game-specific features.
Check the delivery, not just the source.
The sites use different hosting arrangements, including ordinary pages, PHP applications and proxied JavaScript applications. A guarded HTML injection avoids replacing whole page files or publishing local drafts. Actual delivered pages, script loading, exclusion behavior and protected reports need browser review; a prepared file alone is not a completed deployment.
Automated checks: 112 backend checks; 11 PHP script-wrapper checks; 34 frontend and lifecycle checks; 3 central copier checks; 21 instrumentation-tool checks; 9 editorial-preservation checks.
Native browser review: a disposable loopback owner profile opened the central dashboard with the real nineteen-site registry; an empty generic website report showed no invented history; Didga special mode loaded the existing report without a second tracker; site selection, Eastern Time date filtering and a native aggregate-only JSON download were reviewed; live Keyeske and Magivolve pages loaded the shared module once in excluded QA tabs with no console errors; live Magisoft public/login rendering and private-to-public/back navigation retained one configuration and no console errors.
The dashboard observations used a disposable loopback profile; the production owner dashboard was not exercised with production credentials. The first sixteen new website installations passed thirty-two identity/gzip response checks and twenty-nine sampled unchanged-asset checks. Magivolve then passed its separate activation and anonymous public/login response checks. Magisoft Games was reviewed through anonymous responses after its isolated build and activation. These HTTP checks are distinct from the recorded native browser reviews: the loopback dashboard, live Keyeske and Magivolve QA tabs, and Magisoft public/login navigation. They do not certify every private route or exercise Magisoft’s full account, purchase or checkout workflows. The QA browser reviews submitted no synthetic collector event. No private report counts, credentials or visitor identifiers are published here.