Internal Groups are a great way to build and organize internal or third-party test groups. They provide insight into your SDK or API logs, and are useful when testing your SDK integration. You can create an unlimited number of custom Internal Groups with up to 1,000 members.
You need the Access Dev Console permissions for your workspace to create and manage Internal Groups.
In addition to this article, we also recommend checking out our Quality Assurance and Debugging Tools Braze Learning course, which covers how to use internal groups to conduct your own troubleshooting and debugging.
Creating a group
To create an Internal Group, perform the following steps:
- Go to Settings > Internal Groups.
If you are using the older navigation, you can find this page under Settings > Developer Console > Internal Groups.
- Click Create Internal Group.
- Give your group a meaningful name.
- Choose one or more group types, as listed in the following chart.
|Group Type||Use Case|
|User Event Group||Used for verifying events or logs from your test device.|
|Content Test Group||A similar concept to Test Lists. Can be used across push, email, and in-app messages to send a rendered copy of the message.|
|Seed Group||Automatically sends a copy of the email to everyone the Seed Group upon send.|
Adding test users
After you create your Internal Group, you can add test users as members of that group. From your Internal Group’s management page, click Add Test User and either add them in bulk as identified users or as anonymous users.
|Identified Users||Search for the user by their external user ID or email address.|
|Anonymous Users||Search by IP address. Then, provide a name for each test user that is added. This is the name that all event logs will be associated with on the Event User Log page.|
|Bulk Add Users||Copy and paste a list of email addresses or external IDs into the provided section. You can only add users that are already known in the dashboard. For more information, refer to User Import.|
Content test groups
Similar to sending a preview test of a message, the Content Test group saves you time and allows you to launch tests to a pre-defined list of Braze users simultaneously. This functionality is available for push, in-app message, SMS, email, and Content Cards within Braze.
SMS test messages can only be sent to valid phone numbers in the database.
You can select individual Braze users or as many Internal Groups to send the message to as you want. If your message includes any Liquid or other dynamic personalization, Braze will use the attributes available for each individual user to personalize the message contents. For users who have no attributes, Braze will use the default value set.
Additionally, if you preview the message as a random user, custom user, or existing user, you can send that previewed version instead. Clearing the checkbox allows you to send based on each users’ attributes versus the previewed version.
Lastly, if you use an IP pool to send out email, you can select which IP pool you would like the email to be sent from by selecting the pool from the dropdown available.
Only groups that are tagged as Content Test Groups will be available on the preview section of a message.
Seed Groups are only meant for the email channel and allow you to send a copy of each email variant message to members of that group. Seed Groups are not available for API campaigns, although you can include Seed Groups via an API-triggered entry in campaign. This feature is typically used with partners such as Return Path or 250OK to measure deliverability metrics. It can be used to keep a record of the email content for historical and archival purposes.
Once you have created an Internal Group and tagged it to be used as a Seed Group, you can select it from the Target Users step of the campaign composer, or on the Send Settings step in a Canvas. Seed emails will have the identifier
[SEED], appended to the start of the email subject line. Note that Seed emails sent don’t increment sends in dashboard analytics, and they don’t update a user profile’s Campaign Received list.
If your Seed Group members report not seeing the message in their inbox, ensure that they are listed in the Internal Group, verify that your subject lines are different and that Gmail has not bundled the emails together, or have them check their SPAM folders.
Seed Groups can be edited from the Targeting page when composing an email campaign.
Seed Groups send to each email variant once and are delivered the first time your user receives that particular variant. For scheduled messages this typically is the first time the campaign launches. For action-based or API-triggered campaigns, this will be the time the first user is sent a message.
If your campaign is multivariate and your variant has a 0% send percentage, it will not be sent to seed groups. Additionally, if the variant has already been sent and has not been updated to resend in Edit Seed Groups on the Target step, it will not send again by default.
If there is a recurring campaign and an update is conducted on any one of the variants, you have the option of re-sending to only the updated variants, all variants, or to turn off seed group sending upon update.
Seed groups in Canvas work in a similar fashion to that of any triggered campaign. Braze automatically detects all steps that contain an email message and will send to these when your user first reaches that particular email step.
If an email step was updated after the Seed Group was mailed, the option to only send to updated steps, all steps, or turn off seeds will be presented.