Data originality
Imagine a customer receiving the same message again, or worse, twice with different discounts each time. A single instance won’t do much harm, but if this number increases, the campaign may collapse instantly and suffer long-term repercussions, such as a decline in loyalty.

Because of this, data uniqueness needs to be taken care of in your customer database. To do this, you must locate an identifier that enables you to differentiate between two clients. It could be a phone number or an email address. They are not suitable candidates for an identifier even though they are particular to each Tom, Dick, or Harry. First of all, a person’s phone number and email address may change.

Basic sorts of primitives

Boolean: represents true or false values. Consider the attribute “is first time customer,” for instance.
Positive or negative numbers without a decimal point are represented as integers. For instance, integers in Salesforce CRM can have a value as low as -2,147,483,648 or as high as 2,147,483,647.
A number with a decimal point is referred to as a decimal (float), for example, 3.14159.
Characters can be single letters, numerals, or any combination of these (collectively called alphanumeric).
A string, which can be a word, a phrase, or a sentence, saves a string of any alphanumeric letters.
Date is a number that denotes a specific day.
Datetime is a value that designates a specific time and date.
A collection of binary data saved as a single object is referred to as a “blob” (from the binary big object).

There are two general guidelines for both of them:

1) The more freedom you have when it comes to value representation, the less data automation is possible, or, to put it better, the more labour in software is required to handle data. A straightforward illustration would be a US zip code. If it’s a number, we can determine the state using ranges (e.g., Alabama is 35801 through 35816). The string would be unable to accomplish that.

Our survey serves as another excellent illustration. We would need to modify our query to include all the information if we wanted to count iPhone X variants using the open text version.

2) The minimum and maximum values are covered by the second rule. An characteristic is more flexible the larger scale you set it up at. You may be wondering why not always choose the largest choice. because processing data at a larger size requires more computer memory, which is more expensive. When you only have a few hundred entries, it might not even be noticeable, but as you add millions, your CRM instance might become slower to reply or you might reach the limit and need to upgrade to a higher subscription plan.

Takeaways
Visit the documentation for the new CRM you are using to learn more about the data schema. Examine the default objects to discover what you can accomplish right away.