Hello 
We’re having Mopub integrated in our apps (IOS/AN) through which we are mediating Flurry.
Now GDPR comes upon us we’ve started to work (with a ‘bit’ of delay) on this topic.
Flurry, in principle is a ‘supported mediated network’ for Mopub, namely Mopub in principle passes the consent it collects (via own consent screen) to Flurry.
Flurry, on its own via its own SDK, makes available methods for us to pass directly the consent to them (ads (https://developer.yahoo.com/flurry/docs/publisher/ios/gdpr/, https://developer.yahoo.com/flurry/docs/publisher/android/gdpr/ ).
As we would prefer to have directly GDPR relation with Flurry (i.e. send ourselves the consent to them) and at the same time Mopub passing themselves the consent to Flurry, I see some scenarios where a conflict/problematic situation would appear. I mention that besides Mopub’s consent dialogue, we’re having a separate consent dialogue ourselves which we store and pass across the entire exposure stack.
Can you, Mopub support team, please let me know your thoughts on the topic? Is it possible to disable from Mopub adapter (for Flurry) the passing of consent to Flurry and ourselves handle directly the consent-passing? Or for Mopub-supported-networks we’re supposed to fully leave the consent collection/passing in responsibility of Mopub?
