Use Custom Attributes to extend Zeeg CRM beyond the standard fields. Whether you need to capture lead scores, deal stages, or industry-specific data, custom attributes give you the flexibility to build a CRM that lets you track exactly what you need.
What are Custom Attributes?
Custom attributes are fields you create to store additional information in your CRM objects. While standard objects like People and Companies come with built-in attributes (name, email, phone, etc.), with custom attributes you can add fields tailored to your specific needs. They work just like standard attributes: appearing in record forms, they can be filtered and sorted, and are included in exports and reports.
Examples: “Lead Score”, “Lead Source”, “Deal Stage”, “Annual Revenue”, “Customer Since”, “Assigned Agent”. Custom attributes
Custom Attributes are available on Business, Scale, and Enterprise plans.
Business Plan - 5 custom attributes per object
Scale Plan - 10 custom attributes per object
Enterprise Plan - 50 custom attributes per object
"Per object" means you get these limits for each standard object (People, Companies) and each custom object you create. For example, on the Scale plan with 2 custom objects, you could create up to 40 total custom attributes (10 custom attributes × 4 objects).
How to create custom attributes
1. Click on your Workspace on the top left corner and navigate to Workspace Settings.
2. On the left side of the toolbar, refer to Objects under Objects.
3. Then, click on the object where you want to add the attribute (People, Companies, or a custom object). Click + Create attribute.
4. Enter a Name: In this example, we'll call it "Deal Stage" - this is what users will see in the interface.
5. Select a Field Type: Choose "Status" from the 13 available options. We're using Status because it's perfect for tracking pipeline stages. Choose carefully as changing types later may affect existing data.
6. Configure type-specific settings: Since we selected Status, we need to add our pipeline stages. Click + Add option to create each stage:
New Lead (Color: Blue)
Qualified (Color: Purple)
Proposal Sent (Color: Orange)
Negotiation (Color: Yellow)
Closed Won (Color: Dark Blue)
Closed Lost (Color: Red)
7. Then, set field rules:
Required: Check this only if every deal must have a stage assigned. For this example, we'll check it because every deal should have a stage.
7. Click Create. The new attribute is now available in all records of that object.
Attribute types
Zeeg CRM supports 13 different attribute types. Choosing the right type is crucial for data validation, filtering, and reporting.
1. Text: Best for short text entries up to 255 characters like Job Title, Lead Source, or Reference Number. You can optionally validate for email or URL format and enforce uniqueness to prevent duplicate values.
2. Number: Best for numeric values without currency, such as Lead Score (0-100), Number of Employees, or Years in Business.
3. Phone number: Best for phone numbers with validation. Better than Text because it validates the format and supports international numbers.
4. Date: Best for calendar dates without time, like Contract Start Date, Birthday, or Next Review Date. Includes a calendar picker and supports date-based filtering.
5. Date and time: Best for dates with specific times, such as Last Contact, Meeting Scheduled, or Webinar Start Time. Time zone aware and perfect for scheduling.
6. Checkbox: Best for yes/no values like Subscribed to Newsletter, VIP Customer, or Contract Signed. Simple checked/unchecked state that's easy to filter.
7. Select: Best for single choice from a predefined list, such as Industry, Lead Source, or Priority Level. You define the options, users select exactly one, and options can have custom colors. Example setup for "Lead Source": Website, Referral, LinkedIn, Conference, Cold Outreach, Partner.
8. Multiselect: Best for multiple choices from a predefined list, like Interests, Services Interested In, or Product Categories. Users can select zero, one, or multiple options.
9.Status: Best for single choice representing a state or stage, such as Deal Stage or Support Ticket Status. Similar to Select but specifically for workflow states. Perfect for pipeline tracking. Example setup for "Deal Stage": New Lead → Qualified → Proposal Sent → Negotiation → Closed Won / Closed Lost.
10. Rating: Best for 1-5 star ratings like Customer Satisfaction, Lead Quality, or Priority Level. Visual star display that's easy to filter and sort.
11. Currency: Best for money values like Deal Value, Annual Revenue, or Contract Value. Supports 10+ currencies (USD, EUR, GBP, etc.), configurable decimal places, and proper formatting. Never use Text or Number for money.
12. User: Best for assigning team members to records, such as Account Manager, Sales Rep, or Support Agent. Shows a dropdown of team members in your workspace. Great for workload distribution and accountability.
13. Relationship: Best for connecting records across different objects. Creates links between two objects so records can reference each other. This is the most complex attribute type: see the dedicated section below for details.
A closer look on Relationship Attributes
Relationship attributes create links between records in two different objects. For example, connecting a person (John Doe) to a company (Acme Corp) means when you view John's record, you see his company, and when you view Acme Corp, you see all people who work there.
There are four relationship types
1. One-to-One: One record connects to exactly one other record.
Example: CEO to Company—each company has exactly one CEO, and each person can be CEO of only one company.
2. One-to-Many: One record connects to multiple records on the other side.
Example: Company to Employees—one company has many employees, and each employee works at one company. This is the most common relationship type.
4. Many-to-Many: Records on both sides can connect to multiple records on the other side.
Example: People to Projects—one person can work on multiple projects, and one project can have multiple team members.
How to create a Relationship Attribute
Scenario: You run a sales team and want to track which salesperson is responsible for each deal.
What you want:
When viewing a Deal, see which salesperson owns it
When viewing a Person (the salesperson), see all their deals
Step-by-step:
1. Create a new Attribute
Go to Workspace Settings on the left menu, and scroll down to Objects
Find your object and click on it
Click on “+ Create attribute”
2. Configure your Custom Attribute
Give it a name. In this example, we'll call it "Account Owner"
Set "Relationship" from the Type dropdown menu
Select the Relationship Type: "Many to one" - because many deals can belong to one salesperson, but each deal has only one owner
Choose the Related Object: Select "People" - because we're linking deals to salespeople
Under "Associate attribute name", enter "My Deals" - this creates the reverse field on the Person object
Click Create.
What happens now: When you open a Deal record, you'll see a field called "Account Owner" where you can select which salesperson owns this deal
When you open that salesperson's Person record (in this case, Emma), you'll see a section called "My Deals" that automatically lists all deals where they are the Account Owner.
This bidirectional relationship keeps everything connected and up-to-date automatically.
If you created an attributed by mistake or no longer wish to see it, you'll have the option to archive. Attributes are archived rather than permanently deleted to preserve historical data and activity logs. The attribute is hidden from record forms but existing data is preserved. To archive an attribute, simply click the three dots (...) next to it and choose Archive.
Custom Attributes best practices
Plan before you create
Before creating attributes, ask yourself:
What information do I need to track?
What's the right field type for this data?
Is this field required for every record?
How will I use this data for filtering or reporting?
Use clear, descriptive names
Choose names like "Deal Value" instead of just "Value"
Be consistent with naming: if you use "Contact Date" in one place, don't use "Date Contacted" elsewhere
Avoid abbreviations unless they're universally understood in your team
Be strategic with required fields
Only mark fields as Required if they're truly essential for every record. Overusing required fields can frustrate users and slow down data entry.
Choose the right field type
The field type you choose affects data validation, filtering, and reporting:
Use Currency for money, not Text or Number
Use Phone Number for phone numbers, not Text
Use Date or Date and Time for temporal data
Use Select or Status for predefined options to maintain consistency
Review and refine
After a month of use:
Check which attributes are being used and which aren't
Remove unused fields to keep your CRM clean
Add new attributes based on team feedback
Adjust options in Select/Status fields as needs evolve
Frequently asked questions
Can I change an attribute's type after creation?
No, you cannot change an attribute's type after it's been created. This is why it's important to plan carefully and choose the right field type before creating your attribute. If you need to track different data, you'll need to create a new attribute with the correct type.
Can I delete custom attributes permanently?
Custom attributes are archived rather than permanently removed. This preserves historical data and activity logs. Archived attributes can be restored if needed.
How many custom attributes can I create?
This depends on your Zeeg subscription plan:
Business: 5 custom attributes per object
Scale: 10 custom attributes per object
Enterprise: 50 custom attributes per object
"Per object" means you get these limits for each standard object (People, Companies) and each custom object you create.
Example: On the Scale plan with 2 custom objects, you could have 10 attributes on People, 10 attributes on Companies, 10 attributes on Custom Object 1, and 10 attributes on Custom Object 2, for a total of 40 custom attributes.
Can I use custom attributes in automations and workflows?
Yes! Custom attributes can be used in workflow triggers, conditions, and actions just like standard attributes.