An honest read on the first 27 days of the mSDK v2 launch campaign on LinkedIn. We ran three weeks that got engagement but zero leads, worked out why, and in week 4 switched every cold audience to LinkedIn's native lead forms. That's when the first leads landed, carousel CTR tripled, click cost roughly halved, and spend finally hit plan pace.
Three weeks of ads brought traffic but no leads. The audiences engaged from early on, so the problem was never who we targeted, it was where we sent them. In week 4 we moved every cold audience onto LinkedIn's native lead forms, and the numbers moved with it: the first two leads landed, carousel CTR jumped, and clicks got cheaper.
We went live on 16 July with the planned structure, all pointing at the website lead form. Traffic came in, 98 clicks in the first stretch, but zero leads. CTR sat at 0.36%, under the 0.44% pass mark for LinkedIn sponsored content, and spend paced at about R680/day, well under the ~R1,250/day the R50k plan needs to finish on time. Enough was moving to see the shape of it, and the shape was people clicking but nobody converting.
Next we did the obvious housekeeping: cut bids to R65, shifted budget off the weaker C1 onto the stronger C2, and trimmed the lead form from 7 fields to 4. All worth doing, none of it moved the number that mattered. Still zero leads. This is the point where it became clear the problem wasn't the settings, it was the destination we were sending clicks to.
We built a 105-agency target list, companies like Polymorph that build apps for their own clients, and launched a dedicated ad set with a "build once, ship everywhere" angle. It immediately posted the best CTR on the account (~1%), which told us the audience read was right. But it was still landing on the same non-converting website form, so it still produced zero leads. Right people, wrong door.
A landing-page audit found the real problem. The page was written for merchants while the best-performing ads were aimed at developers, the form sat below the fold on mobile, and a sales lead-form is the wrong ask for a developer sizing up an SDK. So we switched every cold audience to LinkedIn native lead forms, in-feed and pre-filled from the member's profile, with a "Request Demo" CTA, and restored the planned carousel plus single A/B. CTR rose to 0.45% overall with the developer and dev-agency carousels at 0.78–0.92%, their CPC dropping to R22–36 (cheaper than the old manual sets), spend hit plan pace at R1,161/day, and the first two leads landed, one from Developers and one from Dev Agencies.
Developers and dev-agencies engaged from early on and posted the best CTRs on the account. The targeting was right the whole time. The problem was where we sent them.
A cold audience won't fill a sales lead form on a merchant-focused page for a developer product. Removing that friction (native in-feed form, developer message, "Request Demo") is what unlocked the leads.
Carousels beat single images consistently, and on the native forms the developer carousels are also the cheapest clicks at R22–36, while the single-image lead-form sets ran R175–236 per click. That's a clear signal for where to concentrate the rest of the budget.
The real demos this campaign era came through the customer newsletter and a sales-shared link, not the ads. That reinforces the ads' job: widen the top of the funnel, and make the cold offer match a developer's intent.