Impact van het switchen naar één database op het gebruik van de SOAP API
Om je Flexmail account GDPR-proof te maken dien je te switchen naar één database, in plaats van een combinatie van meerdere lijsten. Het gevolg is dat alle contacten en imports in één database worden opgeslagen. Hierbij heb je geen dubbele contacten meer, kan je informatie beter terugvinden over je verschillende contacten en maak je gebruik van dynamische segmenten om meerdere doelgroepen te onderscheiden.
Met behulp van de Contact Converter kan je je account omschakelen naar het gebruiken van één database. Dit heeft ook een impact wanneer je gebruikmaakt van de Flexmail SOAP API. Deze aanpassingen zijn vrij eenvoudig. Hieronder vind je een overzicht met optimalisatietips.
| Service | Change | Tips |
| GetMailingList | Will always return exactly 1 item with list as it’s mailingListType: your database. All other items in the response will be segments. | Store the database ID so that you never have to request it again (it will never change again) |
| CreateMailingList | DEPRECATED Response:
|
Structure your contacts with segments instead of with multiple mailing lists. These segments can be created with the CreateSegment service. |
| DeleteMailingList | DEPRECATED Response:
|
Segments can be deleted with the DeleteSegment service. Deleting a segment does not delete the contacts that are part of it. |
| TruncateMailingList | The mailingListId parameter is no longer mandatory (will default to your database ID) | Segments can not be truncated. Be careful here: know that you’re deleting all contacts in the database. |
| CreateCategory | DEPRECATED Response:
|
Categories no longer can be set up under the “Contacts” tab. Depending on the reason why you would need them, using segments/preferences or a dedicated account for specific communication could be a better fit. |
| CreateEmailAddress | The mailingListId parameter is no longer mandatory (will default to your database ID) | No longer use the mailingListId parameter or use a cached value of the database ID. Prevent making useless calls for GetMailingList as this will have an impact on your monthly limit of available API calls. |
| ImportEmailAddresses | The mailingListId parameter is no longer mandatory (will default to your database ID) | No longer use the mailingListId parameter or use a cached value. Prevent making useless calls for GetMailingList as this will have an impact on your monthly limit of available API calls. |
| EmailAddressTypeItems | The language parameter is now mandatory | While using the service ImportEmailAddresses you can instead provide the parameter defaultLanguage with the call. Supported language values are: nl, fr, en, de, it, es, ru, da, se, zh, pt, pl but are limited to the contact languages you have configured in your account. |
| GetEmailAddresses | If one of the provided mailingListIds is the database ID, all the other ID’s will be ignored | |
| GetBounces | If a mailingListId is provided, the database ID will be used, even if the provided ID is different | Use a cached value for the database ID for the mailingListId parameter. Prevent making useless calls for GetMailingList as this will have an impact on your monthly limit of available API calls. |
| GetSubscriptions | If a mailingListId is provided, the database ID will be used, even if the provided ID is different | Use a cached value for the database ID for the mailingListId parameter. Prevent making useless calls for GetMailingList as this will have an impact on your monthly limit of available api calls. |
| GetUnsubscriptions | If a mailingListId is provided, the database ID will be used, even if the provided ID is different | Use a cached value for the database ID for the mailingListId parameter. Prevent making useless calls for GetMailingList as this will have an impact on your monthly limit of available api calls. |
| GetProfileUpdates | If a mailingListId is provided, the database ID will be used, even if the provided ID is different | Use a cached value for the database ID for the mailingListId parameter. Prevent making useless calls for GetMailingList as this will have an impact on your monthly limit of available api calls. |