PlaysbyMoat8
Back to the library
The workflow guideMarketing

Summarize competitor advertising patterns

Review permitted public ad-library data and create a recurring digest of messages, formats, and creative examples.

6 implementation stepsIntermediate

How this works

Review permitted public ad-library data and create a recurring digest of messages, formats, and creative examples. Public ad libraries show what is visible, not necessarily what is profitable or precisely whom it targets. A useful digest documents message and format changes while resisting the temptation to call a long-running ad a proven winner.

Collect a dated sample of competitor ads through permitted access, identify recurring creative patterns, and preserve representative examples. Distinguish observed text and media from inferred audience cues. The creative team uses the digest to frame original experiments.

Before you start

Competitor registry

Resolve brand and advertiser aliases.

Collection method

Use the permitted public library or an authorized export.

Digest remit

Define the product categories, regions, and observation window.

Prepare the inputs

ad_records
Required

Public library entries

Retain ad ID, visible dates, text, media, and destination.

competitor_ids
Required

Advertiser mapping

Avoid merging unrelated advertisers.

taxonomy
Required

Message and format labels

Define observable criteria.

previous_digest
Required

Prior ad IDs and themes

Identify genuinely new patterns.

audience_brief
Required

Own target audience

Keep inferred competitor audience separate.

Implementation, step by step

  1. Capture the observation window

    • Collect visible records and record the access date and coverage limits.
    • Do not treat an unavailable ad as confirmed inactive.

    Checkpoint: A dated ad inventory.

  2. Normalize and deduplicate

    • Group exact reposts and closely related variants while preserving meaningful copy differences.
    • Keep advertiser and destination references attached.

    Checkpoint: A clean comparison set.

  3. Describe the creative evidence

    • Identify opening promise, proof, format, and call to action from observed media.
    • Mark audience cues as inference unless documented explicitly.

    Checkpoint: A structured creative description.

  4. Find recurring patterns

    • Compare themes with the previous digest and choose representative examples.
    • Use visible counts and dates only for what they establish, not inferred spend or effectiveness.

    Checkpoint: A pattern and change table.

  5. Draft the digest

    • Explain the observed approach and possible relevance to the team's own questions.
    • Include counterexamples and limitations instead of a universal best-practice claim.

    Checkpoint: A concise research brief.

  6. Prepare original next steps

    • Suggest distinct concepts or questions for the creative team to explore.
    • Keep source material private for review and record any authorized internal distribution.

    Checkpoint: A reviewable idea shortlist.

Decisions along the way

An ad has a long visible running period

Describe the period without claiming profitability.

Several variants share one concept

Group them as a family and retain the differences.

Destination page no longer loads

Mark destination evidence unavailable and limit the analysis.

What you will produce

competitor-ad-patterns.csv

CSV

Preserves observable evidence.

Include: ad_id · advertiser · observed_at · format · message · proof · cta · inference_notes

ad-pattern-digest.md

Markdown

Supports creative planning.

Include: new_patterns · examples · changes · limits · original_questions

Check the result

  • Verify descriptions against the actual media.
  • Check dates refer to the library's documented meaning.
  • Separate observed audience language from targeting claims.
  • Confirm repeated variants do not inflate distinct-concept counts.

When something goes wrong

Library access becomes incomplete

Disclose the gap and use a smaller documented sample.

The assistant calls an ad a winner without data

Replace the claim with the visible observation.

A proposed idea copies the competitor script

Rewrite using the team's own message and example.

A worked example

SYNTHETIC EXAMPLE · NOT A REPORTED BUSINESS RESULT

Request

Review public ads for a workflow-software category.

Inputs

Synthetic example. Synthetic A1 and A2 use the same checklist hook with different images; A3 uses a customer quote. No spend data is visible.

Expected result

Synthetic expected result. The digest reports two creative approaches and three variants. It does not rank them by ROI or infer targeting from the imagery.

Run a small pilot

Start small

A few advertisers across two observation windows.

Record the baseline

Record collection effort and unsupported interpretations found in review.

Agree success criteria

Agree pattern accuracy and useful novelty with the creative owner.

Stop or revise

Stop comparative performance claims when only public visibility is available.

Keep the scope clear

  • Public access does not authorize copying complete ads into a new campaign.
  • The digest does not authorize contacting advertisers or altering live campaigns.

Check before using

An ad appearing in a library does not establish its performance or targeting. Keep inferred audiences separate from documented facts.

Business activities

  • Run advertising and acquisition tests
  • 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: Competitor list · Permitted ad-library access · Reporting period and taxonomy

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 ↗