Karelia Conversions
Server-side conversions for Meta, Google and TikTok ads
Ad blockers and browser privacy hide a large share of the leads and sales your ads bring in. Karelia Conversions sends them from your Statamic server to Meta, Google and TikTok, so the ads get credit and learn from them again.
Statamic 6Free to try locally
Listing on the Statamic Marketplace: coming soon.
What it does
A contact form on a Statamic site is often the most valuable thing an ad leads to, and the browser pixel is the weakest way to report it. Ad blockers, Safari's tracking protection and closed tabs stop the pixel, so Meta, Google and TikTok see fewer conversions than you get, and their bidding optimises for the wrong people.
Karelia Conversions reports conversions from your server instead. Choose which forms count as a lead or a contact, and sign-ups and Cargo orders are reported too. Email addresses and phone numbers are hashed before they leave the server, the ad click that brought the visitor is kept after consent, and every conversion shows up in a log in the Control Panel with each platform's answer.

Three platforms
The Meta Conversions API (Facebook and Instagram), Google Analytics 4 through the Measurement Protocol, which you can import into Google Ads, and the TikTok Events API. Switch each on or off.
Forms without code
Choose which Statamic forms count, whether they send a Lead, a Contact, a Sign-up or your own event, and what a lead is worth. Email, phone and name fields are found by themselves.
Sign-ups and orders
Registrations through user:register_form send a sign-up. With Cargo, paid orders send a purchase with the order value and its products.
Keeps the ad click
The fbclid, gclid and ttclid and the UTM tags of the visitor's first visit are kept for 90 days after consent, so a lead that comes back days later still counts for the ad. Works on statically cached pages.
Privacy built in
Email, phone and names are hashed with SHA-256 on the server, the way each platform asks. Nothing is sent before consent unless you choose so. Ready-made rules for Cookiebot, CookieYes and Complianz, or one line of JavaScript for any banner, and a refusal never counts as consent.
A log you can trust
Every conversion in the Control Panel with its value, campaign and each platform's answer, totals per day and source, a dashboard widget and a test button per platform.




Pricing
| Licence | Price | Includes |
|---|---|---|
| One site | $79 | The addon for one production site, with a year of updates |
| Updates after the first year | $29 a year | Optional. The addon keeps working without it |
Bought on the Statamic Marketplace. Local, development and staging copies of your site need no licence, so you can try it for free before you go live.
Hashed on your server, sent only to your accounts
Conversions go straight from your server to the Meta, Google and TikTok accounts you connect. Contact details are hashed before they leave, access tokens stay in your .env file, and the addon never contacts us.
Good to know
- It reports conversions; the platforms decide how many they match and how they use them. How many more you see depends on your visitors, your ads and your consent rate.
- It does not add the Meta Pixel, the GA4 tag or the TikTok pixel to your pages. If a pixel also sends the same Lead from the browser, keep form leads on the server only, or the platform counts both.
- For Google Ads, mark the GA4 events as key events and import them into Google Ads. GA4 ties a conversion to the visitor's session through the _ga cookie when the GA4 tag is on your site.
- Sending happens after the response, or on your queue if you use one, so forms never wait for the platforms.
- Works with Statamic Core and Pro, flat files or the Eloquent driver. Cargo orders need Cargo; forms and sign-ups work without it.
Data and security
Karelia Conversions runs on your own Statamic server and sends conversions only to the Meta, Google and TikTok accounts you connect. Contact details are hashed first, and it never contacts us. The security page lists what is stored, for how long and which permissions are needed. The privacy policy and the EULA are public.