HigherStack Conversion tracking overview
What server-side conversion tracking is, why it’s more reliable than pixels alone, and how to set a value.
If you run ads, conversion tracking tells platforms like Meta or Google Ads when a form submission happens, so they can measure and optimize your campaigns. HigherStack sends these conversions server-side, which is more reliable than a browser pixel alone — it survives ad blockers and works even without a thank-you-page redirect.
How matching works
When someone lands on your form from an ad, the page often carries a click ID (like gclid for Google or fbclid for Meta) and campaign utm_* parameters. The embed captures these, and on submit they’re sent — along with a hashed email/phone — so the platform can match the conversion to the right click. See Tracking & attribution.
Browser pixel and server event use the same event ID, so platforms automatically de-duplicate — you won’t double-count.
Conversion value
You can attach a monetary value to each conversion for value-based bidding. Choose one of:
| Source | Value sent |
|---|---|
| None | No value (the default). |
| Static | A fixed amount for every submission. |
| From a field | Pulled from a numeric answer or calculation (e.g. an estimated deal size). |
Set a currency too (defaults to USD). Non-numeric or zero values are simply sent without a value rather than erroring.
Privacy
Emails and phone numbers are hashed (SHA-256) before they’re sent to any ad platform — raw values are never shared. Your embed can also honor a consent signal so no identifiers are captured when a visitor declines; see the Embed reference.
Set up each platform: Meta, Google Ads, TikTok, LinkedIn.
Still need help?
A dedicated support form is coming soon. In the meantime, jump back into the product or reach the team from the contact page.