Tags, fields and where segment data comes from

You will be able to set up the tags and fields your tool needs to build segments automatically.

If an email tool has been used for a few years without a plan, its tag list usually looks something like this: "promo", "Promo2", "nov list", "VIP?", "test", "Jas import", "DO NOT USE". Nobody remembers what most of them mean, so nobody trusts them, and nobody builds segments from them. The data was collected, but it cannot be used.

Lesson 6.1 chose which segments are worth building. Next comes the data underneath those segments: how it is stored, where it comes from, what you are allowed to collect, and how to name it so it still makes sense a year from now.

Fields for facts, tags for events and interests

Email tools store subscriber information in two main ways. The names differ from tool to tool, but the idea is the same.

A field holds a fact about a person and has one value at a time. First name, a child's level, postcode area and date of last order are all fields. When the fact changes, the old value is replaced with the new one.

A tag marks that something happened, or that a person has an interest. Downloaded the ordering guide, clicked the wedding cake link, attended a trial class and interested in baking classes are all tags. A person can carry many tags at once. Tags are usually added and only sometimes removed.

As a rough rule, a piece of information with one answer at a time belongs in a field. An event or interest that can sit alongside others belongs in a tag. Some tools also have lists or groups, which work much like tags for this purpose.

The four places subscriber data comes from

Very little subscriber data is typed in by hand. It flows in from four main sources, and each one can be set up to run automatically.

Signup forms are the first. The form from lesson 2.4 can add a tag for the lead magnet and fill a field from any question the form asks. Priya's signup form asks for a child's level, and the answer goes straight into a field.

Link clicks are the second. Many tools can add a tag automatically when someone clicks a particular link in an email, without asking the subscriber anything. Mei Ling's newsletter mentions wedding cakes and links to the wedding page. Everyone who clicks that link can be tagged as interested in weddings without being asked.

Purchases are the third. An integration between an online shop platform and the email tool can pass over who bought, what they bought and when. That fills in "customer" and "last order date" without anyone updating a spreadsheet. If you have no shop integration, for example a tuition centre taking bookings through a form, a tag added when a booking is confirmed does the same job.

Preference pages are the fourth. When a subscriber ticks topics on the preference page from lesson 6.1, the tool records the choices as tags or fields.

Collecting only what you will use

Every piece of data you collect is personal data under the PDPA, which lesson 1.2 introduced. The PDPA asks you to collect data for a purpose you have told people about, and to collect only what that purpose needs.

This matches good email habits anyway. Ask for a child's level if you will send tips for that level. Don't ask for a date of birth just in case.

If you tag clicks so you can send more relevant emails, say so in plain words in your consent line and privacy notice, so subscribers are not surprised by it. If your current privacy notice does not cover click tagging, update it before you start.

Data you are not using is a liability, because it has to be protected and it can be wrong, so keep the data set small.

Writing a naming scheme for tags and fields

Messy tags are the normal result of tagging without a plan. A naming scheme prevents this. It does not need to be elaborate, but it does need to be consistent and written down.

One workable pattern is a prefix for the kind of tag, a colon, then a plain description:

"source: ordering guide", "source: market signup", "source: website footer" "interest: weddings", "interest: baking classes" "action: clicked December dates", "action: attended trial class" "status: customer", "status: re-permission sent"

With prefixes, tags of the same kind sort together in the tool, and anyone can tell at a glance what a tag means and roughly where it came from. Write tags in lowercase, use full words, and leave out private abbreviations. Fields get plain labels, such as "Child level" and "Last order date".

Put the scheme in a short document and keep it next to the tool login. Anyone adding a tag, whether a teammate, a freelancer or you in a year's time, checks the document first.

The order of work, then: sort each piece of information into a field or a tag, cut anything you won't use, check your consent line and privacy notice, connect the four sources, then write the naming scheme down and keep it with the login.

In the activity below you will write your own naming scheme for tags and fields, then set up at least two tags in your tool that are added automatically, from a form signup or a link click.

Write a naming scheme for your tags and fields. Then set up one field filled by a signup form question and at least two tags added automatically by form signups or link clicks.

Course

Junxiong-WFG Organisation is an authorised representative of AIA Financial Advisers Private Limited (Reg. No. 201715016G).