The Spotler Connector already supported Purging Contact from Spotler.
We now have added two new operations to replace the Purge Contact operation, the Anonymize Contact and Deactivate Contact operations!
Purge Contact
The Purge Contact operation was created for GDPR (AVG) purposes when Anonymize and Deactivate Contacts through the Spotler API was not yet possible.
This operation purges the contact in Spotler by clearing out all the fields. After this action you are left with a blank record in Spotler, only containing the ExternalId.
The record is still visible and active in Spotler. If needed, you can re-sync the contact to populate it again in Spotler.
Anonymize Contact
The Anonymize Contact operation is new and allows the contact in Spotler to be anonymized. After this action, the contact can’t be found anymore in Spotler. Not be name, email or ExternalId.
The record is not visible anymore.
You can re-sync the contact again to Spotler, but this will create a new record in Spotler.
The Anonymize Contact operation is now automatically executed when you delete a Contact/Lead/Account in Dynamics 365 or PowerApps. This also happens when you make a Contact/Lead/Account inactive (this can be turned off).
Spotler doesn’t like it when you empty an Email address. So, when you make the Email address blank in CRM, we will anonymize the Contact in Spotler.
This helps to keep the system in line with GDPR (AVG) compliance.
Deactivate Contact
The Deactive Contact is also a new operation and allows a Contact to be opt-out of all in Spotler.
This is a dangerous operation because it makes the contact Inactive in Spotler. After this any syncing for this Contact to Spotler is blocked and will not work anymore!
In Dynamics 365 / PowerApps the contact will have the Spotler Status Opt-out.
How to enable it?
When you delete or inactivate contacts in Dynamics 365 / PowerApps then these contacts will be anonymized in Spotler. This already works, you don’t need to do anything.
To use the new Anonymize and Deactivate Contact operations yourself in Dynamics 365 / PowerApps, an update of the solution to version 3.3 or higher is needed to see the new operations. Contact us to help you out with this.
