Vibe Conversions Destination
Beta
This feature is in active development and may change before general availability.
Vibe is a streaming TV advertising platform that lets brands run performance-based CTV campaigns and measure them like digital campaigns. The Vibe Conversions destination sends your conversion events (like purchases, sign-ups, and page views) to Vibe's server-to-server conversion API, where Vibe matches each event to a household by IP address and attributes it to your Vibe campaigns.
Vibe maintains this destination. For any issues with the destination, contact the Vibe support team.
Before connecting the Vibe Conversions destination, you need a Vibe Pixel set up in your Vibe account. To find your Pixel ID:
- Log in to your Vibe account.
- Go to Settings > Web Tracking.
- Copy your Pixel ID.
- From your workspace's destination catalog page, search for "Vibe Conversions".
- Select Vibe Conversions and click Add destination.
- Select an existing source to connect to Vibe Conversions.
- Enter your Vibe Pixel ID in the destination settings and save your changes.
- In the Mappings tab, review the prebuilt mappings for
Order Completed,Page Viewed, andSigned Up, or create a new Track Conversion mapping for other events. - Enable the destination.
The Vibe pixel ID associated with the advertiser. Found in the Vibe dashboard.
Vibe Tracking Event has the following presets
| Preset Name | Trigger | Default Action |
|---|---|---|
| Order Completed | Event event = "Order Completed" | Track Conversion |
| Page Viewed | Event type = "page" | Track Conversion |
| Signed Up | Event event = "Signed Up" | Track Conversion |
Build your own Mappings. Combine supported triggers with the following Vibe Tracking Event-supported actions:
Mapping limits per destination
Individual destination instances support a maximum of 5 mappings.
Send a conversion event to Vibe.
Track Conversion is a Cloud action. The default Trigger is type = "track" or type = "page"
The action/event type that was performed.
Unique event ID. Must be unique for each event. UUID format is recommended. Defaults to the Segment messageId.
Timestamp of the event, in ISO 8601 format or UNIX milliseconds. Must be within the last 7 days. Sent to Vibe as UNIX milliseconds.
IP address of the user who performed the action. Must be IPv4.
Optional
Additional event data to send with the event.
Optional
Google Analytics ID for cross-platform attribution.
Optional
User Agent string.
Optional
The URL of the page where the action occurred.
Vibe uses the IP address to match each conversion to a household, so IP Address is required and must be a valid IPv4 address. By default, it maps to context.ip. Browser and mobile libraries populate this automatically, but server-side libraries (like Node.js or Python) don't. When you send events from a server, set context.ip to the end user's IPv4 address, or map IP Address to another field that contains it.
Vibe only accepts conversion events with a timestamp from the last 7 days. Events older than that, like replayed or backfilled historical data, are rejected.
Event Type must be one of call, install, lead, page_view, purchase, or signup. The prebuilt mappings set this for you. When you create a new Track Conversion mapping, choose the value that best matches the event you're sending.
Map the purchase amount to Price (USD) inside Event Data. By default, this maps to properties.price_usd. If your events store revenue in a different property (like properties.revenue), update the mapping to point to that property.
You can send computed traits and audiences generated using Engage to this destination as a user property. To learn more about Engage, schedule a demo.
For user-property destinations, an identify call is sent to the destination for each user being added and removed. The property name is the snake_cased version of the audience name, with a true/false value to indicate membership. For example, when a user first completes an order in the last 30 days, Engage sends an Identify call with the property order_completed_last_30days: true. When the user no longer satisfies this condition (for example, it's been more than 30 days since their last order), Engage sets that value to false.
When you first create an audience, Engage sends an Identify call for every user in that audience. Later audience syncs only send updates for users whose membership has changed since the last sync.