> For the complete documentation index, see [llms.txt](https://docs.mediarithmics.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mediarithmics.io/audience-and-activation/build-your-audiences/segment-reference/segment-types/list-automation-segment.md).

# Automation segment

The same list type as an imported list, but filled and emptied by an automation.

## What it is

An **Automation segment** is a list of users populated by an [automation](/audience-and-activation/automate/automations-reference.md) rather than by a file. Users are added and removed as they travel through a scenario, and the segment appears in the segments list with the type `Automation`.

Underneath, this is the same list type as an [imported list](/audience-and-activation/build-your-audiences/segment-reference/segment-types/list-import-segment.md): always persisted, no query, no evaluation period. The shared properties are documented there and are not repeated here. What differs is what fills the list, and one extra attribute.

## The scenario subtype

A segment created by an automation's **Add to segment** node is a list segment with a **scenario** subtype. Two automation nodes act on it:

| Node                    | Effect on the segment                                                                                                           |
| ----------------------- | ------------------------------------------------------------------------------------------------------------------------------- |
| **Add to segment**      | Adds the user travelling through the node. The node's configuration carries the segment name and a time to live in the segment. |
| **Delete from segment** | Removes the user. If the user is not in the segment, the automation moves on to the next node with no action.                   |

{% hint style="info" %}
The **Delete from segment** node only offers list segments in its picker, which is a useful reminder of the boundary: automations can write into a list, but not into a Query segment - membership there is decided by the query.
{% endhint %}

## Time to live and consent

The **Add to segment** node sets a time to live (TTL) - the period after which the user should leave the segment. It exists mainly for regulatory reasons, and it plays the same role as the segment's default lifetime.

The node can also be linked to processing activities, so that user choices govern who ends up in the segment. See [Enforce compliance on your audience](/audience-and-activation/build-your-audiences/enforce-compliance-on-your-audience.md).

## Related pages

<table data-view="cards" data-search="false"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Actions</strong></td><td>The two segment nodes, and every other action an automation can take.</td><td><a href="/audience-and-activation/automate/automations-reference/actions.md">Actions</a></td></tr><tr><td><strong>Build your audience from live user activity</strong></td><td>Reacting to behaviour as it happens.</td><td><a href="/audience-and-activation/build-your-audiences/target-your-audience-based-on-criteria/build-your-audience-from-live-user-activity.md">Build your audience from live user activity</a></td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.mediarithmics.io/audience-and-activation/build-your-audiences/segment-reference/segment-types/list-automation-segment.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.