AdRoastWhy is Descope's sharp CIAM ad sending buyers to the wrong page?
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.
The original teardown, on LinkedIn
The full infographic and commentary, straight from the post. Open on LinkedIn
The ad to landing page journey
A strategic ad, an implementation tutorial.
What the ad gets right
- The ad copy is specific, category-aware, and written for a CIAM audience with a real strategic problem.
- Every line earns attention: token issuance, non-human identities, consent after the token.
- It meets problem-aware buyers exactly where their thinking is.
Where it breaks after the click
- Audience: the ad speaks to CIAM leaders, the page serves developers.
- Author signal: the ad sounds brand-level, the landing experience feels DevRel-led.
- Content type: the ad hints at a strategic read, the page delivers an implementation tutorial.
- Buying stage: the ad meets problem-aware buyers, the page assumes implementation-ready intent.
The fixes I would prioritize
Keep the developer blog for organic traffic, and send paid traffic to a true Agentic Identity Hub page.
Add customer logos and one named testimonial with a metric.
Segment campaigns by role: developer ads to the blog, CIAM ads to the product.
Replace the CTA with "Get the CIAM buyer's guide" or "Book a walkthrough".
“Descope clearly has two ICPs, developers and CIAM leaders, and paid traffic is being pushed into the wrong experience.”Marina Kogan, on the Descope campaign
This teardown is based on Marina Kogan's public analysis of Descope's live LinkedIn ad and landing page, published August 3, 2026.
Questions, answered
What does Descope's ad get right?
The ad copy is specific, category-aware, and written for a CIAM audience with a real strategic problem. Every line earns attention: token issuance, non-human identities, consent after the token. It meets problem-aware buyers exactly where their thinking is.
Where does the Descope funnel break?
Audience: the ad speaks to CIAM leaders, the page serves developers. Author signal: the ad sounds brand-level, the landing experience feels DevRel-led. Content type: the ad hints at a strategic read, the page delivers an implementation tutorial. Buying stage: the ad meets problem-aware buyers, the page assumes implementation-ready intent.
How would you fix the Descope funnel?
Keep the developer blog for organic traffic, and send paid traffic to a true Agentic Identity Hub page. Add customer logos and one named testimonial with a metric. Segment campaigns by role: developer ads to the blog, CIAM ads to the product. Replace the CTA with "Get the CIAM buyer's guide" or "Book a walkthrough".
Get these teardowns in your Google feed. Tap the button to make AdRoast a preferred source in Search, Discover, and News.
Want this on your own ads?
AdRoast pulls your live LinkedIn and Google ads, scores each one against your buyer, and shows exactly where the click leaks. Paste a URL, that is it.
Roast your ads free →