# How to use a Righthand with Google Analytics

Prepare a reviewed campaign-metric definition and freshness brief from approved Google Analytics inputs, with a worked brief, access checks, and reconciliation.

By Righthand Team · 2026-10-10

Source: https://www.righthand.ai/blog/how-to-use-righthand-with-google-analytics

## Quick answer

Use an approved Google Analytics report slice to prepare a campaign brief whose metric definitions and freshness are explicit. Righthand can organize the supplied report, while the analytics owner decides whether differences are meaningful.

Start with a **campaign-metric definition and freshness brief** that the analytics owner can check against the original records. Righthand prepares the review artifact; the source application remains the operational record.

## Establish the input route

Google’s Analytics Data API documentation describes programmatic reports for Google Analytics properties using dimensions and metrics. [Official Google Analytics reference](https://developers.google.com/analytics/devguides/reporting/data/v1), checked October 6, 2026.

The analytics owner should supply the property reference, report date range, dimensions, metrics, and filters. For a connected route, verify property permission and the available report operation. A screenshot without its report definition is inadequate for comparing campaigns reliably.

Check the current [integration directory](/integrations) and [Righthand setup documentation](https://docs.righthand.ai/introduction). A listed app does not establish every read or write action. For a connected route, verify the assigned account, available operation, object scope, and one permitted sample read. This guide also works from an explicitly supplied, approved extract; it does not require an unverified native operation. Keep credentials out of the article brief.

## Worked input and output

These three records are synthetic illustrations, not customer results or a hands-on integration test.

| Approved input | Proposed review output |
| --- | --- |
| GA61: campaign A has sessions and users columns | Keep both measures; do not relabel sessions as people |
| GA62: prior report used a different channel filter | Flag definition mismatch before calculating change |
| GA63: current day is only partly observed | Label incomplete period rather than compare with a complete day |

The brief should lead with the actual reporting question and its measure. GA61 prevents a common unit confusion. GA62 means the apparent difference may reflect selection rather than performance, while GA63 requires a comparable cutoff before any trend statement.

## A complete first-run brief

> Use an approved Google Analytics report extract and measurement definitions for October 12–16, 2026. Fields: property reference, report range, dimension names, metric names, campaign value, filter definition, property timezone, extraction time. At Monday 9 AM America/Los_Angeles, prepare a campaign-metric definition and freshness brief as source-linked Markdown in my private review thread. Preserve record identities and the extract timestamp. Group unresolved items by next action and responsible owner. Reviewer: analytics owner. Do not change tracking, edit campaigns, alter budgets, infer causation, or publish performance claims externally. Result check: Reproduce one campaign row with the same property, date range, dimensions, metrics, and filters.

A permitted preparation step does not authorize a consequential write or an external send. Resolve proposed changes through the app's supported process after the responsible owner approves their exact scope.

## Reconcile before widening the task

A campaign name can exist in several dimension contexts. Preserve the exact dimension instead of joining on display text casually. Reporting evidence also does not establish causation; do not attribute a change to a campaign edit merely because their dates overlap.

Trial one weekly campaign review with a frozen definition. Ask the owner to reproduce GA61 and explain GA62’s filter difference. If accepted, reuse the definition and date rules on the next fresh slice while leaving budget changes to the authorized decision-maker.

For the first acceptance review, keep the original input slice beside the result and mark which items were checked. If access or evidence is incomplete, return that gap with its record identity rather than a confident completion statement. Review [Pricing](/pricing) using the actual preparation workload and correction effort.