Server-side conversion tracking
Send consented events to Meta CAPI, TikTok Events API and Google Ads from your server rather than the browser.
Send consented conversion events server-side, compare platform reports with first-party records, and find where attribution drops.
Web and app conversion events
Collect the first-party event and its consent state.
Consent and identity rules
Apply the rules before the event moves downstream.
Ad platforms and analytics
Send the configured server-side signal and keep a first-party record.
Collection, policy, and delivery rules sit in one event path, so marketing teams can see what happens before data leaves.
Send consented events to Meta CAPI, TikTok Events API and Google Ads from your server rather than the browser.
Use first-party identifiers and server-side events where third-party cookies are unavailable.
The consent state collected at the source travels with the event and decides what each destination is allowed to receive.
See the traffic, campaign and conversion events Hardal received, in dashboards you own.
Build audiences from consented events and push them to the ad platforms you already run.
Compare the events Hardal sent with the totals each ad platform reports back.
Measure more of the conversions browser-only tags miss.
Send consented server-side signals to ad platforms.
Trace a reporting gap back to the events you hold.
Hardal uses encrypted transport and managed access controls. Its security programme includes ISO 27001, ISO 27701, and ISO 9001:2015 certifications. Check the Trust Center for scope and certificate details.
Send us your current pixel and consent setup. We will show which destinations move first.