Disable destinations dynamically

[danisandoval]

Hi team,

We'd like to request a feature that allows us to disable a destination SDK dynamically based on configurable criteria such as:

• Country
• Percentage of users
• Other conditions that allow for partial disablement (rather than 100%)

Currently, we don't see a way to achieve this within the platform. One of our main use cases is handling SDK crashes in specific regions. For example, we've encountered a scenario where an SDK is causing crashes in a particular country. Instead of disabling it globally, we'd like to selectively turn it off for affected users to test and mitigate the issue while maintaining normal operation for the rest.

Would it be possible to add support for this functionality? Please let us know if there are any workarounds we might have missed or if this feature is on the roadmap.

Thanks!

[samdozor]

Hi @danisandoval thank you for the thoughtful request. There is some support here and a few less-than-ideal workarounds. We'll take this internally to see if there's anything else I didn't think of.

1. User sampling
   You can sample the % of MPIDs by setting a percentage on the connection settings. This is based on a modulo of the MPID:

2. Consent
   You could use consent as a mechanism for this. The SDKs will programmatically enable/disable kits based on consent - which in this case would not be actual user consent, but you could define a consent such as "production_kits" and only set it to true for a % of users or based on whatever business logic you please.

3. Sideloaded kits

This would be likely too high effort - but the SDK supports "side loaded" kits, where you decide which to enable based on client side and whatever business logic you need: https://docs.mparticle.com/developers/client-sdks/ios/kits/#including-the-sideloaded-kit-and-adding-filters

4. The SDKs being open source, you could hook into the method that the SDK uses to initialize a kit, and return false based on your business logic. See the method here: https://github.com/mParticle/mparticle-apple-sdk/blob/main/mParticle-Apple-SDK/Kits/MPKitContainer.mm#L494

I imagine purely server side is desired - but if we were to add an callback API that you set a callback could return true/false from (similar to option 4 but just exposed via the public interface) - would that accomplish your use-case?

[danisandoval]

Hi @samdozor, thanks for your answer.
We'll analyse the options provided and get back to you as soon as possible.

[claudiomadureira]

Hi, I'm one of the engineers responsible for this and I have some statements/questions:

1. User Sampling: It wouldn't work for us once we needed to control the audience and know which userIds are enabled/disabled. Is there a way for us to control it?
2. Consent: I have some questions.
   I. How should we pass the consent for disabling Appboy Kit for example?
   II. Would this option prevent the Appboy SDK (Braze) to be initialised?

Hoping to hear from you soon!