Contact properties

​

Default contact properties

These are the default properties for every contact on Loops. They cannot be deleted.

Contact Property	Example	Merge Tag	API Attribute
Email	[email protected]	{email}	email
First Name	Chris	{firstName}	firstName
Last Name	Frantz	{lastName}	lastName
Notes	Favorite color is blue.	{notes}	N/A
Source	API	{source}	source
Subscribed	true	N/A	subscribed
User Group	Investors	{userGroup}	userGroup
User Id	ask523236	{userId}	userId

​

Source

“Source” describes where the contact originated from.

By default, this value will be “Form” for contacts added via a form, or “API” for contacts added via the API. You can specifiy custom “Source” values when adding contacts via forms and the API.

​

Subscribed

The “Subscribed” value determines whether a contact is able to receive loops and campaigns. Unsubscribed contacts will receive all transactional emails.

Contacts can unsubscribe from your emails using an Unsubscribe link automatically added to your campaigns and loops.

Some important notes:

• We do not charge for unsubscribed contacts.
• We suggest you keep unsubscribed contacts in your audience. If you delete and then re-add them in the future somehow, they may end up being “subscribed” even though they have been unsubscribed.
• You cannot re-subscribe contacts via a CSV upload or from the Audience page in Loops. You can re-subscribe contacts with the API and with some of our integrations.

​

User Group

“User Group” is a useful optional property that you can use to segment contacts. It is a free text field that allows you to easily divide contacts into groups like “Users”, “VIPs”, “Investors” or “Customers”.

Contacts can currently only have one user group value.

​

User Id

“User Id” is a unique external ID you can assign to each contact in your audience. For example, this could be a customer ID from your store or a user ID from your SaaS.

This field is optional but is very useful if you are working with our API. For example, you need a user ID to be able to change a contact’s email address.

​

Custom contact properties

Custom contact properties are additional fields that you can create to store information about contacts.

​

Types of property

Custom contact properties can be one of four different types:

• String
• Number
• Boolean
• Date (see below)

You can specify a property type when creating new properties in Loops.

​

Dates

When sending dates with the API or via one of our integrations, you can use either a Unix timestamp (in milliseconds) or an ECMA-262 date-time string

Timestamps must be in milliseconds and can be sent as either an integer or string.

• 1705486871000 (if the Unix timestamp is 1705486871)

Supported date formats are shown below. These must be sent as a string. Adding a time offset at the end (e.g. +02:00 or -07:00) is optional (if omitted, the date will default to UTC).

• YYYY-MM-DDTHH:MM:SS.sss
• YYYY-MM-DDTHH:MM:SS
• YYYY-MM-DDTHH:MM
• YYYY-MM-DD HH:MM:SS.sss
• YYYY-MM-DD HH:MM:SS
• YYYY-MM-DD HH:MM
• YYYY-MM-DD

​

Reserved names

Note that Loops does not allow the creation of properties with the following reserved names:

• id
• listId
• softDeleteAt
• teamId
• updatedAt

​

Add a property

Option 1

To create a custom contact property visit your Audience, click on any of the column headers and select Add property.

Option 2

Alternatively, scroll to the end of the Audience table and click the + button at the end of the column headers.

The same column header menu can be used to delete properties.

​

Deleting contact properties

To delete a custom contact property, visit your API Settings page and click the trashcan icon next to contact property you’d like to delete.

It is not possible to delete default contact properties.

​

Property in use warning

If you receive a “Property in use” warning modal while deleting a contact property, there are a few things you can check before you’re able to delete the property.

• If the listed email is a Campaign:
  • Check if the property is in use within a merge tag inside the email editor
  • Ensure this property is not being actively used in the Audience filter
• If the listed email inside a Loop:
  • Make sure a draft or running Loop is not using it as part of the Audience filter or as a Trigger