The contacts list

What this page is — the contact database: everyone you have a relationship with, as distinct from everyone who might buy.

What it is for — finding a person, segmenting the list, and grouping contacts for campaigns.

The problem it solves — leads are transient; contacts are the permanent record. This page also carries two warnings worth reading before you rely on it: the export writes only the page you are looking at, and the duplicate check can be walked past with a capital letter.

Route: /org/marketing/contacts · Module: mkt_manage_contacts — 12 permissions Permission to view: View Contacts

---

1. What a contact is

	Contact	Lead	Storefront customer
Answers	Who is this?	Might they buy?	Who is shopping?
Can log in	No	No	Yes
Has a pipeline	No	Yes	No
Groups	Yes	No	No
Table	contacts	leads	project_customers

Figure 1 — 1 Contacts · 2 Groups · 3 Create Contact.

---

2. Where contacts come from

The Source column tells you which. A marketing form writes a contact directly — Pulse works it afterwards, which is the boundary between Pulse and Marketing Suite.

---

3. The columns

Figure 2 — Six columns. Real contacts' details are blurred in this documentation; legible rows are invented records.

Column	Holds
Name	First and last name
Email	email
Phone	phone
Company	company_name
Lifecycle Stage	customer · opportunity · subscriber · lead
Actions	View · edit · delete

Contact lifecycle values are not the lead ones

Contacts use customer, opportunity, subscriber and lead. None of those is in the five values a lead uses. Leads and contacts do not share a vocabulary, so do not expect a report to line them up.

---

4. Filtering

Figure 3 — Eight filters. Five of them accept patterns, not exact values.

Filter	Behaviour
Search	Name, email, company
Lifecycle stage	Exact
Group	Exact — from contact groups
City · Company · Job title · State · Country	Pattern match, not exact

Five filters accept patterns

City, company, job title, state and country are matched as patterns rather than exact strings, so Manchester also finds Greater Manchester. Useful, and worth knowing before you conclude a filter is broken.

---

5. Export — read this before relying on it

Export writes every contact matching your current filters

The file is produced by the server from the full result set, not from the rows on screen, so it is complete however many pages the list runs to. Filter first if you want a subset.

The file contains: First Name, Last Name, Email, Phone, Company, Job Title, Lifecycle Stage and Address.

---

6. Duplicates

A contact is checked against existing contacts by email within the project before it is created, ignoring case and surrounding spaces — so [email protected] and [email protected] are recognised as the same person and the second is refused.

An older database may still hold duplicates

Contacts created before that matching was in place can still sit in pairs differing only in capitalisation. A split contact has half its history: activity, group membership and lifecycle stage are each only partly right, and a campaign reading a group can mail the person twice.

Worth doing once: sort the list by email and merge any pairs you find.

---

7. The admin contract

Needs	Or
A selected project	The list is empty
View Contacts	Access denied
Groups configured	The Group filter is empty

---

8. Don't confuse this with…

This	Not this
A contact	A Storefront customer, who can log in
A contact	A lead
Import Contacts	Import Leads — a different screen in a different module
Contact lifecycle values	Lead lifecycle stages

---

9. Troubleshooting

Symptom	Cause
Export has far fewer rows than the list	It writes one page. Section 5
The same person appears twice	Case-sensitive uniqueness. Section 6
A pattern filter matched more than expected	Five filters are patterns. Section 4
Group filter empty	No groups configured