# How to use a Righthand with Wistia

Use Righthand to prepare a Wistia review connecting each video's identity, reported activity, and next editorial question.

By Righthand Team · 2026-10-11

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

## Quick answer

Use Righthand to prepare a Wistia review connecting each video's identity, reported activity, and next editorial question. Keep media replacements and embed changes with the owner.

Start with a reviewable deliverable, keeping Wistia as the accepted home for its records. This guide uses an explicitly approved snapshot or browser read; it does not assume that every provider API action is exposed by your Righthand connection.

## Evidence and access

Wistia documents a media statistics endpoint. See the [official Wistia reference](https://docs.wistia.com/reference/get_stats-medias-mediaid). Provider capabilities and Righthand's available tools are separate checks.

Request a limited video report with the owner's metric definitions, date range, and embed context; exclude unrelated media projects. Verify the required tools and owner-approved scope through [Righthand integrations](/integrations); use the supplied packet when a native read is unavailable.

## Define the objects and authority

Include these fields in the working input: media ID, title, embed destination, report window, reported statistics, review owner. These are the requested review columns, not a promise that every provider endpoint returns them under those exact names.

Statistics use provider event definitions. They do not establish the cause of audience behavior or a sale.

| Responsibility | Owner |
| --- | --- |
| Prepare source scope and access | Account owner |
| Organize evidence and proposed next steps | Righthand |
| Approve consequential changes | the content lead |

## Illustrative first-run brief

> Use the owner-provided Wistia snapshot or approved read-only view. Compare three product videos using the supplied media inventory and statistics report. Draft review questions without replacing media or changing embeds. Run once for the agreed sample, using America/Los_Angeles for the review deadline and preserving source timestamps separately. Return the draft in this conversation by Friday at 3 PM Pacific for the content lead to review. Include source references and missing fields. Do not write records, spend money, change permissions, or send external messages. Stop and report an unavailable source rather than substituting another account.

## Expected result and verification

One media ID may serve several pages. List that ambiguity instead of crediting all viewing activity to one landing page.

Match a media ID to the original media page and selected interval. Record the source cutoff, applied filters, and items excluded from the sample. The reviewer should be able to follow each consequential finding back to an original object. A well-written summary is not evidence that a proposed action happened. If a later write is authorized, verify its specific result separately before changing the task's status.


### Illustrative input and draft output

These synthetic entries show the requested review, not live account results or a provider field schema.

| Source item | Supplied observation | Draft conclusion |
| --- | --- | --- |
| Media A | Matching window and embed | Comparable report |
| Media B | New landing-page placement | Annotate distribution change |
| Media C | Window not supplied | Hold trend conclusion |

## Common failure and recovery

An embed can still reference an older version. Check the actual identifier and separate assets before comparing statistics.

When multiple embeds share a video, separate their context or label aggregation. Ask the owner before comparing unlike audiences as one trend.

## FAQ

### What should the reviewer verify first?

Match the media identifier and window to the report. Preserve play and engagement definitions rather than treating every viewed event as a complete watch.

### How should a repeat run be scoped?

Retain media IDs, embed context, and reporting filters for each review. Compare equivalent windows and annotate changed distribution; increased exposure may change the audience mix.

For connection and permission details, use [Righthand Docs](https://docs.righthand.ai). Review [Pricing](/pricing) alongside any separate provider charges before expanding the workflow.