Skip to main content
Use this page when a user or Remote UI request is not attributed as expected.

​
Check the app integration

  • The app sends attribution after the attribution provider returns data.
  • The provider name matches the SDK-supported value.
  • The identifier is stable for the provider.
  • The same PNLight user ID is used for SDK actions around install, attribution, and Remote UI.
  • If PNLight initialized before ATT authorization, the app calls updateIdfa() after the prompt completes.

​
Check dashboard settings

Open Settings and review:
  • Attribution priority order.
  • Enabled attribution sources.
  • Wait window for preferred attribution.

​
Attribution is delayed

Attribution can be delayed when the app waits for the preferred provider before falling back. If early flows depend on attribution, review the wait window with your product and marketing teams. On the first app launch, wait 4-5 seconds after AppsFlyer initialization before requesting Remote UI when attribution is required. The SDK also waits for attribution internally when attributionRequired is true.
For launch testing, use one test device and one attribution source at a time. This makes it easier to confirm which provider supplied the final attribution.