# Rudder Lookout


{{< customreadfile "/includes/lookout/beta-callout.md" >}}

**Rudder Lookout** is an AI-powered analytics and activation agent for marketing teams. You ask questions in plain language, and an AI agent answers them and acts on them against the customer data you already trust — without writing any SQL, raising a ticket, or waiting on an analyst.

Each result that Lookout shares is saved as a durable artifact you can revisit and share, rather than a transient chat reply.

## Audiences and activation

Most of what teams do in Lookout starts with a sentence like *"create an audience of my most valuable customers"*. The agent reads your warehouse, works out which tables hold those people, and drafts the audience.

You then see what it built. Every rule can show you the data behind it — the spread of a numeric column, the values a text column actually contains, and how many people each choice keeps. Adjust a rule and the count moves with it.

When the audience is right, send it to a destination in your RudderStack workspace and it stays in sync from there.

See [Audiences and Activation]({{< ref "lookout/audiences/_index.md" >}}) for more details.

## What Lookout connects to

Lookout works with the systems you connect it to, for example:

- When you link your RudderStack workspace, it can activate audiences to your destinations and read your sources, transformations, and Tracking Plans
- When you link your warehouse, it answers questions on your data and builds audiences from it
- When you approve external AI agents or assistants, they can connect to Lookout through the [Lookout MCP]({{< ref "lookout/integrations/external-mcp.md" >}})

The following integrations are currently supported:

{{< customreadfile "/includes/lookout/integrations-table.md" >}}

## What Lookout produces

Lookout's output is a set of durable artifacts:

{{< customreadfile "/includes/lookout/artifacts-list.md" >}}

## How it works

Lookout reasons over the context a RudderStack team already has — the events flowing through your pipelines, the Tracking Plans that define them, the warehouse they land in, and the destinations they feed. Because of this, a single conversation can move from a warehouse metric, to the audience it suggests, to the ad account that audience is sent to.

Two rules govern how the agent operates:

{{< customreadfile "/includes/lookout/governing-rules.md" >}}

## Next steps

- Set up your workspace with the [Quickstart]({{< ref "lookout/get-started/quickstart.md" >}})
- Build your first audience — see [Audiences and Activation]({{< ref "lookout/audiences/_index.md" >}}) for details
- Review the [Rudder Lookout Key Concepts]({{< ref "lookout/key-concepts.md" >}})
- Connect your tools — see [Integrations]({{< ref "lookout/integrations/_index.md" >}}) for details
- Understand the data model in [Security and Data Handling]({{< ref "lookout/security.md" >}})