Export enrichment
Add stored identifiers, attributes, signals and computed attributes to the profiles a stream sink exports, and trim the rest.
By default a profile export carries the fields that just changed. Export enrichment adds more fields to each exported profile record, and Exported fields (allow-list) trims what is sent. Both are on the Filter tab of a stream sink whose data type is Profiles; see connector detail. Needs the integration_editor role, or another role your administrator has given access to this area — see Licences and roles.
Fields
| Field | Meaning | Valid values | Default |
|---|---|---|---|
| Identifiers | Stored identifiers to add. | Choose fields with Add field…, or All | None |
| Stored attributes | Stored attribute values to add. | Same | None |
| Signals | Signal values to add. | Same | None |
| Computed attributes | Computed attribute values to add. | Same | None |
Enrichment only adds fields. Changed and newly created attributes are always exported, whatever is checked here. Anything checked is looked up for each exported profile, so leave all four empty when you do not need the extra fields, which keeps exports fastest.
Exported fields (allow-list) has the same four groups. A group in which you pick fields keeps only those; groups you leave untouched pass through in full. It is applied after enrichment. If the entity type has nothing defined for a group, the screen says so, for example "No signals defined for this entity type."
The connector's privacy clearance still applies to everything added.
Examples
Send each changed profile with its email and loyalty tier: under Identifiers add email, under Stored attributes add loyalty_tier. Then add email and loyalty_tier to the allow-list groups if nothing else should leave.
Common problems
- The section does not appear. It exists only for stream sinks with the Profiles data type.
- A field is exported empty. The clearance does not cover its purpose or PII level.