Posts

Post not yet marked as solved
0 Replies
239 Views
When Apple rolled out SKAdNetwork 2.0, we were able to see pingback messages sent from the device directly to our server. Observing those messages with a web proxy like Charles or ProxyMan was very helpful for testing and debugging. We could know the precise time the message was sent, for example, and we could look at the contents of the message to get e.g. the transaction ID, which helped us confirm receipt of and processing of the pingback message on the server. Starting with iOS 14.6, however, the pingback messages are not sent directly to the server, but are apparently sent through a proxy server instead, which makes it more difficult to demonstrate that the pingbacks are being sent from the device and received at the server. Are there any tools or techniques that you recommend for testing this aspect of SKAdNetwork attribution?
Posted Last updated
.
Post not yet marked as solved
0 Replies
324 Views
The Testing Ad Attributions with a Downloaded Profile page, from which we download the IA Pingback delay profile that reduces the wait time for an SKAdNetwork pingback, says: This testing profile expires two weeks after you install it on the device. To continue testing, download the latest profile and reinstall it. In my experience, this seems not to be the case at all. As of this moment, the profile itself was last updated on June 8, 2021. I periodically re-install it just to be safe, but it seems to continue to work longer than 2 weeks from the installation date. Are the docs correct? Do I need to keep refreshing my test devices with the same profile? If the profile really does expire two weeks after installation, can we get one that lasts longer? Having to keep updating the profile on multiple devices is a hassle, and it introduces unnecessary uncertainty into a process that already has a lot of moving parts.
Posted Last updated
.