In ScaleGrowth, the order in which you modify User Group memberships via the API can significantly impact the activation of Email Automations and Workflow Automations. This article explains the importance of the sequence of operations for user group changes and how it affects the triggering of these automations.
Example Scenario: Impact on Automations
Let's consider a practical example to illustrate the importance of the order of User Group operations:
- Situation: You have a customer who is currently a member of the User Groups "
Customer" and "Pro". - Objective: You want to upgrade this customer to the "
Plus" User Group while removing them from the "Pro" User Group.
API Request Options:
Option 1: "-Pro,+Plus" – This sequence is akin to the user manually cancelling their "Pro" membership and then signing up for "Plus."
Option 2: "+Plus,-Pro" – This sequence mirrors the user first signing up for "Plus" and then cancelling their "Pro" membership.
Impact on Automations:
- Using Option 1 "
-Pro,+Plus": This order will trigger certain automations. For example, if you have set up an Email or Workflow Automation that activates when a user is added to the "Plus" group but excludes those in the "Pro" group, this sequence will effectively initiate the automation. It's because at the time of adding to "Plus," the user is no longer in "Pro."
- Using Option 2 "
+Plus,-Pro": This sequence will not trigger the same automation. Here, the user is added to "Plus" while still being a member of "Pro", thus not meeting the criteria for the automation set to trigger only for users exclusively in "Plus."
The design of the ScaleGrowth API's User Group management feature allows for precise control over user group transitions and their impact on related automations. Understanding and strategically planning the order of User Group changes is crucial in leveraging the full potential of ScaleGrowth's Automation engine, especially in scenarios involving complex customer engagement, support, or community management operations.
