Skip to content
Optima docs
ConsoleIntegrationsData connectors

Collection purposes and clearance

Which consent purposes imported data is stamped with, and what an exporting connector is allowed to send.

Two connector settings carry privacy decisions. Collection purposes (on importing connectors) record why the data was collected. Privacy clearance (on exporting connectors) limits what may leave Optima. Both are on the New connector and Edit connector dialogs of Data connectors.

Needs the integration_editor role, or another role your administrator has given access to this area — see Licences and roles. A privacy officer should review the choices, because they decide which purpose-based erasures and reads apply to the data.

Collection purposes (imports)

Shown for Profiles and Events connectors that are a batch source or a stream source. Tick the consent purposes under which this feed collects its data. Every attribute value the connector imports is stamped with these purposes, as provenance. Later, an erasure or a read that is limited to one purpose can find that data by its stamp.

FieldMeaningValid valuesDefault
Collection purposesThe purposes stamped on imported values.Any active consent purposeNone selected
Lawful basis overrideThe lawful basis stamped on imported rows.Derive from purposes (default), Consent, Legitimate interest, Contract, Legal obligation, Vital interests, Public taskDerive from purposes

An empty selection means undeclared: the imported values carry no purpose. With Derive from purposes, each selected purpose contributes its own lawful basis. Choose an explicit basis only when the whole feed has a single known basis. If no purposes exist, the list says "No active consent purposes defined." Purposes are created under the privacy settings; see consent and purposes.

Privacy clearance (exports)

Shown for batch sinks and stream sinks. It states what this connector may export. Every value passes the same purpose, consent and PII-level checks as an API key with the same clearance: a value needs a purpose listed here and a PII level at or below the level set here. Values with no purpose tag at PII level 0 always pass.

FieldMeaningValid valuesDefault
PurposesThe purposes this connector may export.Active consent purposesNone
PII levelThe highest attribute and identifier PII level it may export.Whole number 0 to 2550

Values the clearance does not cover are left empty or dropped. Saving authorises the clearance in your name, and the Overview tab shows Purposes: … · PII level … and who authorised it. You can grant only purposes and a PII level that you hold yourself.

Examples

Marketing feed to a warehouse. A Profiles batch sink with the purpose marketing and PII level 10 exports the fields tagged marketing up to level 10, and nothing more sensitive.

Newsletter sign-ups from a file. A Profiles batch source with the purpose newsletter and lawful basis override Consent stamps every imported value accordingly.

Common problems

  • "Missing" next to Privacy clearance. No clearance is stored. Until you set one and save, the connector exports only values with no purpose tag and PII level 0. Saving other changes leaves it missing.
  • The filter is refused because of a field. The message names the field and says whether it needs a higher PII level or a purpose the clearance does not list. Raise the level, add the purpose, or change the filter.
  • PII level is rejected. Enter a whole number from 0 to 255.
  • I cannot tick a purpose. You can grant only purposes you hold.

On this page