For most deployments we are going to use the same workspace for testing and content delivery so we need to have dedicated triggers (and groups) for actual users (not testers/facilitators) so we can identify their data.
A wrapper for the campaign was created so that messages are only pushed to users in the dedicated groups
https://docs.google.com/spreadsheets/d/1yUzKndclwMurTwBgDTzA5ha7xLjj214oZy10KYtjW4U/edit#gid=540754912
This needs to become a template where group names can be specified (deployment specific)
Similarly the flow for verifying the joining triggers and add to the groups need to be transformed into a template where it's possible to specify the joining triggers and the corresponding group names
https://docs.google.com/spreadsheets/d/1yUzKndclwMurTwBgDTzA5ha7xLjj214oZy10KYtjW4U/edit#gid=1932032165
For most deployments we are going to use the same workspace for testing and content delivery so we need to have dedicated triggers (and groups) for actual users (not testers/facilitators) so we can identify their data. A wrapper for the campaign was created so that messages are only pushed to users in the dedicated groups https://docs.google.com/spreadsheets/d/1yUzKndclwMurTwBgDTzA5ha7xLjj214oZy10KYtjW4U/edit#gid=540754912 This needs to become a template where group names can be specified (deployment specific) Similarly the flow for verifying the joining triggers and add to the groups need to be transformed into a template where it's possible to specify the joining triggers and the corresponding group names https://docs.google.com/spreadsheets/d/1yUzKndclwMurTwBgDTzA5ha7xLjj214oZy10KYtjW4U/edit#gid=1932032165
and same holds for hook_message_wrapper