Trackers can be “disguised” and embedded into first party domains, invisible to the user, which allows them to escape blocking
I will see if there is anything the developers have to say, but from my understanding, there is no way for the iodé blocker app to do anything to protect against these trackers, if they are truly only “seen” by your phone as “approved web addresses”.
Effectively in that case, the traffic the iodé blocker “sees” is again only to the approved address, but possibly at the app’s cloud / server instance they mangle / inject trackers and then deliver back to you via their “approved first party domain” again.
Now if these trackers are embedded at a subdomain level or have further identifiers in the FQDN, then those could be identified (and blocked, likely by default) by the iodé blocker. But if it truly delivered to your device using the same FQDN as valid traffic then there is no way to differentiate it (and thus block it).