Skip to content

Commit 09eb066

Browse files
authored
Update documentation to include archiving events
1 parent 14153e2 commit 09eb066

File tree

1 file changed

+9
-0
lines changed

1 file changed

+9
-0
lines changed

src/connections/sources/schema/schema-unique-limits.md

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,16 @@ If you hit any of the limits or would like to clear out old events or properties
2727

2828
Clearing events from the Source Schema only clears them from the Segment interface. It does not impact the data sent to your destinations or warehouses. Once you clear the events, the Schema page starts to repopulate new events.
2929

30+
#### How can I remove specific events from my Source Schema?
31+
You can archive events in order to declutter the Source Schema. This is particularly useful for Protocols customers that want to keep events “Unplanned yet acknowledged” and build a process to monitor for unplanned events. Please note,
32+
Protocols is not required to use this feature. You can also filter your view by “Archived” in addition to Planned and Unplanned.
33+
34+
If a Tracking Plan is connected, events need to be blocked or unplanned in order to archive.
35+
36+
Archiving an event triggers an “Schema Event Archived” activity to the Audit Trail.
37+
3038
#### How can I clear/archive properties in my source schema?
3139

3240
At this time, you cannot clear or archive old event properties individually. An alternative for this is to archive the event itself, and then clear the archive. After you clear the archive, the event will re-populate in the schema with only the current properties.
3341

42+

0 commit comments

Comments
 (0)