Overview
When sending user-related data from Zendesk into Amperity, a common question is whether custom attributes should be created as Fields or Objects in Zendesk.
The correct choice depends on what the data represents and where it should appear in Amperity.
Recommended Approach: Use Fields for User Attributes
If the attributes belong to users (for example, customer preferences, flags, or profile details), they should be created as Fields in Zendesk.
Specifically:
Create them under User Fields in Zendesk
These fields are automatically passed through the Zendesk Users API
In Amperity, they appear in the Zendesk:Users table
This is the correct and supported approach for most customer and user-level attributes.
When to Use Objects
Zendesk Objects should only be used when you are modeling a separate entity that is not a User or a Ticket.
Examples where Objects make sense:
Orders
Products
Subscriptions
Custom business entities that have their own lifecycle
If the data is not a standalone entity and is directly tied to a user, Objects are not needed.
Quick Decision Guide
Use Fields when:
The data belongs to a user
You want it available in the Zendesk:Users table
The attribute is part of the customer profile
Use Objects when:
The data represents a separate entity
It is not directly a user or ticket attribute
You need a custom data model outside Users/Tickets
Summary
For Zendesk data flowing into Amperity:
User attributes → Create as Fields
Separate entities → Create as Objects (only if needed)
Using Fields ensures the data flows cleanly through the Zendesk Users API and is available for use in Amperity without additional configuration.