Skip to main content
All CollectionsData Tips, Tools, And Analytics
Using Email "Groups" For Distributed Notifications
Using Email "Groups" For Distributed Notifications

Groups offer flexibility, velocity, and transparency when managing multiple data source accounts

Openbridge Support avatar
Written by Openbridge Support
Updated over 10 months ago

Use a group or “distribution list” to have emails to a project team without using individual email addresses. A group email ensures all group members receive communications. This is perfect for alerts, notices, updates, and more.

Why Use Groups?

Using groups can greatly simplify managing accounts at a given data destination or source.

For example, let's say you create a group email for all your Amazon Advertising accounts called amazon-ads@foo.com. This group has bob@foo.com and sue@foo.com as members. If you use amazon-ads@foo.com, Bob and Sue will get notifications, alerts, or updates as the user email in Amazon Advertising. If you have 5, 10, 20, 100... Amazon Advertising profiles using a group email is incredibly convenient.

Some other benefits of using group emails:

  • Adding / Removing Recipients: If you have a new team member, Nancy (nancy@foo.com ), adding here to the group is trivial. Likewise, if Bob leaves the company, his access can be removed quickly.

  • Broad Visibility: All team members get notifications if there are permission or authorization errors. For example, a client removed your access to reports. This removal disables API authorization for data collection. A team email, rather than individual emails, allows you to respond more quickly. For example, if bob@foo.com was the primary email and Bob was on vacation, nobody on your team would know that there was an alert sent bob@foo.com. However, using a group email amazon-ads@foo.com ensures that Bob, Sue, and Nancy get notified.

Ultimately, the goal of the group email is to increase the velocity of notifications, alerts, and other email communications. This approach will increase transparency and reduce the impact of upstream changes like permission removals.

For a reference on how to set up groups with Google, see https://support.google.com/a/answer/9400082

Did this answer your question?