I deactivated the last emails in my campaign. Does it count as completed?

Why the tag does not fire

The tag is added at the moment a contact completes the campaign. Deactivating an email does not produce a completion, so for the contacts sitting at that step the tag does not fire.

systeme.io has a page on deactivating and reactivating a campaign's emails, and a page listing the workflow triggers. Neither one connects the two, so this answer rests on something you cannot open. systeme.io's support team answered it by email on 10 September 2026, and the answer was direct: deactivating the last emails does not complete the campaign for those contacts, so a campaign completion tag is not triggered by removing the final emails. Contacts stay subscribed to the campaign unless they are specifically removed.

What no page says is whether a contact sitting at a deactivated step moves on past it, stays put, or is treated as having reached the end. This answer does not guess at that. The settled part is the outcome: the campaign is not completed for them.

A campaign does not release anybody on its own

That is the part which explains the rest, and it is documented. Even after a contact receives the last email in a sequence, they remain subscribed to that campaign unless they are specifically removed.

So "finished the campaign" and "still in the campaign" are true at the same time. It is also why adding a new email to the end of a campaign enrols every contact still subscribed to it, including people who reached the old ending long ago.

The same holds for a contact who cannot receive anything. Someone who unsubscribes or bounces stays enrolled and keeps moving through the steps on the delays and conditions that were set. The sequence never pauses for them.

What that trigger is called now

You will find it in a workflow. Automations, then Workflows, then open a workflow and click + Add a trigger. Under the Email group sits Email completed, described as firing when a contact has just completed a campaign.

That name is new, which matters if you built the thing earlier. This site read systeme.io's workflow article on 5 September 2026 and again on 12 September, and it was rewritten between those two readings. The older version carried one flat list of triggers with Campaign completed on it, described as firing when a contact completes a campaign. systeme.io does not say anywhere that it renamed anything. What can be said is that the description points at the same event.

How to tag the contacts already sitting there

Support gave two routes, a workflow or tagging by hand, and pointed away from the completion trigger for both.

That second half is the useful part. A workflow hung on the completion trigger has nothing to fire on, because the completion is what never happens. Support did not say which trigger it would use instead, and systeme.io's own note on workflows is that they only trigger on events that happen after the workflow is activated.

Adding the tag by hand is the route systeme.io documents step by step. CRM, then Contacts. Select the contacts, then More actions, then Add tag. A popup asks which tag, then Add tag to contacts.

The rule that catches people out here

Adding a tag is not always only adding a tag. If a rule or a workflow is set to trigger on that tag being added, tagging a contact can set it off, and tagging a large group does it to all of them at once.

systeme.io's own advice on the page that documents tagging is to check the rules already running, understand which triggers are attached to the tag, and work out what could launch automatically, before adding it.

Turning the emails back on is not the fix

systeme.io documents this for one case, and it is worth reading before anybody undoes anything. Deactivate all of a campaign's emails while contacts are still enrolled, then reactivate them, and they are resent to everyone currently enrolled, including the people who already received them. Its recommendation for that situation is to build a new campaign rather than reactivate old emails for people already inside one.

Switching only the final few back on is not the case systeme.io writes up, so treat the same resend risk as a reasonable expectation rather than a documented certainty. Its wording on the other half of the question reads as a rule: only deactivate an email if you are certain it should never be sent again.

A reactivated campaign email is one of three documented ways the same message goes out twice.