Customer StoriesPricing

Use case

Test ad reception in the field, not the focus group

Pair any brand’s live ad set with the audience conversation around it, and reception stops being a guess.

Get your API key

The short answer

Waldo tests ad reception with field evidence: pull a brand’s active ads, then read the audience conversation around the campaign, clustered into themes. Days-live metadata shows what a brand keeps funding, comment and transcript lookups show how people respond, and the whole loop runs on one API and MCP surface.

The job to be done

A media planner wants to know how creative is landing before doubling the budget behind it, and the standard answers disappoint. Panel pre-tests are slow, artificial, and measure a forced exposure nobody chose. Post-launch, reception lives in comment sections and quote posts that no one reads systematically, and competitor reception is invisible entirely.

The field already runs the test. What stays live is what someone keeps paying for, what the audience echoes or mocks is written down in public, and both signals exist for every brand in the category, not just yours. The job is reading that evidence deliberately instead of anecdotally.

How Waldo does it

Pull the set under test

GET /brands/{id}/ads/active returns the full running set for any tracked brand, yours or a rival’s. One real pull returned 14,793 active Meta ads for a single brand, so sampling is a choice, not a constraint.

Read days live as revealed preference

An ad that has run for ninety days is an ad someone renewed ninety times. Days-live metadata sorts the set into what the market rewarded and what it did not.

Listen to the reception

GET /audiences/{id}/conversations clusters what the audience says around the campaign’s themes, and enrichment endpoints pull the comments and transcripts where reception actually happens.

Score angles, not executions

Roll reception up by angle using scored analysis, and the finding feeds the next brief directly: this framing earns imitation, that one earns screenshots for the wrong reason.

The endpoints

/brands/{id}/ads/activeThe full running set with creative, copy, and days live
/audiences/{id}/conversationsWhat the audience says around the campaign, clustered
Enrichment endpointsComment and transcript lookups where reception lives
MCP: discover_adsFollow-up ad pulls inside the working session
14,793Active Meta ads in one tested set, real pull
24hRefresh cycle for tracked brands
200+API and MCP endpoints

Questions teams ask

Does this replace panel pre-testing?

For some teams it complements it, for some it replaces it. Field reception reads real behavior at category scale, panels read controlled response pre-launch; the honest position is that they answer different questions.

Can I test a competitor’s reception?

Yes, and that is half the value. Their live set, their days-live data, and the conversation around their campaigns are all readable, so their budget becomes your experiment.

What data comes with each captured ad?

Creative, copy, days live, and metrics, stored permanently even after the ad stops running. Pulled campaigns stay readable, which matters when the interesting result is the one a brand retired early.

Keep reading

What is creative testing?The testing landscape this field method fits into.What is message testing?Testing the claim rather than the execution.Waldo for media plannersThe planning workflow reception reads feed into.Waldo BuildThe API and MCP server behind the field data.

Put Waldo behind your agents

Brand, category, and audience intelligence over 200+ API and MCP endpoints. Sign up, mint a key, and run it against the brands you actually track.

Get your API key
See everything. Miss nothing. Move first.
Get startedContact us
CompareAlternativesUse casesWho it's forGlossaryAudiences
Find us on LinkedIn • X -Twitter
Copyright 2026 • All Rights Reserved • Terms of Service • Privacy Policy