Skip to main content
Conversion Postbacks are currently in alpha. Behavior and supported networks may change between releases.
Who is this for? Marketers running paid acquisition on TikTok Ads, Meta Ads, Google Ads, or Reddit Ads who want to feed conversion data back to those platforms to improve campaign optimisation.
When a player clicks your ad, installs the game, and completes an action you’ve defined as a conversion, Immutable Audience captures the whole journey. Conversion Postbacks close the loop by automatically notifying the ad network that the click led to a real outcome. What counts as a conversion is set by your Conversion Goals. A postback fires whenever an attributed event matches an active Goal, so you control exactly which actions are forwarded. Without postbacks, ad networks are flying blind. Their optimisation algorithms can see your spend but not your results. With postbacks enabled, every attributed conversion you send back directly improves your campaign targeting.

​
How It Works

1

Player clicks your ad

Immutable’s Tracking Pixel captures the click ID from your ad campaign on your marketing site.
2

Player installs and acts

Your game sends events via the Unity SDK, Web SDK, or REST API as the player plays.
3

Immutable attributes the event and checks your Goals

The Audience attribution engine matches the in-game event to the original ad click, then checks it against your active Conversion Goals. If it matches a Goal, the conversion is recorded.
4

Postback fires automatically

For each matched Goal, Immutable sends a server-to-server callback to your connected ad networks with the conversion data. No code changes needed after initial setup.

​
Supported Networks

TikTok Ads

TikTok Events API, connected via OAuth in Audience Hub

Meta Ads

Meta Conversions API, connected via OAuth in Audience Hub (sandbox mode)

Google Ads

Google Ads API offline conversion import, connected via OAuth in Audience Hub (testing mode)

Reddit Ads

Reddit Conversions API v3, configured with a paste-in token in Audience Hub

​
What You Need

Before configuring postbacks for a game:
  • The Immutable Tracking Pixel or Web SDK is installed on your marketing site (captures click IDs from ad platforms)
  • The Unity SDK, Web SDK, or REST API is sending the events your Conversion Goals are built on (such as purchase)
  • At least one Conversion Goal is active for the game. A postback fires when an attributed event matches an active Goal.
  • You have admin access to the game in Audience Hub

​
Event Mapping

A postback carries the event from the Conversion Goal that matched. Immutable maps each Goal event to the closest standard event on each network:
Goal eventTikTok AdsMeta AdsGoogle AdsReddit Ads
purchasePurchasePurchaseConversion Action (mapped per Goal)Purchase
wishlist_addAddToWishlistAddToWishlistConversion Action (mapped per Goal)AddToWishlist
wishlist_removewishlist_removewishlist_removeConversion Action (mapped per Goal)Custom named wishlist_remove
email_acquiredCompleteRegistrationCompleteRegistrationConversion Action (mapped per Goal)SignUp
For purchase conversions, Immutable forwards value and currency when both are present, so ad networks can optimise for revenue (ROAS), not just conversion count. This applies to all four networks. Google Ads requires you to map each active Goal to a Conversion Action you’ve created in your Google Ads account. See the Google Ads setup guide for details. To choose which events count as conversions for your game, set up your Conversion Goals.

​
Monitoring Postback Delivery

The Delivery logs section on each ad network’s integration page (Settings then Integrations then [Network]) shows every postback dispatch attempt for that game. Filter by time range (last hour, 24 hours, 7 days, or 30 days) and status. Each log entry shows:
ColumnDescription
TimeWhen the postback was sent (hover for the exact timestamp)
EventThe Conversion Goal event that triggered it, such as purchase or wishlist_add
StatusDelivery outcome (see below)
HTTPThe HTTP status code returned by the ad network
LatencyRound-trip time in milliseconds
AttemptWhich retry attempt this entry represents

Success

The network accepted the postback

Failed

The network rejected the payload, usually a credential or configuration issue. Not retried.

Retried

A transient network error. Immutable automatically retried the delivery.

​
Health status

Each postback config in the list shows a health indicator alongside its enabled/disabled badge:
IndicatorMeaning
No indicatorPostbacks are delivering normally
”Credential failures detected” (warning icon)Recent deliveries are failing with auth errors. Credentials may have been revoked or expired.
”No recent activity” (clock icon)No delivery history yet. Normal for a newly configured postback.

​
FAQ

No. Postbacks rely on click IDs captured by the Tracking Pixel or Web SDK on your marketing site when a player arrives from an ad. Without a click ID, Immutable cannot tie the in-game conversion back to the original ad click, and there is nothing to forward to the ad network.Reddit Ads also accepts a hashed email address as a fallback identifier when no click ID is present. See the Reddit Ads setup guide for details.
No. Only conversions attributed to a paid ad click on a configured network are forwarded. Organic players, players from untracked sources, and players whose click happened outside the supported networks do not generate postbacks.
Yes. The REST API accepts the same events. Events from any source (Unity SDK, Web SDK, REST API) are eligible to match a Conversion Goal and trigger postbacks once attributed.
Events marked test: true (from SDK or Pixel testMode) are handled differently per network. TikTok and Reddit route them to each platform’s test environment if a test code or test ID is configured on the postback. Meta uses test_event_code in the same way. Normal production events are never affected by test codes, even when one is set.
Erasure removes the user’s data from Immutable’s systems (see Deleting User Data). Postbacks already delivered to ad networks are not retracted by Immutable. Once the network has received the conversion signal, it operates under that network’s data retention policy. To request erasure from the ad network itself, contact the network directly. New postbacks will not be sent for the erased user.
Check the following:
  • Is the postback config enabled?
  • Is there at least one active Conversion Goal matching the events you’re sending? Without a matching Goal, nothing is forwarded.
  • Is the Immutable Tracking Pixel installed and capturing click IDs on the pages you’re running ads against? Without a click ID, Immutable can’t attribute the conversion to a paid ad click.
  • Is the Unity SDK, Web SDK, or REST API sending the expected events?
The ad network rejected the payload. Check the HTTP status code shown in the log entry:
  • 401 / 403: your credentials have expired or been revoked. For OAuth networks (TikTok, Meta, Google), reconnect the integration. For Reddit, rotate your Conversion Access Token.
  • 400: the event payload was rejected by the network’s validation. Contact your Immutable account manager with the attribution event ID from the log.
Additional networks are not yet available for self-service configuration. Contact your Immutable account manager or reach out via the support portal to discuss your needs.

​
Next Steps

Conversion Goals

Define which player actions count as a conversion and control what triggers postbacks

Attribution

How tracking data powers player attribution and Hub reports

Data Dictionary

Full reference of event schemas and consent levels

Tracking Pixel

Make sure click IDs are being captured from your ad platforms

Web SDK

Typed SDK for web games, marketing sites, and SPAs

Unity SDK

In-game tracking for Unity desktop builds

REST API

Send events from your backend or game server