Skip to main content
Upstack Data

Vibe integration: identity-resolved conversions, sent server-side

Send resolved conversions to Vibe so streaming TV campaigns are attributed to the orders they drove.

Role
Destination
Category
Ad platforms
Pre-built connectors
12 sources
Plans
All plans

What Upstack sends

Every conversion reaches Vibe with the identifiers it matches on. Captured on the server, resolved to a person, then sent.

In: from Shopify1 of 12 sources
  • order_idShopify order and checkout token
  • email / phonecustomer contact from checkout
  • customer_idShopify customer record, if they have one
  • line_itemsproducts, variants and quantities
  • total / subtotal / discountorder economics

Storefront events from the Upstack Pixel, orders directly from Shopify.

Upstack DataResolved before it is sent
  • IdentityMatched against a 750M+ device graph, so a phone browse and a desktop checkout resolve to one customer.
  • customer_typeNew or returning, resolved before send.
  • DeduplicationBrowser and server copies of the same purchase collapse on event ID, so nothing is counted twice.
  • Bot and fraud filteringAutomated traffic never reaches the model, because what you keep out of the training set matters as much as what goes in.
Out: to VibeOn every event
  • hashed email / phonematch a purchase to an exposed household
  • ip / user_agenthousehold matching for a no-click channel
  • order timestampplace the order inside the campaign window
  • value / currencymeasure streaming on revenue
  • event_iddedupe against site-side reporting

Streaming TV conversions, server-side.

About Vibe

Upstack forwards resolved orders server-side with their full value, so campaigns are judged against actual revenue.

For an advertiser iterating weekly, the difference between complete and partial conversion data is the difference between learning and guessing.

What Vibe is

Vibe sells streaming television advertising to small and mid-sized advertisers, with self-serve buying and fast campaign turnaround.

Fast iteration only helps if the results arriving back are accurate.

How Vibe works

Vibe attributes conversions by matching exposed households to site activity within an attribution window. Like every no-click channel, it depends entirely on the conversion data the advertiser sends it.

What you can do with it

Three jobs this connector does inside Vibe.

01

Send complete conversions

Conversions reach Vibe through its server-side API with restored click IDs and hashed identifiers attached, so more of what you send is matched on arrival, and the conversions you never saw stop being invisible.

02

Optimize on the customer you want

Map any order attribute to the conversion Vibe receives (profit rather than revenue, new customers rather than repeat buyers, high-value orders rather than every checkout), so the platform learns from the buyers worth acquiring.

03

Accurate results, fast enough to act on

Resolved orders arrive server-side on the same cadence as the campaign, so a weekly iteration cycle runs on complete data rather than a partial view.

Pre-built connectors

12 sources connect to Vibe. Whichever of these you run, Vibe is one switch away.

See all connectors

Documentation

Set-up reference.

Set-up, event schema and field mapping for Vibe as a destination.

FAQ

Vibe integration questions.

What does Upstack send to Vibe?

Send resolved conversions to Vibe so streaming TV campaigns are attributed to the orders they drove.

How do I check that events are reaching Vibe?

Open Vibe › Campaigns › Conversions. Matched conversions report the campaign window they were attributed inside.

Which plans include the Vibe integration?

All plans. Upstack has three plans that scale with your order volume, and the same integrations are on every plan.

Which sources can send events to Vibe?

12 sources: Shopify, WooCommerce, BigCommerce, Checkout Champ, Recharge, Custom stack, Funnelish, Lasso Commerce, Phoenix Technologies, Skio, Loop Subscriptions and Stripe. Each one has its own pre-built connector.

Will Upstack slow down my store?

Upstack’s own pixel loads asynchronously and fails silently, so it doesn’t hold up your pages. What each destination adds depends on its Tracking Method. The default, Browser + Server, loads that platform’s own tag on your store, in place of the copy you would otherwise install yourself, and also sends the same events from Upstack’s servers. Choose Server for any destination that offers it and its tag never loads, while its events still arrive from Upstack’s servers.

Similar integrations

Other Ad platforms integrations.

See all integrations

Get Vibe tracking right.

A 15-minute walkthrough tailored to your stack and channels.