Internal Tools

LEV Wigs Analytics Tools

An introduction to the internal analytics tools behind levwigs.com — what they do for LEV's operators, what they can and cannot read through Google, and how their authorization is managed. The governing detail lives in the two policy pages linked at the end of this page.

Application
B2B Data Dashboard (Google OAuth application)
Used by
Authorized LEV operators
Access
Read-only Google scopes
Contents

01

What the tools are

LEV Wigs uses a small set of internal analytics tools to understand how levwigs.com performs in Google Search. The tools connect to Google through an OAuth application registered as B2B Data Dashboard, used from a desktop client identified as LEV SEO Readonly. Together, they bring Google Search Console and Google Analytics (GA4) report data into the analysis workflow on an operator's own computer.

B2B Data Dashboard is an internal LEV utility, not a public service. It is not a customer login, not a hosted dashboard, and not something offered to website visitors — and this page provides no access to anything. The name shown by Google may vary depending on the authorization screen.

Not a Google-verified product

The application has not completed Google's verification process. LEV does not claim Google review, endorsement, or certification for these tools, and publishing this page is not a claim that any Google approval has been obtained.

02

What operators use them for

The tools support LEV's internal work on its own website:

  • Internal reporting — regular summaries of how levwigs.com pages perform in Google Search and how traffic behaves in GA4 aggregated reports.
  • SEO analysis — checking which queries and pages are gaining or losing visibility, and diagnosing what needs attention or repair.
  • Content planning — deciding which pages and guides to write, improve, or restructure next.

Report data is used for these internal purposes only. It is not sold, and it is not used for advertising. The full set of rules that govern use of the tools is set out in the Analytics Tools Terms of Use.

03

Data access and the read-only boundary

Through the authorized Google connection, the tools read two kinds of reporting data:

  • From Google Search Console: search performance data — the queries pages appeared for, the pages that were shown, and their clicks, impressions, and average positions.
  • From Google Analytics (GA4): aggregated report data, such as traffic sources, session and engagement metrics, and configured event counts.

The connection requests exactly two read-only authorization scopes:

  • https://www.googleapis.com/auth/webmasters.readonly — Google Search Console performance data
  • https://www.googleapis.com/auth/analytics.readonly — Google Analytics (GA4) reporting data

Read-only means exactly that. The connection cannot publish or edit website content, cannot change Search Console or Analytics settings, and cannot submit changes anywhere on LEV's behalf. These scopes do not grant access to Gmail, Google account passwords, payment account credentials, or card details. GA4 reports may include purchase and revenue metrics where configured.

Operators work with the resources they select and are authorized to access in their own Google account. The connection itself is not a technical restriction to a single website or Analytics property.

One measurement caveat: an event count in GA4 — including an event named generate_lead — is a counter, not a verified outcome. LEV does not treat event counts as confirmed inquiries or sales.

04

How report data is handled

The reporting connector runs locally on the operator's own computer. Reports and summaries pulled by the tools feed LEV's internal analysis workflow, which includes coding and analysis assistants such as Codex and Claude Code. Selected reports or summaries may be processed by external AI services as part of that work.

Running the connector locally does not mean all processing stays on that computer. How report data may be stored, retained, and shared — including the checks that apply before anything is sent to an external AI service — is described in the Analytics Tools Privacy Policy.

Where the detail lives

This page is an introduction. Handling, storage, retention, and third-party boundaries are governed by the Analytics Tools Privacy Policy and the Analytics Tools Terms of Use.

05

Managing the authorization

Each operator connects the tools with their own Google account and chooses which resources to work with; access follows what that account is already authorized to see.

Access can be revoked at any time in the Google Account under Security › Third-party apps with account access (also shown as "Your connections"), by removing the connection associated with B2B Data Dashboard. Google's own instructions are available in the Google Account help center.

Revoking stops further data fetching. It does not delete reports that were already saved; the separate steps for stopping use of the tools are set out in the Terms of Use.

06

Policies and contact

The two policy pages are the authority for how these tools operate. This introduction summarizes them and does not replace them.