multiple subscription group update
Adding subscription group to your email program is a great way to retain customers from on overall exit. Unfortunately adding the program starts all existing customer as unsubscribe. Luckily there is...
Forum Discussion
Hi Ben,
Yes I would like to do a bulk update to everyone. I am using a webhook which successfully updates all subscribed/opt-in customers to "turn-on" for a specific subscription group in a sandbox test environment. The test environment had 1.2M contact which took nearly 4 hours to turn on 1 subscription group while our true list consist of 42M plus customers with 6 subscription group.
The rate limit for this is 5k per minute which will lead us over 40 days (at least) so this brings up a few hiccups. Updating 1 subscription group per run will take us at least 240 days to back-fill 6 subscription group for 42M plus and that runs into potential issue with new customer switch since they will run simultaneously and be part of the 5k threshold.
For that reason, I am hoping to switch all 6 subscription group to all subscribed/opt-in customers in one run then let the new subscriber webhook kick in after the run rather than reduce backfill and new customer switch. I tried testing multiple subscriber group switch which didn't work sadly. Hoping someone had better luck.
Hey ravn, great to see you posting here also. This has been on my mind since we last spoke. I think submitting a Braze ticket for this one could be worth it, since we're blocked by Braze's rate-limits. Please let me know if you end up going this route!
Hi AllanHeo,
I actually reached out to our account manager and engineer. A great alternative they suggested was to build a canvas and use the user update module with the advance json editor to do it all in one go. Attaching user update description to read if you're curious.
I was able to update multiple subscription group all at once. There is a note that the module will consume data point but from testing with Braze it didn't seem to consume any. Based on the documentation, subscription group is a non-billable asset therefore it shouldn't consume your allotment. If anyone wants to try and use it, suggest confirming with your account manager prior (just in case).
Quick note for your tutorial. If you're using webhooks and directing to the /subscription/status/set then the 5000 per minute request must take into consideration the total number of webhook passing to that endpoint. If you set 5000 per minute for each webhook, you will run into skips. The maximum documented is for all passing communication within a minute. For example, if you have 3 subscription group passing to that one particular endpoint then you will need to set each to 1000 or a combination of it. As long as it does not exceed 5000 because on the chance that they all fire (potentially at once), they will all get through and update profile successfully.
