For the complete documentation index, see llms.txt. This page is also available as Markdown.

Layer Hide

Configure dynamic layer visibility with data, direct settings, expressions, and preview states

Use Layer Hide when a layer should appear or disappear based on data, a direct setting, or custom logic. Typical uses include optional badges, conditional messages, alternate layouts, personalization states, and visual elements that should not appear for every viewer.

Studio connector list used to review connector states before opening a specific connector detail panel

Options

Option
What it controls
Notes

Target layer

The layer whose visibility is controlled.

Confirm the connector targets the exact layer, group, or element that should change.

Manual state

A fixed hidden or visible state.

Use when the layer should be disabled without deleting it from the scene.

Data source

A Dynamic Data field, Live Control value, or other supported value.

Boolean values are the clearest source for visibility logic.

Expression

JavaScript that decides whether the layer is hidden.

Use when visibility depends on multiple fields or more complex rules.

Default state

The state used when the source value is missing.

Pick the safer viewer-facing state for incomplete data.

Platform editing

Whether operators can control the visibility value from Platform.

Enable only when business users should decide whether the layer appears.

Internal description

A note explaining the rule or visual state.

Helpful when several optional layers are controlled by data.

Boolean Visibility

When a boolean field drives a Layer Hide connector, define the meaning clearly before connecting it. For example, a field such as hide_discount_badge can use true to hide the badge and false to show it. A field such as show_discount_badge would use the opposite meaning.

Use field names that make the expected state obvious to developers, operators, and QA reviewers.

Configure Dynamic Visibility

1

Select the Layer

Choose the layer that should be hidden or shown based on the connector value.

2

Choose the Control Method

Use a direct hidden state, a Dynamic Data field, a Live Control value, or an expression.

3

Set the Default State

Choose what should happen when the source value is empty, missing, or not included in the preview profile.

4

Preview All States

Test both visible and hidden states, plus any missing-data fallback state.

Success Checks

Before publishing a Layer Hide connector, confirm:

  • The field name clearly communicates the intended true or false behavior.

  • Both visible and hidden states have been previewed.

  • Hiding the layer does not leave broken spacing, empty frames, or conflicting copy.

  • Showing the layer does not overlap other dynamic elements.

  • The default state is acceptable when data is missing.

Data in Studio

Last updated