Teach ad platforms what really converts
When a recognised ad click turns into a sign-up or purchase, PathClue sends the conversion back to the ad platform server to server — so bidding learns from real results, not lost pixels.
- 8 ad platforms
- Server to server
- Delivery status and retries
Conversions that arrive
Browser pixels miss conversions. Server-side sending doesn’t depend on the browser.
Eight platforms
Google Ads, Meta, TikTok, Microsoft Advertising, Ocean Engine, Baidu, Tencent Ads and Kuaishou.
Click IDs kept
Click IDs from 14 ad platforms are kept on the visitor, so later conversions still match.
Offline conversions
Import phone orders or in-store sales from CSV; matched ones are sent too.
Delivery status
See what was sent to each platform, with automatic retries.
Set it up once
- 1
Connect the ad account
Add the platform’s credentials in the console.
- 2
Pick conversions
Choose which events count — sign-up, purchase, lead.
- 3
Check delivery
Watch the status per platform and conversion.
What the conversion API solves
Why does the ad platform show fewer sales?
Blocked pixels and lost cookies — server sending fills the gap.
Can offline sales count?
Imported offline conversions that match a click are sent back.
Will bidding improve?
Bidding learns from conversions it receives; more complete data helps.
Conversion API questions
Anything else — open the chat in the corner and ask.