Best practices for workspace structure

This guide explains how to organize your workspace structure to best fit your needs.

Introduction

To get the most out of Adverity, you need to establish a strategic and scalable workspace structure. A well-organized workspace is more than just a folder for your data, it is the foundation for efficient workflows, consistent reporting, and effective data governance.

There is no single best structure for everyone, but rather a right one for your specific needs. Choosing the right structure at the outset simplifies crucial processes like managing user permissions, cloning setups for new clients or markets, and monitoring data quality as your operations scale. By aligning your workspace structure with how your teams operate in real life, you can reduce manual work, maintain data integrity, and focus on delivering valuable insights to your stakeholders.

A well-designed workspace structure is a critical foundation for workspace cloning, helping you to consistently replicate the setups for new markets, clients, projects, or business units. This approach streamlines the onboarding of new work, ensuring uniformity and reducing manual setup time. For more information, see Cloning workspaces.

Workspace relationships explained

Within the Adverity workspace hierarchy, understanding the relationship between parent and child workspaces is crucial for efficient data management. This structure helps organizations to centralize common assets at the parent level and distribute them to child workspaces. This approach prevents redundancy and ensures consistency across your data stack.

This section outlines how the objects are shared between parent and child workspaces. By leveraging this feature, you can standardize your Adverity setup, promoting uniformity and saving time on scaling and maintenance.

• From the parent workspace, you can

  use the following child workspace objects:

  • datastreams

  • authorizations

  • destinations

  • transformations

  • mapping tables

  view the following child workspace objects:

  • datastreams

  • authorizations

  • destinations

  • transformations

  • mapping tables

  • value tables

• From the child workspace, you can

  use the following parent workspace objects:

  • datastreams

    For example, you can use a datastream from the parent workspace in a join transformation.

    The datastreams are not shared by default. To use the parent workspace datastreams in child workspaces, enable this setting for the datastreams in the parent workspace. For more information, see Configuring advanced datastream settings.

  • authorizations

  • destinations

  • transformations

  • mapping tables

  The objects in the parent workspace cannot be viewed or configured from the child workspace.

Additionally, mapping tables can be used from the sibling workspaces.

Best practices for data organization in Adverity

Adverity’s flexible workspace structure provides a foundation for both agencies and enterprises to build scalable and resilient reporting systems. By strategically organizing your workspaces, you can streamline workflows, enforce data quality standards, and manage data with greater efficiency. The key is to choose a structure that mirrors your organization’s operations and allows you to grow without increasing manual overhead.

While there is no one-size-fits-all solution, the following are common and effective workspace structures:

By market

For global organizations with local teams, structuring workspaces by market or region is an excellent approach. This ensures local flexibility while maintaining a consistent global data governance policy.

When using this approach, you can customize the warehouse used by your workspaces to comply with regional data residency laws. For more information, see Configuring data warehouses for workspaces.

By client

This is a common setup for agencies that provide individualized reporting for each client. Each client has their own workspace, ensuring data segmentation and clean, client-specific dashboards. This model is ideal for maintaining a high level of security and data isolation.

When using this approach, you can customize the warehouse used by your workspaces to align with specific requirements, for example using a warehouse hosted by the client. For more information, see Configuring data warehouses for workspaces.

By channel or business unit

This structure works best for specialized teams, where each team focuses on a specific marketing channel (e.g., paid social, SEO) or business unit (e.g., e-commerce, retail). This ensures data segmentation and allows each team to focus on its specific data needs.

Hybrid setups

Many organizations find that a hybrid approach, combining elements of the above, is the best fit. For example, a global organization might use a market-based structure, with a business unit or client workspace nested under each market.