From a685b9114970aa848aae35a1ee6770f0d3f5ec83 Mon Sep 17 00:00:00 2001 From: Jonny Hatch Date: Wed, 7 Feb 2024 16:56:08 -0700 Subject: [PATCH] Callout required permissions for mParticle integration When debugging a customer integration setup in mParticle, we discovered that Update profile permissions were inadequate, and that Create & Update profile permissions are preferred/default for integrations. https://docs.mparticle.com/guides/personalization/profiles/#input-protections --- .../Integrations & Events/third-party-integrations/mparticle.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs_source/Integrations & Events/third-party-integrations/mparticle.md b/docs_source/Integrations & Events/third-party-integrations/mparticle.md index 9c212880..5083bc30 100644 --- a/docs_source/Integrations & Events/third-party-integrations/mparticle.md +++ b/docs_source/Integrations & Events/third-party-integrations/mparticle.md @@ -264,6 +264,8 @@ mParticle also allows you to log a user in after starting the SDK and log a user In mParticle, add the RevenueCat feed input and create two feeds: one for the Android platform and one for the iOS platform. Copy each feed's Server to Server Key and Server to Server Secret for setup on RevenueCat. Refer to [mParticle's documentation](https://docs.mparticle.com/guides/feeds/) to learn more about feeds. +> ❗️ RevenueCat requires [Create & Update Profile](https://docs.mparticle.com/guides/personalization/profiles/#input-protections) permissions in order to send purchase & subscription lifecycle events into mParticle + ![](https://files.readme.io/adc36bb-2020-06-17_22.04.49_app.mparticle.com_a4031d73e6bc.png "2020-06-17 22.04.49 app.mparticle.com a4031d73e6bc.png") ![](https://files.readme.io/595280f-mParticle.png "mParticle.png")