Oh, welcome to the iOS tracking circus. It's like trying to follow a cat through a hedge maze - technically possible, but you'll lose the little bugger every time.
Yeah, Google Ads can track iOS downloads, but Apple's privacy changes have turned it into a game of hide and seek where the ads always lose. The core problem is that the click ID gets stripped somewhere between the ad click and the App Store. Google's left staring at a blank screen while your events happen in GA4 and App Store Connect. It's the digital equivalent of throwing a party and the guest list goes missing.
You've got the basics right - linking accounts, importing conversions. But even if everything's connected, the attribution pipeline is broken. iOS doesn't hand over the Google Click ID like Android does. So your first_open fires, your installs show up on Apple's side, but Google sees zero. The events exist, the ad just can't claim credit.
If you control the app, the Firebase SDK is your best friend for getting cleaner data. Server-to-server tracking via Apple's Attribution API is the gold standard, but it's not a weekend project. If you're just running ads for someone else's app... well, welcome to the club where we squint at click volume and CTR and pretend it's a conversion signal.
SKAdNetwork exists, but it's like getting a postcard from your holiday two months late - delayed, vague, and you're not sure if that blob in the photo was the Eiffel Tower or a lamppost.
Bottom line: your downloads are probably happening. Google just can't see them. Cross-reference App Store Connect with GA4 and your ad spend, take a deep breath, and accept that iOS tracking is a beautiful mess. We're all in the same leaky boat.