Static lists vs dynamic segments, and other beginner mistakes

A static listStatic listA snapshot export of customers who matched a rule on a particular day. It starts drifting immediately: members stop qualifying, new qualifiers are missing, and consents change. Fine for genuinely fixed groups, such as event attendees; wrong for anything defined by ongoing behaviour.View in glossary is a snapshot: customers who matched a rule on the day you exported it. A dynamic segment is the rule itself, re-evaluated continuously, so membership updates as behaviour does. The difference sounds technical. It decides whether your segments stay true or quietly rot.

If you're exporting CSVs between systems, you're carrying snapshots, and path 3 shows what connected data does about it.

Four more mistakes that undo good starts

PersonasPersonaA fictional portrait of a typical customer, used to guide tone, creative and empathy. A persona is not a segment: you can't email a portrait. If a persona matters commercially, define the measurable segment that approximates it and check the two actually match.View in glossary wearing segment name badges. "Weekend gardener Wendy" is a creative tool, not an audience (lesson 1.2 drew the line). The mistake is building campaigns "for Wendy" without any defined, countable group behind the name. If a personaPersonaA fictional portrait of a typical customer, used to guide tone, creative and empathy. A persona is not a segment: you can't email a portrait. If a persona matters commercially, define the measurable segment that approximates it and check the two actually match.View in glossary matters commercially, define the segment that approximates it and check the two actually match.

Demographics as a reflex. Age and location are the first fields every tool offers, so they become the first segments every beginner builds. But knowing a customer is 42 and lives in Leeds rarely tells you what to say to them. Behaviour (what they bought, browsed, ignored) almost always predicts response better. Use demographics to sharpen a behavioural segment, the way Matt's 55+ bird-care pattern sharpens a category segment, not to replace one.

Too many segments, too soon. Enthusiasm produces fourteen segments in week one; maintenance reality supports about four. Each segment you keep needs creative, logic, monitoring and a reason to exist. The unloved ones don't just idle, they mislead: numbers get reported, nobody remembers the definitions, decisions get made anyway. Matt's whiteboard purge in lesson 1.4 is the model: build few, test hard, retire fast.

Segments without a decision attached. The subtlest mistake: building segments because the data made them possible rather than because a decision needed them. "Customers who browse on mobile" is buildable in most tools. Unless something in your marketing would change because of it, it's shelf-ware. Before building anything, ask the question Matt now keeps taped to his monitor: what will we do differently if this segment exists?

The habit that prevents all five

Every mistake in this lesson survives on the same fuel: nobody re-examines segments once they exist. So schedule it. Once a quarter, list every segment, its definition, its size, the last campaign that used it, and what that campaign earned. Retire anything with no answer in the last two columns. Twenty minutes, quarterly, keeps the whole system honest. That's segment governance, and you now do it before most enterprises do.

You've finished the foundations, and so has Matt: three dynamic segmentsDynamic segmentA segment defined by a rule that is re-evaluated continuously, so membership updates as customer behaviour changes. The opposite of a static list. "No purchase in 180 days, valid consent" stays correct every day it runs, because whoever matches today is in today.View in glossary, two survivors from the whiteboard, and a quarterly review in the diary. The quiz below checks the whole path; pass it and path 2 introduces the model families properly, starting with a practical map of all five.