Hiding is Apsis's way of removing things from the interface without deleting any data. You can hide a whole Section or individual data-model items (Attributes, Tags, Custom Events). Hidden things stop appearing in lists, dropdowns, and editors — but they continue to exist in the database, and any active activities, integrations, and API calls keep functioning.

This is the part of hiding that catches people out, so it deserves a section of its own.

The mechanic is the same in each case — you click an eye icon on the item you want to hide.

Hiding is selective — it removes things from the configuration interface but leaves operational behaviour mostly intact. Here's the detailed breakdown:

Flows that listen for, check, or update hidden Profile data continue to work as before. The flow doesn't break just because the Attribute or Event is hidden from the Data Model interface.

Sendings continue on schedule. If an email contains a Data Tag for a hidden Attribute, the tag still renders the Attribute value at send time — but in the Email Preview, you'll see the Attribute ID instead of its friendly name. Segmentation and tag-based filtering on hidden data still work for already-configured sendings.

Templates and Assets are account-wide (not per Section) and continue to function. Data Tags pointing at hidden Attributes show the Attribute ID in Preview but render the actual value at send time.

Forms keep collecting Profile data. If a Section is hidden, active Forms within it continue to receive submissions and add Profile data — visitors aren't aware the Section was hidden internally.

The Apsis One API is unaffected by hiding. Calls to hidden Sections or hidden Profile data continue to work exactly as before. There is currently no way to restrict the API in a way that hidden sections or profile data is not accessible. Ensure you update the section discriminator in any integration.

Segments containing hidden Profile data keep functioning — the hidden Attribute, Tag, or Event stays in the Segment's conditions. But you cannot add hidden data to new Segment conditions. And critically: if you remove a condition that uses a hidden Attribute, you can't add it back.

If a Profile has data in multiple Sections and you hide one of those Sections, only the data tied to the hidden Section disappears from the Profile view. The Profile itself stays visible, with its data from other Sections intact.

All activities (Marketing Automation flows, scheduled emails, active forms, sent campaigns) belonging to a hidden Section continue to run. Reports stay available. They appear on each tool's Start Page with a hidden icon next to the title.

One subtle gotcha: when working with the File Import Wizard, you cannot apply hidden Tags to Profiles based on a column value when that hidden Tag has already been applied to Profiles before. New Tag values from the column rows will be created and applied as fresh tags.

🚨 Locking Profiles is permanent and blocks future re-subscription

Locking a Profile is a separate (and harsher) operation than hiding. A locked Profile cannot be unlocked, and locking blocks anyone with that email or mobile number from ever opting back in to your communications — even if they want to. Use it only when strictly necessary (e.g. legally mandated suppression). For most "I want to stop talking to this person" cases, an opt-out or unsubscribe is more appropriate.

Locking is mentioned here because it's often confused with hiding — but they're very different. Hiding affects what you see in the platform; locking affects whether a real person can ever subscribe to you again.