Why are the selected profiles not compatible with the template?
A situation that can occur when working with our platform is the incompatibility between the selected profiles and the template used when configuring a shipment. In this case, the following message will be displayed:
This is usually due to the presence of a variable or custom field in the selected email piece (newsletter). This means that the content of that field is personalized for each recipient, and the database you are using may not contain that field or may not be written in the same way.
If a field such as "Name" is indicated in the email piece, then in the Profile (database) it must be written in exactly the same way: "Name". It cannot be, for example, "names", since our platform will not consider it as the same field. This issue can also occur if the custom field is not present in one of the selected databases. In this case, all databases must have the custom field in the same shape as indicated in the email piece.
Check newsletter settings: Make sure to check the template and confirm that the names of the custom fields exactly match the fields present in the database. If there is a difference, update the template to match the database.
Check Database: Verifies that all selected databases contain the required custom field. If any database doesn't have that field, add the field or choose an alternative database that does.
Scripting Consistency: Make sure that custom fields in all databases are written the same way, with the same syntax. Even subtle differences in handwriting can result in incompatibility.
This is usually due to the presence of a variable or custom field in the selected email piece (newsletter). This means that the content of that field is personalized for each recipient, and the database you are using may not contain that field or may not be written in the same way.
Example
If a field such as "Name" is indicated in the email piece, then in the Profile (database) it must be written in exactly the same way: "Name". It cannot be, for example, "names", since our platform will not consider it as the same field. This issue can also occur if the custom field is not present in one of the selected databases. In this case, all databases must have the custom field in the same shape as indicated in the email piece.
Check compatibility
Check newsletter settings: Make sure to check the template and confirm that the names of the custom fields exactly match the fields present in the database. If there is a difference, update the template to match the database.
Check Database: Verifies that all selected databases contain the required custom field. If any database doesn't have that field, add the field or choose an alternative database that does.
Scripting Consistency: Make sure that custom fields in all databases are written the same way, with the same syntax. Even subtle differences in handwriting can result in incompatibility.
Updated on: 08/10/2023
Thank you!