I have just noticed that transaction emails are recreating a contact that was previously deleted using the GDPR option.
I understand the problem that a transaction email needs to be sent due to the transaction behind it (order confirmation etc).
However, I consider it dangerous and inconsistent that the contact is simply recreated. The contact cannot be created via the traditional API, nor via imports.
In the knowledge database it only says that contacts are created again via a form entry.
Is it really intentional that a transactional email re-creates a contact? I think not. But if it is, it should be documented correctly.
@floeru82 ,
When you create the SMTP token, you have the option to the createContact property to false. When you do this, it should not create a contact.
You should be able to set this in the UI as well per this knowledgebase article
Thank you for this tip. In my case, this may indeed be a possible workaround.
But it is still not consistent:
- I can create contacts via API, but contacts previously deleted using the GDRP option are not created.
- I can create contacts via Imports, but contacts previously deleted using the GDRP option are not created.
So I think it should be possible to create contacts also via SMTP API without creating previously deleted contacts using GDRP option.