The following diagram shows the information flow. The flows with dotted lines mean that this is configured outside of Gigya.
Additional points to consider:
- On the ESP, you should create a custom "Gigya UID" field, and sync Gigya's UID to that field. Gigya's UID should be used as the identifier to support the use case of a user changing their email address. When the UID is used rather than the email, that user will remain identified by the system after the change.
- Whether you are using a simple Gigya data field for describing the user's subscription status, or Communication Preferences, you should update the relevant subscription status (opt in or out) on the target platform.