-
Notifications
You must be signed in to change notification settings - Fork 201
Description
Hi we are ensuring our app & data pipeline adheres to GDPR. That means that we have implemented a CMP to collect consent, then we add the consent object to each segment event, no problem!
We've ran into an issue with Appsflyer, because it doesn't send it's data via Segment in the cloud, it sends data directly from the device with it's own SDK, and then tells Segment it happened, which fires an event.
We'd like appsFlyer.startSdk(); to be called after we have shown the CMP and obtained the users consent, so we can set the consent (with appsFlyer.setConsentData()). The init: appsFlyer.initSdk can still be called when we add the plugin.
We are doing this:
const segmentClient = createClient({...etc})
segmentClient.add({ plugin: new AppsflyerPlugin() });
Now, as it stands, the AppsflyerPlugin inits and starts Appsflyer. What is the best way for me to keep the init, but delay the start of Appsflyer? I can't add a consent param to the constructor, because I don't know the consent yet.
Do I just edit the code for the plugin to add this consent param, and if it's not given, only init, then remove + re-add the plugin later when consent is given? This is the main thing I can think of atm.
Hope this makes sense. Thanks.