> This page is part of the [Customer.io documentation](https://docs-customerio.netlify.app). For the complete index, see [llms.txt](https://docs-customerio.netlify.app/llms.txt).
> Last updated: July 15, 2026

# Trigger automations based on Roles

When you send automations customized by profile roles, you’ll have a better chance of motivating them to take action than if you sent generic messages to everyone.

## Method

Determine how you’re storing data in Customer.io. This will determine the type of automation you should make.

*   Are you storing role information on profiles as [attributesA key-value pair that you associate with a person or an object—like a person’s name, the date they were created in your workspace, or a company’s billing date etc. Use attributes to target people and personalize messages.](/journeys/people/manage/attributes/)?
*   Or are you storing role information on profiless’ [relationshipsThe connection between an object and a person in your workspace. For instance, if you have Account objects, people could have relationships to an Account if they’re admins.](/journeys/objects-data/objects/relationships/) to [objectsAn object is a non-person entity that you can associate with one or more people—like a company, account, or online course.](/journeys/objects-data/objects/) (like Accounts, Companies, Courses)?

### Role stored as profile attribute

#### Build a segment

If you store role data as attributes, you can create a segment to trigger an automation for profiles that belong to it.

1.  Go to **Segments**.
2.  Click **Create Segment**.
3.  Name your segment so it’s easy to find later - like “Marketing role.”
4.  Choose **Data-driven Segment**.
5.  Add an attribute condition. In this example, the role is stored as this attribute `person_employment_role`.

[![image.png](https://docs.customer.io/images/image%28455%29.png)](#d5076a9ab64adf523e123d651006f964-lightbox)

If you have similar roles, you might include them all in one segment. For instance, maybe you have “marketing\_manager” and “product\_marketer” and profiles with any of these roles should receive the same messaging. Change the top condition to “**Any** of the following conditions match” and include all roles in the segment.

#### Create a segment-triggered automation

Now you can use your role-based segment as a trigger for an automation.

Start by creating an automation and choose **Segment change** as the trigger type. Select the segment you made above:

[![image.png](https://docs.customer.io/images/recipe_personalize-campaigns-based-on-roles_trigger-1.png)](#8445cbd77b88f2bab9c3ebe4203b6536-lightbox)

Only users with marketing roles will enter this automation, so you can customize your content for this specific audience. If your segment includes profiles with multiple kinds of marketing roles, you can personalize messaging further with [liquid](/messaging/liquid/using-liquid/) conditionals or [action conditions](/messaging/send/workflows/action-conditions/) based on specific roles.

### Role stored as relationship attribute

If you’re storing role data on a relationship to an object, you can [use the relationship attribute to trigger automations](/messaging/objects-data/objects/relationships-in-automations/). For example, if you have Account objects in your workspace, you could trigger an automation based on the creation of an account and filter the audience to profiles that are admins of the account. You could also trigger an automation when someone becomes an admin on the account.

For instance, maybe you want to nurture admins of accounts to encourage them to upgrade their account. Checkout our recipe on [upselling power users](/messaging/objects-data/use-cases/upsell-users/) to begin.

## Wrap Up

Role based messaging is an ideal way to increase engagement by only showing profiles content relevant to them. Customization based on role is only the beginning! Consider tailoring your messaging based on location, interests, or even company size to create more engaging emails.

If you have questions about how to apply this to your business, [we’re here to answer](https://customer.io/contact/)!

*   *   [Method](#method)
        *   [Role stored as profile attribute](#role-stored-as-profile-attribute)
            *   [Build a segment](#build-a-segment)
            *   [Create a segment-triggered automation](#create-a-segment-triggered-automation)
        *   [Role stored as relationship attribute](#role-stored-as-relationship-attribute)
    *   [Wrap Up](#wrap-up)

Copy page

Copy page [Download .md](/messaging/send/recipes/role-based-messaging-automation.md)

Is this page helpful?

![](https://docs.customer.io/images/export-success.png) ![](https://docs.customer.io/images/export-failure.png)

# How can we make it better?

Close

Do you need help from Customer.io support?  No  
 Yes

What part of Customer.io do you need help with? 

How can we improve this page?

Email (optional):  Please provide a valid email address

 I am not a bot

 

We appreciate your feedback!

Our support team will contact you as soon as possible
