AdRoastAdRoast/ TeardownsRoast your ads free
Ad teardown · CIAM / Identity

The ad was written for a buyer.
The page was written for a developer.

The ad copy is genuinely strong and category-aware, written for CIAM leaders with a real strategic problem around agentic identity. Then the click lands on a 3,000-word DevRel tutorial full of Python and MCP snippets. Descope clearly has two ICPs, developers and CIAM leaders, and paid traffic is being pushed into the wrong experience. You do not need more traffic when the conversation after the click falls apart this badly.

Descope
Descope
descope.com · LinkedIn
Wrong pageVerdict

The teardown, on LinkedIn

The ad, torn apart
LinkedIn post
Open on LinkedIn →

What the teardown found · tap to open each one

What’s happening

Every line earns attention: “Auth stops at token issuance,” “NHIs outnumber humans 20:1,” “57% of CIAM leaders fear agents sharing data.” It is concrete, it names the problem, and it speaks the CIAM leader’s language.

What’s happening

The copy is sharp, but there are no customer logos and no Descope-specific proof points. The stats frame the problem well; nothing yet shows Descope is the answer.

The fix

Add one named customer or a Descope-specific result so the strategic frame has a payoff attached to it.

What’s happening

The CTA “See the strategic read” lands on “Monitoring and Auditing Agentic Identities,” a 3,000-word technical post with Python, MCP and Snowflake snippets, bylined by a Developer Relations Engineer. Zero customer logos, zero testimonials, zero named customers. The buyer who clicked for strategy gets handed code.

The fix

Send the paid CIAM-leader click to a strategic page, the executive read the ad promised, and keep the DevRel tutorial for the developer funnel it was written for.

Questions, answered

The ad is one of the sharpest in the series: specific, category-aware copy written for CIAM leaders, with real stats on agentic identity. Its only gap is proof, no named customers or Descope-specific results. The real problem is not the ad, it is the page it sends you to.
At the click. A strategic ad written for a CIAM buyer lands on a 3,000-word DevRel tutorial full of Python and MCP snippets, written by a Developer Relations Engineer. Descope has two ICPs, developers and CIAM leaders, and the paid traffic is going into the developer experience.
Match the page to the buyer the ad targeted. Send the paid CIAM-leader click to the strategic executive read it promised, and reserve the implementation tutorial for the developer funnel. The traffic is fine; the destination is wrong.
If you sell to more than one ICP, click your own ad as the buyer it targets and ask: is this page written for me, or for someone else in the org? Paid traffic landing in the wrong experience wastes the best copy you have. AdRoast scores this automatically, and the first roast is free.

This is Marina Kogan’s original teardown of Descope’s live ad. See the full infographic on LinkedIn →

More teardowns

Silverfort
The right message, in the wrong order.
Read the teardown →
Cycode
Four analysts sold the click. The page hid them.
Read the teardown →
Hyperproof
A privacy hook that lands on a compliance page.
Read the teardown →

Your ads, roasted the same way

Pull your live ads, score each against your buyer, see where the click leaks.

Roast your ads free →