Insurance Business Applications paid ads audit: a specific core-modernization pitch flattened by generic landing pages
Insurance Business Applications (IBA) is a Danish insurtech selling IBSuite, a cloud-native, API-first insurance core platform aimed at P&C insurers in Europe. The LinkedIn campaign is unusually specific (named customers like Zurich, AXA, Topdanmark, ManyPets, and Frende, a Celent award, EverGreen architecture, and quantified claims like up to 30% lower core system costs). The five audited destinations all score C, not because the pages are off-topic, but because the H1s read as catalog labels (Customer Cases, Use Cases, IBSuite Insurance Platform) instead of restating any of those specific promises in the first viewport.
Snapshot
- Total ads found
- 46
- Channels
- Matched destinations
- 5
- Unmatched ads
- 0
- Average destination score
- 6.5 / C
How this account runs paid ads
IBA's paid strategy is concentrated on LinkedIn and on one buyer: CIOs, COOs, and architects at European P&C insurers who are evaluating a move off legacy core systems. The campaign sits on top of a single product story: IBSuite is a cloud-native, API-first, EverGreen insurance platform that replaces rigid legacy cores and quantifies the benefit (up to 30% lower core system costs, faster product launches, simpler partner onboarding).
The ad creative is unusually specific for the category. Named customer stories (Zurich, AXA, Topdanmark, ManyPets, Frende) carry a credibility punch most ABM campaigns do not have, and the Celent recognition adds analyst weight. The campaign also splits cleanly by intent: case-study traffic to /customer-cases, brand and broad traffic to the homepage, a dedicated demo page, a use-cases hub, and a platform page.
Where the campaign loses points is the handoff. Every landing page is on-topic but generically titled. /customer-cases opens with 'Customer Cases.' /use-cases opens with 'Use Cases.' /ibsuite-insurance-platform opens with 'IBSuite Insurance Platform.' None of these H1s carry the specific promise the visitor just clicked on (cloud-native, EverGreen, award-winning, claims automation, 30% cost reduction). The result is a steady C grade across the board: not broken, but consistently a half-step behind the ad.
Page report card
Strong proof inventory (named insurer logos) but the page opens with a generic Customer Cases H1 and asks the CIO to navigate to the architectural story the ad teased.
Video and demo ads dump into the homepage. The hero supports the cloud-native pitch but never quantifies the 30% cost reduction the lead ad promises.
Demo page leads with a generic confidence headline. The four acceleration benefits from the ad body (time to market, product launch, IT cost, no-downtime) never appear above the form.
Three specific ad themes (pet claims, customer-satisfaction claims, motor innovation) all dump into one Use Cases hub, so each visitor has to scroll to find the video that matches the ad they clicked.
Hero never mentions cloud-native, EverGreen, or the Celent award (all dominant ad hooks). Reads as a module catalog instead of a modernization pitch.
This table only shows pages with a reviewed ad sample and a published score.
Common patterns
// Pattern 01
Specific ads, generic page H1s
The LinkedIn creative is full of named customers, named awards, named architectural choices (cloud-native, API-first, EverGreen), and quantified outcomes (30% lower core costs). The landing pages open with category labels like Customer Cases, Use Cases, and IBSuite Insurance Platform. This is the single most consistent pattern in the account: the ad does the specificity work, and the page resets to a generic catalog frame.
// Pattern 02
Multiple ad themes funneled into one hub URL
/use-cases takes three different ad themes (pet claims, customer-satisfaction claims, motor innovation). /customer-cases takes a similarly diverse cluster of named-insurer stories. Each cluster would convert better if it deep-linked to its matching anchor or sub-page rather than the hub, so the visitor confirms in one scroll that the specific story they clicked on lives on this page.
// Pattern 03
Strong proof inventory, but proof lives below the fold
The pages have the proof (named logos, Celent recognition, 20+ insurers, 500M+ monthly transactions, 20M+ policies). It is almost always one scroll down from where the ad's claim lands. Moving one or two of those proof points into the hero band would close most of the visible message-match gap without rebuilding a single page.
// Pattern 04
European P&C focus that the pages never explicitly state
Every customer named in the ads is a European insurer, and the buyer profile (CIOs and architects at P&C insurers) is consistent across the campaign. The landing pages do not name that region or that buyer, which leaves a small persona-confirmation gap. A single subhead naming European P&C insurers would tighten this for free.
Should you copy this playbook?
Copy the ad construction. Naming specific enterprise customers in B2B SaaS ads is rare for a reason: most accounts cannot get the logo permissions and the legal review through fast enough. IBA evidently can, and the result is a LinkedIn cluster that punches above its category in credibility. The Celent recognition and the EverGreen and API-first architectural language also do real work for the architect buyer.
Do not copy the catalog-page handoff. The lift here is mechanical and almost free: when an ad uses a specific phrase (cloud-native, award-winning, EverGreen, 30% lower core costs, accelerate insurance growth), the destination H1 should repeat that phrase. Generic page labels (Customer Cases, Use Cases) signal that the visitor has landed on a hub, not on the specific story they clicked, and that signal costs continuity even when the page underneath is on-topic.
Also, do not pool diverse ad themes into one hub URL without deep links. The use-cases page is the clearest example: three distinct ad clusters land on the same general page, and each visitor has to find their own video. A pair of #anchor links or dedicated sub-pages would lift conversion without changing any ad creative.
Sources
- LinkedIn Ad Library: Public ad transparency data for Insurance Business Applications, captured 2026-05-19
- Destination pages: Five ibapplications.com pages (customer-cases, homepage, book-a-demo, use-cases, ibsuite-insurance-platform) scraped from the LinkedIn ad set
Want the same teardown for your account?
PostClickSignal grades every paid destination against its matched ads, so you see exactly where the message breaks. Free for the first audit.
Audit my full account