Liftoff SKAdNetwork attribution help

Seeing 'weird data' is often the first sign that SKAdNetwork is doing its job... just maybe not your job quite right yet. I definitely understand the frustration here; SKAdNetwork setup, especially with post-install events, can be a bit of a labyrinth. I've personally debugged similar Liftoff integration challenges more times than I care to admit.

[LiftoffSDK] WARNING: SKAdNetwork post-install event registration failed. Check SDK integration.

This warning, and your suspicion about updateConversionValue, points to a few common areas. The updateConversionValue function is indeed critical, but the issue often stems from its implementation timing, frequency, or the values being passed. Here’s a checklist for debugging your Liftoff SKAdNetwork setup:

• SDK Initialization & Version: Ensure your Liftoff SDK is correctly initialized early in the app lifecycle and that you're on a recent, stable version. Outdated SDKs can cause unexpected behavior.
• updateConversionValue Logic:
• Timing: It should be called only after registerAppForAdNetworkAttribution() has been invoked.
• Frequency: You can call it multiple times, but only increasing values will be registered. If you try to update with a lower or equal value, it will be ignored until the next attribution window.
• Value Range: Ensure your conversion value mapping is correctly implemented, and you're passing values between 0 and 63. Liftoff will have specific recommendations on how to map your in-app events to these 6-bit values.
• Privacy Manifest (iOS 17+): If you’re targeting iOS 17 or later, ensure your app's Privacy Manifest (PrivacyInfo.xcprivacy) correctly declares the required reasons for API usage related to SKAdNetwork, especially if Liftoff's SDK uses any of those APIs. Missing declarations can lead to runtime issues.
• Liftoff Dashboard Configuration: Double-check your event mapping and conversion value schema within the Liftoff dashboard. The values you're sending from the app must align with what Liftoff expects for post-install event attribution.
• Server Postbacks: While less common for this specific warning, ensure there isn't any server-side logic inadvertently interfering with the SDK's ability to register events, especially if you're using a hybrid approach or a server-to-server integration for other attribution.

Could you clarify if you're seeing any specific errors or logs *before* this warning, or if the updateConversionValue calls themselves are returning any non-success responses?

Oh nice! Thanks Fatima Mansour, I was seriously starting to think SKAdNetwork was just a big maze for fun, your checklist is exactly what I needed.