Stack Management

Stacks are the core content containers in Tiparra. They hold groups of actions that create interactive digital experiences.

Content Hierarchy

All content in Tiparra is organised into a four-level hierarchy. Understanding this structure is essential for building effective engagement experiences.

  • Stack Groups — The top level of organisation. Stack Groups let you organise related stacks together, making it easier to manage large numbers of stacks. For example, you might have a Stack Group for each season, venue, or campaign.
  • Stacks — The main content unit. Each stack represents a single engagement experience that is presented to users. A stack belongs to a Stack Group and contains one or more Action Groups.
  • Action Groups — Within each stack, Action Groups cluster related actions together. They allow you to section your content logically, such as grouping all media actions separately from engagement actions.
  • Actions — The individual interactive elements that users see and interact with. Actions include polls, quizzes, videos, forms, and many other types. Each action belongs to an Action Group within a stack.

Managing Stack Groups

Stack Groups provide the top-level organisation for your stacks. To manage Stack Groups, navigate to Stack Groups in the sidebar navigation.

From the Stack Groups screen you can:

  • Create a new group — Click the add button and enter a name for the group. The group will be created immediately and you can begin assigning stacks to it.
  • Assign stacks to a group — When creating or editing a stack, select the Stack Group it should belong to. A stack can only belong to one group at a time.
  • Edit a group name — Click on the group name to edit it inline. Changes are saved automatically.

Use Stack Groups to keep your workspace tidy. Organising stacks by event, season, or campaign makes it much easier to find and manage content as your library grows.

Creating a Stack

To create a new stack, navigate to Stack Management and click Add Stack. You will be prompted to fill in the following details:

  • Name — The display name for the stack. This is the primary label users will see.
  • Short Name — A condensed version of the name, used where space is limited.
  • Description — A text description that provides context about the stack and its purpose.
  • Stack Theme / Avatar — Choose a visual theme or upload an avatar image to personalise the stack's appearance.

Once the basic details are saved, you will need to add at least one Action Group containing at least one Action before the stack can be published and made available to users.

Editing a Stack

When you open a stack for editing, the stack editor presents several sections that allow you to configure every aspect of the stack:

  • Stack Info — Edit the stack name, short name, description, and other basic information.
  • Actions — Add new actions, edit existing actions, and reorder actions within their action groups using drag-and-drop. You can also add or remove action groups from this section.
  • Access Controls — Configure who can access the stack and under what conditions. See the Access Controls section below for details.
  • Tile Editor — Customise the visual appearance of the stack tile as it appears in the app. You can adjust images, colours, and layout to match your branding.
  • Delete — Permanently remove the stack and all of its associated action groups and actions. This action cannot be undone.

Stack Access Controls

Access controls allow you to restrict who can view and interact with a stack. The following options are available:

  • App-only access — When enabled, the stack is only accessible through the app. Users accessing via other channels will not see this stack.
  • Authentication requirements — You can require users to be authenticated (signed in) before they can view the stack. Unauthenticated users will be prompted to sign in or create an account.
  • Redirect configuration — Configure a redirect URL for users who do not meet the access requirements. Instead of showing an error, users can be directed to a specified page such as a sign-up flow or informational page.

Combining app-only access with authentication requirements is useful for delivering exclusive content to your most engaged fans.

Duplicating Stacks

To duplicate a stack, navigate to Stack Management and select Duplicate. You will be asked to choose a source stack and a target location (Stack Group). The duplication process creates an identical copy of the stack, including all of its action groups and actions.

Duplicating stacks is useful when you need to create similar experiences across multiple groups or events. Rather than rebuilding a stack from scratch, you can duplicate an existing one and then make targeted modifications to the copy.

Loyalty Points Per View

Stacks can be configured to award loyalty points each time a user views the stack. This feature encourages repeated engagement by rewarding users simply for opening and viewing the content.

To enable this, open the stack editor and set the desired number of loyalty points to award per view. Each time an authenticated user views the stack, the configured number of points will be added to their loyalty balance. This can be combined with other loyalty features such as Fan Offers to build a comprehensive rewards programme.