> ## Documentation Index
> Fetch the complete documentation index at: https://docs.unifygtm.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Play triggers

> Choose when a play runs and which records it receives.

## Overview

Plays run on individual records, such as companies or people. Triggers define
when a play should run and what data should be provided to it. Below are the
triggers you can choose from when creating a play.

## How triggers run

### Timing

Most automated triggers run on a recurring schedule. When the schedule runs,
Unify checks which records currently match the trigger, removes records that
have already run through the play, and starts new play executions for the
remaining records.

For **Record matches criteria** and **Record enters an Audience** triggers, this
means a record can run when it already matches at publish time or when it starts
matching later. By default, the same record will not run through the same play
again after it has already started a play execution. To allow the same record to
run again after a waiting period, configure [play settings](https://docs.unifygtm.com/reference/plays/play-settings.md).

Automated trigger schedules are managed by Unify. Record match and audience
triggers are evaluated about every 15 minutes. Lookalike company triggers are
evaluated about every 30 minutes.

### Outputs

The record type you choose in the trigger determines the output of the trigger
and which actions can connect directly to it:

| Trigger output | Common next actions |
| - | - |
| Company | Prospect, Get People, Assign owner, CRM sync, Slack alert, Webhook |
| Person | Sequence, Get Company, Assign owner, CRM sync, Slack alert, Webhook |

If a play triggered by a company needs to enroll people in a sequence, add a
**Prospect** or **Get People** action first. **Prospect** can find net-new or
existing people, while **Get People** only returns people that already exist in
Unify.

## Available triggers

### Champions

This trigger is a shortcut for running a play on champions that Unify has
tracked for your business. Once selected, you can customize the matching
criteria similar to the record match trigger. This trigger always returns
people.

![The configuration panel for a champions trigger.](https://mintcdn.com/unify-19/avtuudRDiSi2SYXV/images/reference/plays/triggers/champions-trigger.png?fit=max\&auto=format\&n=avtuudRDiSi2SYXV\&q=85\&s=9e8400e606e97f0ca5f8f59e57acea70)

The configuration panel for a champions trigger.

In order to use this trigger, you must have enabled and configured champion
tracking in your settings. For more information, see [Champion tracking](https://docs.unifygtm.com/reference/signals/champions.md).

### Find lookalike companies

This trigger runs a play on companies that are similar to a set of companies
you specify. This is useful for finding new companies that are similar to your
existing customers or ideal customer profile.

![The criteria panel for a lookalike companies trigger.](https://mintcdn.com/unify-19/avtuudRDiSi2SYXV/images/reference/signals/lookalikes-criteria-panel.png?fit=max\&auto=format\&n=avtuudRDiSi2SYXV\&q=85\&s=9232958a0d4e4bf92903da7c4db35855)

The criteria panel for a lookalike companies trigger.

Once you've defined the criteria that specifies which companies to find
lookalikes for, you can define some additional options for the trigger, such as
additional filters to apply or exclusions to enable and disable.

![The configuration panel for a lookalike companies trigger.](https://mintcdn.com/unify-19/2bGCds6YQ9Qo4--E/images/reference/signals/lookalikes-configuration-panel.png?fit=max\&auto=format\&n=2bGCds6YQ9Qo4--E\&q=85\&s=11e4dd11db05b12b7586fa07031668d5)

The configuration panel for a lookalike companies trigger.

Unify manages the data providers used to find lookalike companies.

### Record enters an audience

This trigger runs a play on companies or people that are in an audience and have
not already run through the play. A record enters an audience when it meets the
audience criteria for the first time.

![The configuration panel for an audience trigger.](https://mintcdn.com/unify-19/avtuudRDiSi2SYXV/images/reference/plays/triggers/audience-trigger.png?fit=max\&auto=format\&n=avtuudRDiSi2SYXV\&q=85\&s=60567c5ebe148cf64a25f044c15e06e3)

The configuration panel for an audience trigger.

When you select an audience trigger, you will be prompted to select an audience
from the list of audiences you have created. Audiences are reusable in Unify,
which means you can use the same audience in multiple plays.

You also have the choice to run the play on either companies that enter the
audience or people that enter the audience. If you select companies, the output
of this trigger will be a company record. Otherwise, the output will be a person
record.

### Record matches criteria

This trigger runs a play on companies or people that match a set of filters and
have not already run through the play. This trigger behaves the same as the
audience trigger, but it doesn't require that you already have an audience
created. Instead, you can define the filters directly in the play.

![The configuration panel for a record match trigger.](https://mintcdn.com/unify-19/avtuudRDiSi2SYXV/images/reference/plays/triggers/record-match-trigger.png?fit=max\&auto=format\&n=avtuudRDiSi2SYXV\&q=85\&s=30ce5eda62f417165fc4c63d5821eaad)

The configuration panel for a record match trigger.

When you select a criteria trigger, use the
[filter builder](https://docs.unifygtm.com/reference/filter-builder.md) to choose the companies or people
the play should run on. Preview the matching records before saving the trigger.

As with audience triggers, you can choose to run the play on either companies or
people. This will determine what type of record the trigger outputs.

### Website visitors

This trigger is a shortcut for running a play on companies that visit your
website. Once selected, you can customize the matching criteria similar to the
record match trigger. This trigger always returns companies.

![The configuration panel for a website visitors trigger.](https://mintcdn.com/unify-19/avtuudRDiSi2SYXV/images/reference/plays/triggers/website-visitors-trigger.png?fit=max\&auto=format\&n=avtuudRDiSi2SYXV\&q=85\&s=b553c9c2cfbbc7ab9b3d6510060c8b89)

The configuration panel for a website visitors trigger.

### Record manually added

This trigger runs a play on a company or person that is manually added by a user.
It runs when someone explicitly sends a record to the play.

![The configuration panel for a record manually added trigger.](https://mintcdn.com/unify-19/avtuudRDiSi2SYXV/images/reference/plays/triggers/record-manually-added-trigger.png?fit=max\&auto=format\&n=avtuudRDiSi2SYXV\&q=85\&s=2c903673e4a1f7edde70033a8fbba4f6)

The configuration panel for a record manually added trigger.

When you select a manual trigger, you will be prompted to choose whether the
play should accept companies or people. This determines the type of record that
the trigger outputs.

Once the play is active, you can manually add records to it from anywhere in
Unify where you can select companies or people. This is useful when you want
full control over which records enter a play, rather than relying on automated
signals or filter criteria.

## Questions

> [accordion] Should I use an audience trigger or a record match trigger?
>
> Audience triggers and record match triggers can both be used to accomplish
> the same goal. The main difference is that audience triggers require you to
> create an audience ahead of time, while record match triggers allow you to
> define the filters directly in the play.
>
> Audiences can be reused in multiple plays, which is useful if you have a set
> of filters that you use frequently. Audiences can also be viewed, edited,
> and exported from the **Audiences** tab.
>
> Use a record match trigger when iterating on a play or
> if you don't want to create an audience for a one-off play. You can always
> come back later, convert the filters into an audience, and then swap the
> trigger out for an audience trigger.

> [accordion] Is an audience trigger the same as sending an audience to a manual trigger?
>
> Audiences are dynamic lists of companies and people that can change over
> time according to the filters you specify. For example, an audience might
> capture all companies that have visited your website in the last 30 days.
>
> When you send an audience to a manual trigger, you are sending the current
> list of companies or people that are in the audience at that moment. This
> is useful if you want to run a play on a snapshot of the audience but not on
> a recurring basis.
>
> By contrast, an audience trigger will keep checking the audience over time
> and run the play for matching companies or people that have not already run
> through that play. This is useful if you want the play to run on records that
> match now and records that match in the future.

> [accordion] Can I make an automated trigger run only on future matches?
>
> Automated triggers evaluate matching records when the play is published and
> on future scheduled checks. If you only want future matches, add a time-based
> condition to the trigger or audience, such as a recent activity date, created
> date, or signal timestamp that represents the future window you want to
> target.
>
> If you need a one-time snapshot instead, use a manual trigger and send the
> selected records to the play manually.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.