PlaysbyMoat8
Back to the library
The workflow guideMarketing

Track competitor short-form videos

Collect public video metadata, identify recurring formats, and translate useful findings into a competitor content brief.

6 implementation stepsIntermediate

How this works

Collect public video metadata, identify recurring formats, and translate useful findings into a competitor content brief. Public video counts are snapshots rather than a fair ranking of creative quality. The useful output explains repeatable formats and audience questions while keeping posting age, distribution, and unavailable metrics visible.

Collect permitted metadata and captions for a defined competitor set and observation period. Analyze message structure, visual format, and topic recurrence separately from performance. Supply original concepts inspired by general patterns, not copies of a creator's script or an unsupported claim about their conversion results.

Before you start

Competitor scope

Choose relevant accounts and explain why their audience or offer is comparable.

Permitted collection method

Use public pages, exports, or an available authorized connector; record access limits.

Format taxonomy

Define labels such as demonstration, objection handling, tutorial, or customer story before reviewing clips.

Prepare the inputs

account_list
Required

Account IDs and relevance notes

Exclude unrelated high-view accounts from the comparison.

window
Required

Date interval

Keep posting and observation dates separate.

video_records
Required

Metadata rows

Include video ID, duration, caption, visible metrics, and capture time.

format_labels
Required

Controlled list

Define each label with a short example.

target_audience
Required

Audience brief

State which audience questions the research should inform.

Implementation, step by step

  1. Define comparable observations

    • Choose the observation window and capture the same visible metrics for each account.
    • Record whether content is promoted, pinned, or newly published when that information is available.

    Checkpoint: A collection specification with known limitations.

  2. Collect and deduplicate videos

    • Store each permitted video record once using a stable ID and preserve caption text.
    • If captions or metrics cannot be retrieved, keep the row with explicit missing fields.

    Checkpoint: A dated metadata table.

  3. Describe content structure

    • Identify the opening promise, proof or demonstration, payoff, and requested next action.
    • Use captions plus visual review where available; do not infer unseen scenes from the title alone.

    Checkpoint: Structured descriptions linked to the observed material.

  4. Compare formats responsibly

    • Group recurring structures and compare videos with similar age and duration where possible.
    • Treat raw views as an exposure signal, not proof of audience fit, sales, or causal success.

    Checkpoint: A pattern table with representative examples.

  5. Translate patterns into original briefs

    • Connect useful patterns to the team's own product facts and audience questions.
    • Propose a different example, script, and visual treatment rather than imitating identifiable creative expression.

    Checkpoint: A shortlist of original concept briefs.

  6. Review the findings

    • Check a sample of labels against the actual clips and inspect outliers manually.
    • Record collection gaps and the next observation date so future comparisons use the same method.

    Checkpoint: A reviewed competitor content brief.

Decisions along the way

Only a title and thumbnail are accessible

Limit the description to those observations and request fuller material before detailed format analysis.

One clip has extreme views

Inspect age, promotion, and topic context before calling it a winning pattern.

An account changes content strategy mid-window

Split the period instead of averaging incompatible formats.

What you will produce

video-patterns.csv

CSV

Provides a traceable comparison set.

Include: video_id · account_id · published_at · observed_at · format · hook · visible_metrics · missing_fields

competitor-content-brief.md

Markdown

Helps the creative team choose what to test next.

Include: patterns · examples · limits · original_concepts

Check the result

  • Verify IDs remove repost duplicates without erasing meaningful variants.
  • Check that translations preserve the actual promise and tone.
  • Inspect claimed formats against captions or observed frames.
  • Keep unavailable metrics out of averages and rankings.

When something goes wrong

Platform access changes

Stop automated collection and use a permitted export or manual sample.

Captions misrepresent speech

Correct only the reviewed span and retain the uncertain original.

A generated concept closely copies a source

Rewrite around the abstract mechanism and the team's own example.

A worked example

SYNTHETIC EXAMPLE · NOT A REPORTED BUSINESS RESULT

Request

Find useful tutorial formats from three competitor accounts.

Inputs

Synthetic example. Synthetic V1 is a 20-second checklist posted yesterday with 500 views; V2 is a 90-day-old demonstration with 20,000 views.

Expected result

Synthetic expected result. The brief identifies checklist and demonstration patterns but does not rank V2 as better solely by views. It proposes an original checklist using the team's own workflow.

Run a small pilot

Start small

A small fixed account set and one observation period.

Record the baseline

Record manual collection time and disagreement on format labels.

Agree success criteria

Agree usable-label consistency and evidence completeness before expanding coverage.

Stop or revise

Stop performance comparisons when observation dates or basic denominators are unavailable.

Keep the scope clear

  • Collect only material available through the authorized method.
  • Do not infer private campaign spend, sales, or audience demographics from public engagement.

Check before using

Check sampling, translation, and relevance before adapting ideas.

Business activities

  • Create and publish content
  • Research customers and markets

Editorially adapted workflow; not independently tested.

FROM A RECIPE TO YOUR WORKFLOW

Bring the company context together.

This workflow needs reliable inputs before it needs a better prompt. Moat8 Vault brings working information into a readable archive for the AI tools you use.

For this recipe: Public competitor short videos

Start with one recurring task, agree which sources to use, and review the first result with your team.

Discuss this workflow

What does your team do?

Choose the recurring work you would like to improve.

A field guide, made for work.

Plays is a curated library of anonymized business workflows. Each recipe explains the inputs, steps, tools, and checks you can adapt to your team. These are editorial guides, not independently tested implementations.

When you share a company website, the guide may read a limited number of public pages on that website. Messages and retrieved page text are sent to our AI provider, NVIDIA, to recommend relevant workflows. Share a general description rather than confidential information.

Saved workflows and selected activities stay in this browser. Your chat history and selected company website are kept in this tab and cleared when you reload or start a new chat. The server does not store conversations. Live source monitoring is not enabled.

If you allow analytics, PostHog receives page views and actions such as workflow saves, skill downloads and link clicks. Random browser and session identifiers connect these actions without identifying you by name. Your choice and browser identifier expire after 90 days; sessions restart after 30 minutes of inactivity or 24 hours. We use local storage, not analytics cookies. Messages, company URLs, search text, full referrers and IP addresses are not sent. There are no person profiles or session recordings. You can decline or withdraw in Analytics settings; Do Not Track and Global Privacy Control keep analytics off.

Read the Plays Privacy Notice ↗