Home › Integrations

Conversion APIs: what Microsite Generator does instead

What sits in place of a conversion API

There is no screen where you connect an ad account. No dataset ID to paste. Nothing in the product that talks to Meta or Google Ads on your behalf.

What you get is the event itself, the moment it happens. A lead from your microsite is posted to any HTTPS address you name, with a signature your end can check. So the fact of it reaches you with no doubt about where it came from.

That event is the raw material every conversion API runs on. The only difference is who does the last hop.

Why the last hop stays with you

A conversion upload is not a neutral pipe. It carries keys to an ad account that spends your money, and it encodes a judgement about what counts as a conversion.

Neither of those is ours to hold. Handing us your ad keys so we can claim conversions for you is a lot of trust for a little convenience.

So we ship a signed event you can route, rather than a black box you have to believe. It is the same instinct as the compliance gate — the check that validates every page against Google Search Essentials and modern web standards before it publishes.

How teams wire it up

The pattern is short, and it is the one you would build against any provider's webhook.

• Point the lead webhook at an address you own, and check the signature when it lands.
• Map the lead's fields to what your destination expects, and drop anything you would rather not send.
• Forward to the ad platform from your own server, with your own credentials.
• No server to spare — Zapier, Make and n8n all start on an inbound webhook.
• Send it to your CRM too — HubSpot, Zoho and Pipedrive match on email instead of adding a duplicate.

Prove the path before it matters

Connecting anything here needs no sign-in screen. You paste the key, ID or address the tool gives you, and a Send test lead button proves the connection before a real lead depends on it.

Do that first. Watch the test land at your address. Then wire the forward.

It is a small habit, and it turns an integration you hope is working into one you have watched work. Your pages get the same treatment. Each one is individually built and has to prove it is genuinely useful before it publishes, not after.

Updated October 2026