> ## Documentation Index > Fetch the complete documentation index at: https://docs.partnero.com/llms.txt > Use this file to discover all available pages before exploring further. # Entry triggers and re-entry A campaign's entry trigger decides who goes into it and when. Each campaign has exactly one. The re-entry policy decides what happens if the same partner qualifies a second time. *** ### Available entry triggers Campaigns use the same trigger wording as [automations](/knowledge-base/automation/automation), limited to the triggers a sequence can start from. | Trigger | Fires when | Extra settings | | - | - | - | | Partner joins program | A new partner signs up | — | | Partner makes first signup | The partner generates their first referral | — | | Partner generates first sale | The partner's referral makes their first purchase | — | | Partner earns first commission | The partner earns a commission worth more than zero | — | | Partner reaches milestone | The partner passes a threshold you set | Metric, comparison, value | | Partner anniversary | Exactly that many days after the partner joined | Days | | Partner inactive for X days | The partner has neither logged in nor referred anybody for that long | Days | | Partner hasn't referred in X days | The partner's last referral is older than that. Partners who have never referred anybody are measured from the day they joined | Days | | Tag is assigned to partner | One of the tags you select is added to the partner | Tags | *** ### Milestone triggers **Partner reaches milestone** asks for three things: which metric, how it is compared, and the value to compare against. | Metric | What it counts | | - | - | | Signups | Referrals the partner has generated | | Customers | Paying customers the partner has referred | | Revenue (all time) | Total revenue the partner has generated | | Revenue (recurring) | Monthly recurring revenue | Entry triggers compare upwards only — *greater than or equal to* or *equal to*. There is no "less than" here, because a campaign starts when a partner achieves something rather than when they fail to. To branch on a partner *not* having done something, use a condition step inside the campaign, which does offer downward comparisons. Choosing **Revenue (recurring)** adds an **Over the last (months)** field, so you can start the campaign on recent recurring revenue rather than all of it. *** ### Tag triggers **Tag is assigned to partner** starts the campaign when any of the tags you select is added to a partner. You must select at least one tag, and the tag has to exist before you can pick it. This trigger is how you start a campaign by hand. Tag a partner — from their profile, from an automation, or from a step in another campaign — and the campaign picks them up. Because a campaign can also *add* tags, two campaigns can trigger each other without that being visible from either one. Before adding a tag from inside a campaign, check whether anything else uses that tag as a trigger. *** ### Day-based triggers and existing partners Three triggers have no event to listen for, so Partnero sweeps for them once an hour: **Partner anniversary**, **Partner inactive for X days** and **Partner hasn't referred in X days**. This matters when you switch a campaign on, because two of them look at a partner's current state rather than a moment in time: * **Partner inactive for X days** and **Partner hasn't referred in X days** match everybody who is currently past the threshold. Switch on a campaign set to 30 days and every partner who has been quiet for 30 days *or longer* enters on the next hourly sweep. * **Partner anniversary** matches the exact day, so it only catches partners whose anniversary falls on or after the day you switch the campaign on. Event-based triggers never reach backwards. A partner who joined last month does not enter a *Partner joins program* campaign you create today. *** ### Re-entry **If they qualify again**, under the entry trigger, decides what happens the next time a partner meets the trigger. | Policy | Behaviour | | - | - | | Never re-enter | The partner goes through the campaign at most once, ever. This is the default | | Re-enter after a cooldown | The partner can enter again once a set number of days has passed since their last time through | | Re-enter every time | The partner enters again whenever the trigger fires | A partner is never in the same campaign twice at once. If they are part way through, a fresh trigger is ignored regardless of policy. Which to choose depends on whether the thing you are saying is a one-off: * A welcome sequence should be **Never re-enter**. Nobody joins twice. * A re-engagement sequence usually wants **Re-enter after a cooldown**, so a partner who goes quiet again months later gets chased again, but not repeatedly in the same month. * An anniversary campaign wants **Re-enter every time**, so it runs each year. *** ### Leaving the campaign The entry trigger decides who comes in. Three things take a partner out: * **Reaching the end** of the sequence — recorded as completed * **Matching an exit condition** — checked before every step, recorded as left early * **Reaching a condition step with an empty No lane** and not matching it Exit conditions are covered in [Campaign steps explained](/knowledge-base/campaigns/campaign-steps-explained). This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.