---
"@context": https://schema.org
"@type": TechArticle
"@id": https://www.twilio.com/docs/segment/guides/audiences-and-journeys#article
headline: Audiences, Journeys, and Broadcasts
description: Compare Audiences, Journeys, and Broadcasts in Twilio Engage and learn how to choose the right one for marketing use cases across the customer lifecycle.
url: https://www.twilio.com/docs/segment/guides/audiences-and-journeys
inLanguage: en
dateModified: 2026-10-02T18:50:10.000Z
author:
  "@type": Organization
  name: Twilio Developer Education Team
publisher:
  "@type": Organization
  name: Twilio
---

# Audiences, Journeys, and Broadcasts

* FREE: x
* TEAM: x
* BUSINESS: ✓
* ADDON: ✓

Engage Foundations requires a Business tier account and includes Unify.

See the [available plans](https://segment.com/pricing), or [contact Support](https://segment.com/help/contact/)

Audiences, Journeys, and Broadcasts are fundamental to [Twilio Engage](/docs/segment/engage/) and let you segment your users, send them personalized content, and show them ads from platforms like Facebook or Google. This guide explains how to choose between an Audience, a Journey, and a Broadcast for marketing use cases across the customer lifecycle.

## Definitions

An Audience, a Journey, and a Broadcast each serve a distinct purpose in Engage.

### Audience

In Engage, an [Audience](/docs/segment/engage/audiences/) is a group of users that share certain characteristics. When you create an Audience, you group users who meet certain conditions, like having performed an event or having a [Computed Trait](/docs/segment/unify/traits/computed-traits).

Once you've created an Audience, you can sync it to [marketing automation tools](/docs/segment/connections/destinations/catalog/#marketing-automation), [ads platforms](/docs/segment/connections/destinations/catalog/#advertising), [analytics tools](/docs/segment/connections/destinations/catalog/#analytics), or [data warehouses](/docs/segment/connections/storage/warehouses/). Depending on the Audience's conditions and [connected Destination(s)](/docs/segment/connections/destinations/), Segment syncs the Audience's users in batches or in real time, as they meet the Audience's conditions.

### Journey

A [Journey](/docs/segment/engage/journeys/) is a logic-driven workflow that progresses users through steps based on conditions and time delays. You add users to a Journey with an entry condition, then users progress through [the Journey's steps](/docs/segment/engage/journeys/v1/#journey-step-types) based on conditions you define during Journey setup.

As with Audiences, Segment can sync users to Destinations at designated points in the Journey.

## Engage and the customer lifecycle

The customer lifecycle provides a helpful framework for thinking about Audiences, Journeys, and Broadcasts.

![Digital marketing lifecycle funnel with stages: Brand Awareness, Nurture, Drive Intent, Post-Conversion.](https://docs-resources.prod.twilio.com/bb1b356f564f6b459d479a07c5d9d70ae0bf55f45d46b296aa926e97a6baeed4.png)

Audiences and Broadcasts tend to be most effective at the top of the customer lifecycle funnel, where brand awareness and discovery occurs.

A Journey becomes a better option as customers progress down the funnel, where a more complex strategy involving messaging, social ads, and newsletters helps move customers closer to conversion.

## Choosing between Audiences, Journeys, and Broadcasts

To choose between an Audience, a Journey, and a Broadcast, match your use case against the following table, then weigh the additional questions below. With the customer lifecycle in mind, use this table as a starting point for common marketing use cases:

| Use Case                                         | Audience, Journey, or Broadcast |
| ------------------------------------------------ | ------------------------------- |
| I want to send email and SMS campaigns.          | Journey or Broadcast            |
| I want to send a one-time email or SMS campaign. | Broadcast                       |
| I only have one intended touchpoint.             | Audience or Broadcast           |
| I need branching logic.                          | Journey                         |
| I want to run A/B tests.                         | Journey                         |
| I want to re-target customers with the same ad.  | Audience                        |

While these suggestions will work for most use cases, you may need to consider other factors before you implement your own campaign. Asking the following questions will help you identify the right approach.

### Over the course of a campaign, how many touchpoints do I want to create?

Audiences and Broadcasts work best for single, one-off messages or touchpoints. If you need a campaign with time delays and branching logic, opt for a Journey.

For example, an Audience works well if you want to show a single ad when a user abandons a cart. If, however, you want to show an ad, wait several days, then send the user an email if they've not completed their purchase, go with a Journey.

### Do I need branching logic?

Create a Journey if you want to incorporate branching logic into your campaign.

### Do I want to conduct an A/B test or create a holdout group?

A number of Journeys step types, like [randomized splits](/docs/segment/engage/journeys/v1/#randomized-splits), let you run experiments and test your campaigns. If you want to experiment with different groups, use a Journey.

### Do I want my customers to receive the same campaign more than once?

With Journeys, you can allow customers to re-enter a Journey they've exited or restrict them to a one-time Journey.

Audiences, on the other hand, admit users whenever they meet the Audience's criteria. For example, you may want to retarget a user with an ad whenever they view a page on your website. In this case, an Audience works well since the user can re-enter the Audience regardless of how many times they've already done so.

## Putting it together

With this guidance in mind, take your next steps with Engage by learning [how to build a Journey](/docs/segment/engage/journeys/v2/event-triggered-journeys) and [work with Engage Audiences](/docs/segment/engage/audiences/).
