You have contacts in your email tool, buyers in your payment service and sign-ups in a Google Form. A client record, often called a CRM, doesn’t have to be complicated. It should answer a few questions, every time:
- Who is this person?
- May I email her?
- How did she find me?
- What has she bought or joined?
- What would be a helpful next step for her?
If your records can’t answer those, more fields won’t help.
Start with who she is and whether you may email her
An email address is a good way to recognise someone, but it isn’t permission to email her. Keep whether she’s subscribed as its own piece of information, and make sure it comes along when you import. Someone who once unsubscribed mustn’t become a subscriber again because a column in a file was missed.
Keep only what you use. Name, email, language and where she came from are often enough. Phone and company only matter once you use them, for an invoice, say.
Note where she came from, once
The source is how you first connected: a workshop sign-up, an interest list for a course, a free meditation or a purchase. Write it the same way every time so you can compare later.
Don’t overwrite the first source every time she clicks a new link. Later clicks belong in her history, while the first source shows how she found you.
Tags that change what you do
A good tag says something that could change what you do:
interest-podcastcustomer-breathwork-courseattended-workshop-aug-2026coaching-applicant
Avoid tags such as important, new-list-2 or a separate tag for every email ever sent. If you can’t say what a tag changes, remove it.
Separate contacts from members without splitting the person
A contact can get email without having an account. A member has signed in and may have access to courses. The roles are different, but the same person shouldn’t turn into two records that don’t know about each other after a purchase.
What you need to see is her contact details together with her access, purchases, bookings and course progress. Then you can answer a question without opening four systems.
Build segments around a decision
A segment is a question you ask your list, not a permanent label. For example:
- subscribers interested in podcasting who haven’t bought the podcast course
- participants with access to a course who haven’t logged in for 21 days
- people who came to the workshop but didn’t go on to the next offer
Each segment should lead to something: a specific email, an export or going through the list yourself. “Everyone active” is fine in an overview, but not always as a mailing list.
Export, so you can move
An export should include email, name, language, tags, subscription state and relevant dates. Test it before you need to move, and avoid any system that takes contacts in but won’t hand them back.
In Idun Blue, contacts, buyers and members live in the same records. Every person has a timeline of purchases, course progress, email, bookings and forms, and you have tags, saved segments and CSV import and export. Anyone who unsubscribed stays unsubscribed when you import. See people and contacts.
