CONNECTIONS / Singular
Singular postbacks, live on every ad platform.
Singular already joins your ad spend to attribution for ROAS reporting. Signals reads the same attributed postback and delivers it, server-side and ATT-aware, to Meta, Snap, and TikTok's app conversion APIs, keeping Singular's cost and revenue view untouched.
- ● singular :: postback received
- > Postback received event=install source=Google Ads
- > Postback received event=purchase revenue=58.00 USD
- hash sha256(idfa,email) att=authorized
- route meta · snap · tiktok
- ✓ 3 destinations synced · revenue matched
The signal Singular yields.
Every kind of signal that moves between Singular and the platforms, through one hashed, deduplicated route.
- App conversions
- Every install and re-engagement Singular attributes forwards to Meta, Snap, and TikTok's app conversion APIs the moment the postback fires, regardless of which network Singular credited.
Pick your platform. Every use case for it, in one place.
Every way Singular data moves, grouped by platform and ranked by how many use cases Singular supports.
Meta 1 
Snap 1 
TikTok 1 From authorization to delivered signal.
-
Point the postback
Singular's postback for install, re-engagement, and revenue events is set to Signals' endpoint, alongside the ad networks it already reports cost against.
-
Map to each app spec
Postback fields map to Meta, Snap, and TikTok's app conversion schema in the visual mapper, revenue values included, so what a platform sees matches what Singular reports.
-
Dedupe on event ID
Postback events dedupe against the platform SDK on shared event IDs, so a purchase Singular attributes and the SDK also logs reaches each platform once.
-
Deliver, ATT-aware
Server-side delivery to every mapped destination, iOS-aware of tracking consent, checked in the live debugger before campaigns rely on it.
Singular questions, answered.
Does adding Signals change what Singular reports for cost and ROAS?
No. Singular's cost aggregation and ROAS dashboards keep running on the attribution and spend data Singular already pulls in; Signals only reads the same attributed postback and forwards it to each ad platform's app conversions API. The revenue figure a platform sees and the one in a Singular report stay the same number.
Do we still need Singular if Signals delivers to the ad platforms?
Yes, if attribution and cost reconciliation across networks is why you run Singular. Signals does not attribute anything; it reads what Singular has already resolved and gets it to each ad platform server-side. Remove Singular and the attribution logic goes with it, since Signals only forwards what Singular hands it.
How does this handle Singular's SKAdNetwork conversion modeling on iOS?
SKAdNetwork-attributed conversions still arrive as a Singular postback carrying whatever Apple allows, a conversion value and campaign ID rather than a device identifier. Signals forwards those fields as they are, so a privacy-modeled install reaches Meta, Snap, or TikTok's app conversions API the same way a deterministic one does.
NEXT STEP
See your Singular data working in every ad platform.
Ready to enable a use case, or still mapping what Singular data could do? Our team helps you find the right place to start.
