The starting point
Meta rejected ads that promised pay and help with papers, and some campaigns were split by age and gender. The landing pages sent leads, but without tags: one care work campaign had 145 leads for 3,838 zł that could not be found in the CRM.
What I built
- One landing page per job. Fast static pages with AI images, a clear WhatsApp button and a form that fills in the country code from the visitor's location.
- Tracking without double counting. Every lead goes to the CRM, to the team in Telegram and to Meta through the Conversions API, with one event ID in browser and server.
- A code in WhatsApp. Each page adds a short code to the first message, so the chat ties back to the ad.
- Copy that gets approved. Banners and texts rewritten without promises about pay and papers, and without age or gender requirements.
- Campaigns on Meta and Google. Click to WhatsApp, lead form and website campaigns in several languages, plus three Google Search campaigns.
- Cuts based on CRM data. Campaigns with a high cost per qualified lead were stopped and the budget moved to the best ones.
- Visible in Google. JobPosting structured data, a sitemap, llms.txt, IndexNow and Search Console.
The result
The new campaign with rewritten copy had all four ads approved and brought 67 leads at about 7.7 zł each. The care work landing page delivered the lowest cost per qualified lead in the whole account, 33 zł. A seven day review showed that without six weak campaigns the cost per qualified lead would have been 42 zł instead of 53 zł, and those campaigns were stopped.
The numbers were tracked in the Meta ads and CRM dashboard.
Tools and tech stack
- Meta Ads
- Google Ads
- Conversions API
- JobPosting schema
- IndexNow
- Google Search Console
- AI bilder
The client is anonymised. The numbers come from the project's own reports and measurements.
Want this for your business? See Meta ads specialist or Meta Conversions API setup.










