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

Forward resolved purchase events to Tapjoy so rewarded placements optimize toward buyers rather than toward engagement.

Request a demo Start free trial

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

What Upstack sends

Every conversion reaches Tapjoy 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.

Resolved 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 TapjoyOn every event

hashed email / phonematch the buyer to the rewarded user
idfa / gaidthe mobile advertising identifier, where consented
event_iddedupe against SDK-reported events
value / currencyoptimize on revenue, not engagement
app_idwhich app the exposure happened in

Rewarded and in-app conversions.

See the set-up reference See all 12 sources How resolution works

About Tapjoy

Upstack resolves the purchase against the device graph and forwards it server-side with its full value, so Tapjoy optimizes toward people who bought rather than people who engaged.

On a rewarded surface those two populations are unusually different.

What Tapjoy is

Tapjoy runs rewarded advertising inside mobile apps, where a user opts in to engage with an ad in exchange for in-app currency.

Rewarded traffic engages readily and converts selectively, so measuring engagement rather than revenue is actively misleading.

How Tapjoy works

Tapjoy optimizes against events reported through its SDK, which sees in-app actions well and web purchases not at all. The handoff from a rewarded placement to a web checkout crosses a boundary its instrumentation does not span.

What you can do with it

Three jobs this connector does inside Tapjoy.

Send complete conversions

Conversions reach Tapjoy 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.

Optimize on the customer you want

Map any order attribute to the conversion Tapjoy 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.

Buyers, not engagers

Purchase events are forwarded with real order value, so bidding separates users who convert from the much larger group who simply engage.

Pre-built connectors

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

See all connectors

Documentation

Set-up reference.

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

FAQ

Tapjoy integration questions.

What does Upstack send to Tapjoy?

Forward resolved purchase events to Tapjoy so rewarded placements optimize toward buyers rather than toward engagement.

How do I check that events are reaching Tapjoy?

Open Tapjoy › Reporting › Events. Purchase events appear with their value attached, separately from rewarded engagement.

Which plans include the Tapjoy 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 Tapjoy?

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 Tapjoy tracking right.

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

Request a demo Start free trial