Overview

Server-to-Server (S2S) conversion tracking lets you send conversion events directly from your backend server to Vibe, without relying on a browser-based pixel. This is useful when conversions happen outside of a web browser (e.g., phone orders, CRM events, in-store purchases) or when you want more control over what data is sent to Vibe.

S2S events are used for attribution and reporting in your Vibe campaigns. They appear alongside pixel-tracked conversions in your campaign reports.

Prerequisites

Before using S2S conversion tracking, you need to set up a Vibe Pixel in your account. The S2S endpoint requires your Pixel ID, which is generated when you create a pixel.

If you haven't set up a pixel yet, follow the instructions in Web Tracking to create one first.

How it works

A conversion happens on your side (e.g., a purchase, a lead form submission).
Your server sends an HTTP request to Vibe's S2S endpoint with the event details.
Vibe matches the event to a household using the IP address provided.
The conversion is attributed to the relevant Vibe campaign and appears in your reporting.

Endpoint

Send a GET request to:

https://tracker.vibe.co/s2s-conversion/events

Required parameters

All parameters are passed as query string parameters.

Parameter	Description	Required
`aid`	Your Pixel ID. You can find this in Settings > Web Tracking after setting up your Vibe Pixel.	Yes
`a`	The conversion action name. Use the same action names configured in your Vibe pixel events (e.g., `purchase`, `lead`, `pageview`).	Yes
`eid`	A unique event ID to deduplicate events. Use your internal transaction or event ID.	Yes
`ip`	The IP address of the user who converted. This is how Vibe matches the event to a household.	Yes
`ts`	The timestamp of when the conversion occurred, in milliseconds since epoch (Unix timestamp × 1000).	Yes

Optional parameters

Parameter	Description
`rev`	Revenue amount associated with the conversion (e.g., `49.99`).
`oid`	Order ID for purchase events.
`cur`	Currency code (e.g., `USD`). Defaults to USD if not provided.

Example request

GET https://tracker.vibe.co/s2s-conversion/events?aid=YOUR_PIXEL_ID&a=purchase&eid=txn_12345&ip=203.0.113.42&ts=1711540800000&rev=49.99&oid=order_789

A successful request returns a 200 OK response with a 1×1 transparent pixel.

Finding your Pixel ID

Log in to your Vibe account.
Go to Settings > Web Tracking.
Your Pixel ID is displayed on this page. It is the same ID used in your Vibe pixel JavaScript snippet.

If you don't see a Pixel ID, you need to create a pixel first by following the setup instructions in Web Tracking.

Best practices

Always include the end user's IP address — this is the primary matching key. Without it, Vibe cannot attribute the conversion to a household. Make sure you send the user's IP, not your server's IP.
Use unique event IDs — the eid parameter prevents duplicate conversions from being counted twice.
Send events in real time — for best attribution accuracy, send events as soon as they occur rather than batching them.
Use the same action names as your pixel — this ensures S2S conversions are grouped with pixel conversions in your reports.

Good to know

S2S events are used for attribution and reporting. They do not currently populate retargeting audiences.
Matching is based on IP address at the household level.
S2S tracking requires a Vibe Pixel to be set up first — the Pixel ID is used to identify your account.
S2S is different from CAPI (Conversion API, used for integration partners). S2S is designed for advertisers who want to send conversion data directly from their own servers.