Contact Fields

In the "Contact Fields" section we have access to two different types of fields: system fields and custom fields. We'll start with the custom fields. If we need to add any custom fields for our contacts, we can do it by clicking the "Add new custom field" button:



After that, a column will appear on the right side of the screen that will allow you to edit the new field:



Types of custom fields

You can create different types of custom fields. You can also give them a name and an ID of it's own, as well as assign them with a different icon than the default one. Some of these fields allow you to mark them as "required". In others, that option is marked by default, since they need to be filled in case of use. We'll now discuss the different types, one by one:

  • Text: allows the contact to add one or multiple words. An example could ve a text field to define the town of the contact. That way, the field could be filled with text like "Newark" or "London", for example. You can also add a default value. This could be useful if your store only sells in a particular city. For example, if you only sell in Los Angeles, the default value could be that text. 

  • Email: allows you to record an email address. As such, it can only be filled with one. There needs to be an @, and it must end with .com, .es, .net, etc. You can make it a required field and also use a default value.

  • Phone: allows you to register a contact's phone number. It's possible to use this field to send SMS texts to the contacts that have it filled. In this case, you can make it required or leave it as an optional field. Instead of a default value, it has a default code for a country. It's useful if your site only has contacts from a particular country. In that case, you select the code for that country (for example, in Spain, is +34).

  • Integer: allows you to register a number as a contact field. In this case, instead of asking for the age, we can ask for the year a contact was born. We have to select  minimum and a maximum, in this case, 1920 and 2021, to cover the biggest gap possible. You can select this as a required field for every contact.

  • Decimal: as in the previous case, it allows you to register numbers, but this time, only of the decimal type. Aside from allowing you to choose if it's required, this field let's you decide the amount of decimals permitted, as well as if it will be a period or a comma. This field could be useful if, for example, we want to follow the amount of money our contacts are expending on our site.

  • Date: allows you to add a date as a contact field. It can be required or optional, and you can also select a minimum date. We can use this type of custom field to complement a strategy regarding your products. For example, we can save the wedding anniversary if we have a traveling company. That way, we can create a mailing campaign suggesting different places you can travel to celebrate the event.

  • Checkbox: it's a type of field that allows you to create different options that can be selected at the same time. This has to be a required field, and you have to select at least one option to save it. You can use it to create a field regarding interests where the contacts can check different categories. That way, we can use them to create segments and campaigns.

  • Radio: similar to checkbox, since it also allows to create different options. The main difference is that, in this custom field, you can select just one. It is also required by default. It's useful in situations where the possible answer is limited. For example, if we have a video game store, we might be interested in the first game that the contact has played from a particular franchise. In the default value, we can put "Haven't played any of them", and then we create tags for each title. 

  • Boolean: this type of fields are use to create a response to a question that only has two possible answers: a positive and a negative. It's required by default and it's mandatory to mark one of the two options. The default tags are "True" or "False", and can be edited. If we had a travel agency, we could use this boolean field to ask our if the contacts have ever travel abroad.

Built-in Fields 

These are the fields that are created by default in Connectif. They are as follows:

  • Surname: Text field. Allows you to save the surname of a contact.
  • Quantity of soft bounces: Integer type. Keeps track of the amount of temporal bounces from a contact.
  • Total purchases: Integer type. Registers the number of purchases by a contact.
  • Email: Email type. Registers a contact's email. This field is unique in Connectif, which means there can't be two contacts with the same email.
  • Email unknown: Boolean type. Informs if the contact has a known email address or not.
  • Email status: Radio type. Shows which type of email status a contact has: active, bounced, banned or paused. For a contact to receive transactional emails, it has to have an active status. For a contact to receive newsletter type emails, apart from being active, it needs to be subscribed to the newsletter.
  • SMS subscription status: Radio type. Reflects if a contact is subscribed, unsubscribed or not subscribed to SMS messages.
  • Newsletter subscription status: Radio type. Same behavior as the previous SMS subscription status.
  • Mobile phone status: Radio type. Shows you if the phone status is active, bounced or paused.
  • Creation date: Date type. Points out the moment that a contact was created within Connectif's database.
  • Birthdate: Date type. Allows you to store the date of birth of a contact.
  • Update: Date type. Registers the date of the last update in a contact's profile page.
  • Last unsubscribed date: Date type. Lets you know the date of the last time a contact unsubscribed.
  • Last purchase date: Date type. Lets you know the date of the last purchase by a contact.
  • Last bounced date: Date type. It shows when the last bounce from a contact took place.
  • Last soft bounced date: Date type. Same as the previous one, but focused on soft bounces.
  • Last unsubscribed IP: Text type. Shows you the IP of the last time a contact unsubscribed.
  • Name: Text type. Registers a name for each contact.
  • Points: Integer type. Stores the points that a contact has.
  • Bounced reason: Text type. Points out the reason behind a contact's bounce.
  • Mobile phone: Phone type. Allows you to register a mobile phone for a contact.
  • Has push subscriptions: Boolean type. Indicates whether a contact is subscribed to push notifications or not.
  • Tracker: Text type. Unique identifier for a contact. Doesn't matter if it's anonymous or known.

Custom field's cases of use

The main way to obtain the information that the custom fields gather is via forms. These can be implemented via web content's such as "Popup", "Full Screen", "Slide In", Floating Bar" or "Inline".

You can also synchronize the data from the custom fields directly from your site. You'll have to use the tag "cn_client_info". You'll also have to indicate in the ID the same one as the custom field of Connectif.

The main thing we have to do in this case of use is that, when the contact sends the form, Connectif has to be clear about which contact fields get the information provided by the form.

This action is done via two nodes:

  • On form submitted: This is a trigger node in which we select the type of content that the form will appear on.

  • Set attribute: With this workflow, we'll indicate which contact fields will be filled by the form.

Here's an example:



In this workflow, when the contacts that don't have an email visit a page, a popup will appear. This web content will include an "Add". We will ask for an email, name and town. When the form is sent, we will establish "name" and "town" as custom fields within Connectif.

It won't be necessary to associate the email field, since it's a key one that Connectif takes automatically by default.

It's important that the form is of the "Add" type if we want to store the email of the contact. You can set it up in the "Form" section.



Node "On Form Submitted"

In the settings, we can select the form that we just created for the purpose of this case of use. 



Node "Set Attribute"

Here is where we associate the fields from the forms with Connectif's contacts. For that, we'll drag the fields from the "On Form Submitted" section of the left, and drop them in their respective spots.



Now that everything is done, all the data will be stored in the contact's profile thanks to the forms.

Was this article helpful?
1 out of 2 found this helpful