SKAdNetwork’s bugs are posing challenges for advertisers, as the adoption of SKAdNetworks increases, leading to various issues or misconfiguration.
A SKAdnetwork bug can be an anomaly in your data, as seen in a real case from August 2023 where a bulk of coarse and fine conversion values appeared as 0 or ‘none’. It can also be an abrupt decline in incoming SKAdNetwork postback.
Not SKAdNetwork bugs
Some of the unexpected behavior in SKAdNetwork doesn’t always indicate bugs; at times, it reflects the intended functionality of SKAdNetwork. Below is a list of such non-buggy behaviors:
- Unavailable values due to crowd anonymity in SKAdNetwork 4 and above
- Empty Conversion Values
- Two digits in the Source Identifier
- Empty Source App ID
Backlog of existing bugs and fixes
- [Fixed] On August 3rd, 2023, An issue where some conversion values for SKAdNetwork 4 postbacks were overwritten with the value 0 was resolved in iOS 16.6.
SKAdNetwork bugs checklist
- Verify Apple’s System Status Page. It’s always a good idea to check there first if something is wrong with the SKAdNetwork.
- If the issue persists with a single ad network, examine the network’s status page (e.g., Unity Status page; note the absence of a dedicated SKAdNetwork section; review ‘Growth’ & ‘User Acquisition’ segments).
- Contact Ad Network support, detailing the problem as they may be unaware of it.
- Check your MMPs status page (e.g., AppsFlyer Status Page; with a dedicated SKadNetwork section).
- Investigate internally with your engineering team, if the issue arose post an app update.
- Review the integration of the MMP SDK.
Use the form below to file your SKAdNetworks bugs. We are happy to help.
This form is currently undergoing maintenance. Please try again later.