Integrations / Advertising

Topsort

Server-to-server purchase event delivery to the Topsort Events API (/v2/events) for retail-media ad attribution. Forwards Order Completed events to the purchases array, keyed on Signal's pseudonymous anonymous_id as the Topsort opaqueUserId. No PII is sent — Topsort matches on the opaque user ID only.

Datafly Signal delivers first-party events to Topsort server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Topsort expects.

Why route Topsort through Datafly Signal

Conversions survive ad blockers and tracking prevention

A browser tag served from an advertising domain is blocked outright for part of your traffic, and Safari's ITP shortens the cookies it can set. Signal sends the event from your own server, so the conversions Topsort optimises against are not filtered by the browser.

Delivery is batched, rate-limited, and retried

Signal buffers to Kafka, respects the Topsort rate limit, and retries on 429 or transient failure rather than dropping the event.

One consent decision governs every destination

Topsort is gated by the same consent state as the rest of your stack, so a withdrawal applies everywhere at once.

What ships in the blueprint

Mapped events

_comment_unsupported_eventspurchase

Vertical presets

Default. Each preset starts from a working configuration for that vertical rather than a blank field map.

Full field mappings, configuration fields, and troubleshooting are in the Topsort documentation.

Frequently asked questions

Does Datafly Signal integrate with Topsort?

Yes. Datafly Signal delivers first-party events to Topsort server-to-server from infrastructure you control, using a pre-built blueprint that maps your event schema to the payload Topsort expects. The integration is included in every deployment at no additional cost.

How is server-side Topsort tracking different from the Topsort tag?

The Topsort tag runs in the visitor's browser, so it is subject to ad blockers, tracking prevention, and page-unload races. Signal collects the event through a first-party endpoint on your own domain and delivers it to Topsort from your server, so delivery does not depend on browser conditions.

Which events can Signal send to Topsort?

The blueprint ships with mappings for _comment_unsupported_events, purchase. Any event in your schema can be mapped to Topsort through pipeline configuration without a code change.

Do I need to keep the Topsort tag on my site?

No. Server-side delivery is designed to replace the tag. Most teams run both briefly during migration, using shared event IDs so Topsort deduplicates, then remove the tag once server-side volume matches.

Ready to move Topsort server-side?

See how Datafly Signal delivers first-party events to Topsort from infrastructure you control, with hashed identity and consent enforcement built in.