The Plain-English Systeme.io Word List

A funnel is really a strategy. It takes people from not buyers to buyers. In Systeme.io, it's the set of pages, in order, that does that. It gets its name from the shape: really wide at the top and very narrow at the bottom.

Example: Your signup page, then your thank-you page. That's a whole funnel.

One page inside a funnel. That's all it is.

Example: Your signup page is one step. Your thank-you page is another.

Watch out: The order matters. When someone fills in your signup form, they land on the next step. So keep your thank-you page right after it.

The simple way to look at it: it's any page that's trying to get someone's contact information. You're squeezing an email address out of a person. I've seen that done in a bad way, but it can be done in a good way, like giving them something useful in return.

Example: "Get the free packing checklist," with a form and a button.

Watch out: A lot of tutorials say "squeeze page." Systeme.io's help articles say "opt-in page." They mean the same thing.

The page people land on right after they sign up or buy.

Example: "You're in. Check your inbox for your checklist."

Watch out: There's one kind for opt-ins and one for sales. Pick the one that matches your funnel.

The page that explains what you're selling and why it's worth buying. Then it sends people to the order form.

Example: A page about your paid trip planner with a "Get the planner" button.

The page where people actually buy. This is where they enter their payment details.

Example: The page that "Get the planner" button opens.

A person on your list. Simple as that.

Example: Someone who signed up for your checklist.

A label you put on a contact, so you can sort people out later.

Example: Everyone who wants the checklist gets the tag "packing-checklist."

One email, sent one time. You can send it now, schedule it, or send it only to people with a certain tag.

Example: "Here are my two best tips for flying with kids."

A series of emails that go out in order, with a wait between each one.

Example: The checklist today, one tip two days later, then another tip two days after that.

The address your emails come from. You confirm it under Settings, then Emails.

Example: hello@yourdomain.com.

Watch out: You can't use a Gmail address to email your list. Systeme.io recommends an address on your own domain.

Your own web address, connected to your pages.

Example: Your signup page lives at yourdomain.com instead of a default address.

This one sounds complicated, but here's the simple way to look at it. You add a few records at your domain host, and those records show email providers you've allowed Systeme.io to send for your domain.

Example: You add the records Systeme.io gives you under Settings, then Emails.

The simple way to look at a rule is "When this happens, do that."

Example: When someone signs up, send them the checklist.

The "when this happens" part. It's the event that starts a rule.

Example: Funnel step form subscribed. That's Systeme.io's way of saying someone filled in your form.

The "do that" part. It's what happens after the trigger.

Example: Send email.

Watch out: If a rule starts with the "Tag added" trigger, it only works for tags added after you set up the rule.

A bigger automation you build on a visual map. It can have waits and yes-or-no paths.

Example: Wait three days. If the person has the "customer" tag, send one email. If they don't, send another.

How a digital product gets charged, such as one payment, a subscription, or a payment plan.

Example: $20 once, or $10 a month for three months.

A small checkbox on the order form that adds something extra before they pay.

Example: "Add the printable luggage tags for $5."

A second offer shown after the first purchase. It's charged separately.

Example: They buy the planner, then see an offer for a full trip-planning course.

A smaller or cheaper offer shown after someone says no to an upsell.

Example: They pass on the course, then see a one-page budget sheet instead.