In our previous update, SwiTra's Apple Ads campaign was still blocked while we waited for a product page review. That review eventually finished, but starting the campaign required one more fix and another app submission.
The product page passed review, but the campaign did not start
On August 9, the default Apple Ads product page from our previous update passed review. Even after that approval, however, the Apple Ads campaign still would not run.
We checked again for a separate cause. The Flutter app supported multiple languages internally, but those languages had not been registered as iOS localization resources in the Xcode project.
We added the iOS localization resources and submitted again
On August 12, we added the supported language settings and language-specific .lproj resources to the Xcode project. We also updated the app version from 1.1.1+33 to 1.1.2+34. The changes were merged into the main branch on August 13, and we submitted the updated app for review that same day. The new app version passed review on August 19.
- August 9: Default Apple Ads product page passed review
- August 12: Added iOS localization resources to the Xcode project
- August 13: Merged the changes into the main branch and submitted the updated app for review
- August 19: Updated app version passed review
- August 19: Apple Ads campaign started
It took another ten days from the first approval on August 9 to the actual campaign launch on August 19.
Starting with a $100 promotion
We also received $100 in promotional credit when the campaign started. We will use it to begin running Apple Ads and observe impressions, clicks, and installs.
There is not enough data yet to evaluate the campaign's performance. What has changed is that the experiment we could not start in July is now finally running. Starting the campaign is not the same as proving that it works. A future update will cover what happened after spending the $100 credit and what kind of traffic it produced.