Back to Blog

    CRM & Automation

    Keap Tags vs Campaigns Explained in Plain English

    A plain explanation of how tags, campaigns and goals work together in Keap Max Classic, written for business owners rather than certified partners.

    Valentina, founder of Rellatech

    Valentina Akpan: Founder of Rellatech, providing administrative and operations support to executives, founders, business owners and teams. Her background combines technical support, customer success, administration and operations.

    ·

    Many Keap Max Classic accounts become disorganized because the owners were never given a clear explanation of what a tag is and what a campaign is. As a result, tags are used like campaigns and campaigns like tags, and the account ends up with hundreds of tags that no campaign uses and that do not do what the owner expects.

    Below is the simplest explanation I can give you.

    Tags are labels, and campaigns are workflows

    A tag is a label on a contact. It records something like 'this person attended my March webinar' or 'this person bought the starter package'. A tag does not do anything by itself. Campaigns are the workflows that look for tags and then take action, such as sending an email, waiting three days, applying another tag and sending another email.

    How the parts fit together

    • ●Tag = state. What is true about this contact right now?
    • ●Goal = trigger. What event causes the workflow to start? Usually 'tag applied'.
    • ●Sequence = the workflow. The emails, waits, and actions that happen in order.
    • ●Campaign = a container holding goals and sequences that belong to one outcome (e.g. the entire welcome series).

    Common mistakes

    • ●Using tags to send emails directly (you can't, you need a campaign).
    • ●Creating a new campaign for every email instead of reusing sequences.
    • ●Forgetting that a sequence keeps running on a contact even after their state changes. If someone unsubscribes partway through a sequence, you need a campaign to remove them.

    A clear way to group tags

    Group tags into four categories. Every tag in your account should fit into exactly one.

    • ●Source: where did this contact come from? (e.g. 'Source - Wufoo Form A', 'Source - LinkedIn Ad')
    • ●Lifecycle: where in the journey are they? ('Lifecycle - Lead', 'Lifecycle - Customer', 'Lifecycle - Churned')
    • ●Product: what have they bought or expressed interest in? ('Product - Starter', 'Interest - Coaching')
    • ●Behaviour: what did they do? ('Behaviour - Clicked Webinar Replay', 'Behaviour - Opened 5+ emails 30 days')

    If a tag does not fit one of those four categories, find out what it was for before you change it. A large number of tags is fine as long as each one has a purpose and you know what depends on it.

    Check dependencies before you delete or rename a tag

    A tag that looks unused may still be in use. Before you delete or rename one, check what refers to it. Deleting a tag removes it from every contact and breaks each of those references without any warning, so I work in this order: list where the tag is used, decide what replaces it, update the references, and then remove the tag.

    • ●Campaign goals that start a sequence when the tag is applied.
    • ●Sequence steps that apply or remove the tag, and decision diamonds that branch on it.
    • ●Saved searches, reports, and dashboards filtered by the tag.
    • ●Merge fields or dynamic content in emails that depend on it.
    • ●Integrations, forms, and Zaps that apply the tag from outside Keap.

    Tags vs custom fields

    Use a custom field when the value always exists and changes over time, like plan tier or renewal date. Use a tag when the fact is yes or no and historical, like attended a specific webinar. A field holds one value, so when it is overwritten the old value is gone. If you need the history, a tag or a note is the better record. Many accounts use tags where a field would be the better fit, and the result is a tag for every possible value of something that should have been one field.

    FAQ

    Yes. Keap was designed around a two-part model, where tags describe a contact's state and campaigns respond to it. Using only one or the other creates more work.

    A goal is the entry point into a sequence. It says 'when X happens, start the sequence below'. The most common goal type is 'tag applied'. Other goal types include form submitted, link clicked, purchase made, and API call.

    There is no right number, and contact count does not tell you whether an account is safe to clean up. The test is whether each tag has a stated purpose, fits one category, and has known dependencies. An account with many tags that are each used by a known campaign is in good shape, while an account with a few tags you cannot explain needs attention.

    Sometimes. Use a custom field when the value can change but always exists (e.g. plan tier). Use a tag when the value is binary and historical (e.g. 'attended webinar X'). Check what reads each one before you switch, because campaigns and searches built on a tag will not see a field.

    Help reviewing your Keap account

    I help review Keap and Infusionsoft records, campaigns and integrations, then scope the corrections and documentation needed. You can find the scope and pricing on the Keap & Infusionsoft Consultant service page.

    Book a free call

    Choose a time that suits you on the booking page. On the call, tell me what needs attention and which tools you use. Any detailed audit or implementation is scoped separately.

    Share This Article

    Comments

    Join the conversation.

    Loading comments…

    Leave a comment

    Tell me what you need help with, and I will suggest where to start.

    Book a free call

    First month free

    Rella: a CRM built for coaches.

    Rella keeps your enquiries, clients, session notes, intake forms, tasks and online booking in one place. You can try it free for your first month.