Tapper Relay server events
Send conversions from your own servers.
Send the sales, bookings and lead stages your own systems record to Tapper once, and Relay sends each one to your ad platforms, matched to the ad click and counted once.
Example conversions
Contract signed, A-2291
$2,400
SENTBooking confirmed, 88213
$310.00
SENTLead qualified, L-5120
Booking 88213 sent again
$310.00
NOT SENTAny conversion you record
Each event counted once
Matched to the ad click
One request for every platform
From your systems to your ads, in one request.
- You set up
01Make a key
Create a workspace key in Tapper that may send conversions, for all your sites or only the ones you choose.
- Your systems send
02Send your events
Your systems send each conversion with its own id, name and time, and a value when it has one.
- Relay delivers
03Relay delivers
Relay checks each event, matches it to the ad click that came with it, and sends it once to each platform.
Every conversion your systems know.
Every conversion is real, matched to its click and counted once.
Any conversion you record.
Bookings, signed contracts, qualified leads: if your systems know it happened, your ad platforms can learn from it.
Safe to send again.
Each event carries your own id, so sending it again never counts it twice.
One request for every platform.
Send once to Tapper, and Relay delivers to each of your ad platforms in its own format.
Test before it counts.
Mark a request as a test to check your events without sending anything to a platform.
Explore the rest of Relay.
Custom sites
Salesforce Commerce Cloud, Magento or a custom build: server-side conversions with no developer work.
Relay for custom sitesGoogle Analytics
The GA4 key events you choose, such as sign-ups and leads, reach your ad platforms as conversions.
Relay for Google AnalyticsLead generation
Lead qualified and deal won go back to the platforms on the ad click, with fake leads held back by default.
Relay for lead generationAll integrations
Every store, CRM and tool Relay connects to your ad platforms.
See every integrationFrequently asked questions
Straight answers about Relay for Server events.
Send a POST request to Tapper with your workspace API key and up to 500 events at a time. Each event has your own event id, a name, the time it happened, and a value and currency when it has them.
The ad click id captured at the visit (gclid, fbclid or ttclid) and the customer’s email and phone hashed with SHA-256, each only where consent allows.
Nothing is counted twice. Relay keeps one record per event id, so a request sent again is safe.
Send what your systems know to your ads.
Get a demo and we will show you how Relay would send the conversions your own systems record to your ad platforms.