# Campaigns

> Campaign is the former name of what Reply now calls a sequence. This page explains where the old name survives and routes to the sequence specification.

**A campaign is a sequence: the former product name for the same object. The old name survives in the legacy v1 API, in older support content and URLs, and in everyday speech; Reply's own help articles still say campaign when they mean sequence. New builds should use the v3 sequences endpoints on docs.reply.io.**

_Status: Reviewed — human-edited, facts not yet confirmed against the product._

> **Campaign vs Sequence.** One object, two names — "campaign" is the legacy name for what
> the current product and API call a [Sequence](/specifications/sequences). This page covers
> where the old name survives; the full specification lives on the
> [Sequences page](/specifications/sequences).

## At a glance

| Aspect | Detail |
| --- | --- |
| **What it is** | The former name of the [sequence](/specifications/sequences) — one object, two names |
| **Belongs to / Contains** | Maps one-to-one onto a sequence; there is no separate campaign object model |
| **Surfaces** | Legacy v1 REST API and older help content — the current UI, v3 API, and MCP say sequence |
| **Key limit** | Sequence limits apply — see [Limits](/reference/limits) |
| **Lifecycle** | Sequence statuses apply: New / Active / Paused / Archived |
| **Does not** | Exist as a separate object — creating a "campaign" creates a sequence |
| **Plans** | All plans |

## One fact

**A campaign is a sequence.** "Campaign" is the former product name for the same object;
Reply renamed it, and this site uses **sequence** everywhere. The full specification lives
at [Sequences](/specifications/sequences).

## Where the old name survives

| Place | What you'll see |
| --- | --- |
| Legacy v1 API | Campaign-named endpoints returning sequence data; the v1 representation differs from v3 (for example, status is reported as a numeric code) — [docs.reply.io](https://docs.reply.io/api-reference/introduction) is the source of truth for both |
| Reply's own help content | Older support articles use the two words interchangeably — "your campaign" for a sequence, "the campaigns will resume", "campaigns still using this schedule" — and older article URLs still live under campaigns paths |
| Common speech and search | "Launch a campaign", "campaign analytics" — this site keeps those phrases in workflow titles because that is what people search for |
| Older integrations | References to campaigns that map one-to-one onto sequences |

## Mapping legacy to current

| Legacy (v1) | Current (v3) |
| --- | --- |
| Campaign | [Sequence](/specifications/sequences) |
| Campaign status (numeric code) | Sequence status — New / Active / Paused / Archived; see [Statuses](/reference/statuses) |
| Campaign statistics fields | Sequence counters — see [Calculations](/reference/calculations) |

## Limits

A campaign is a [sequence](/specifications/sequences), so sequence limits apply: daily
sending volume, per-account caps, and throttling. See [Limits](/reference/limits).

## FAQ

### Is a campaign different from a sequence in Reply?

No. They are the same object — "campaign" is the former name, "sequence" the current one.
The full specification, including lifecycle, settings, and execution behavior, lives at
[Sequences](/specifications/sequences).

### Should new integrations use the v1 campaigns endpoints?

No. Build against the v3 sequences endpoints — the v1 campaigns endpoints are legacy and
return sequence data in the older representation. Consult
[docs.reply.io](https://docs.reply.io/api-reference/introduction) for both versions and
[Terminology](/reference/terminology) for the name mapping.

### Why do workflow titles on this site still say campaign?

Because that is what people search for. Pages like
[Launch an outbound campaign](/workflows/launch-an-outbound-campaign) keep the familiar
phrase in the title while the content uses sequence throughout — the same way Reply's own
help articles still say "campaign" when they mean a sequence.

## Related

- [Sequences](/specifications/sequences) — the real specification
- [Terminology](/reference/terminology) — every synonym mapping
- [Launch an outbound campaign](/workflows/launch-an-outbound-campaign)

## Build with Reply

- REST API: [docs.reply.io](https://docs.reply.io/api-reference/introduction) — v3 sequences endpoints (use these, not v1 campaigns, for new builds)