Consent Workflow

The following diagram shows the consent workflow. In the diagram:

• Contact Consent Import Staging__IQ is used during the import process. Its purpose is to allow for batch processing. It shouldn't be read or written to otherwise, and it will be cleared after each import run.
• Contact Consent Log__IQ provides an audit trail for consent processing. It is similar in format to Contact Consent Import__IQ except that Processed Date is included in the Primary Key, meaning that a consent could be processed multiple times with differing results (for example, reprocessing a failed consent import).
• The Preference Center writes updates to consent records directly to the Master DE. This means consent updates made in the Preference Center are visible immediately when the page is refreshed.
• Two-way consent sync ETLs can use the Source field and Updated Date to identify new consents that didn't originate from the source system.