Server-side tracking

Server-side tracking is sending a measurement or conversion event from a server the business controls to an analytics or advertising system, instead of relying only on a script running in the visitor's browser. Common examples are Meta's Conversions API, Google Analytics 4's Measurement Protocol, and server-side tag containers.

How it differs from a pixel

A browser pixel reports what happens on a page where it is installed, and it misses events when a browser blocks it, a visitor declines consent, the page closes early, or the action happens on another site. A server event is sent when a system records something, such as a stored lead or an investment status change, so it does not depend on a confirmation page loading.

It is a different delivery path, not a way around privacy rules. It needs the same notice, consent where required, and permission to share the data. It also cannot recover an ad click that was never observed; matching still depends on an identifier the destination recognizes.

Deduplication

Most setups send the same event from both the browser and the server for coverage. The destination then needs a way to count it once. Meta deduplicates a browser and a server event that share the same event name and event_id, as its deduplication guide describes. Without a shared ID, one reservation can be reported as two conversions.

Use in a raise

In an equity crowdfunding offering the most valuable server event usually comes from the intermediary: a postback when an investment reaches an agreed state, and later events for cancellations or failed reconfirmations. The issuer's own server can report interest recorded on a testing-the-waters form. Events sent to ad platforms should carry the minimum needed for campaign decisions; investment amounts, identity documents, and investor eligibility data do not belong in them by default, and a hashed email is still an identifier. Reconcile event counts against the intermediary's ledger before calculating cost-per-investor. See also cross-domain-tracking.

Further reading

• Pixels, server events, and consent in a raise
• Cross-domain tracking for a raise
• The measurement dashboard for a raise