ETL segregation
Analytics β Amazon S3 segregates data at the organization, zone, or center level to ensure each S3 bucket contains only the data appropriate for its subscription scope.
Before you begin
- Your organization must have an active Analytics β Amazon S3 subscription.
- You must know your current subscription scope (organization, zone, or center).
How data segregation works
Data segregation is configured during onboarding and determines what data appears in your S3 bucket:
- Organization-level β Your bucket contains data for every center in your organization.
- Zone-level β Your bucket contains data only for centers within the specified zone.
- Center-level β Your bucket contains data only for the specified center.
The pipeline filters data during the S3 Sync stage (Stage 4), splitting the processed warehouse data by organization, zone, or center based on your configuration.
Organization-level reference tables
For zone-level and center-level subscriptions, organization-level dimension tables are replicated into each bucket. These shared reference tables contain configuration data that is defined at the organization level but used across all centers:
Bi_DimAgentβ Agent reference data.Bi_DimCampaignβ Campaign definitions.Bi_DimCategoryProductsβ Product category mappings.Bi_DimCategoryServicesβ Service category mappings.Bi_DimCustomFormsβ Custom form definitions.Bi_DimDiscountβ Discount definitions.Bi_DimDonationsβ Donation type definitions.
This replication ensures that your filtered data can be correctly joined to shared reference records.
Multi-tenant identification
All tables include columns for multi-tenant identification:
PodNameβ Identifies the Zenoti infrastructure pod serving your data.groupidβ Identifies the data load cycle.organizationidβ Identifies your organization (present in fact tables for S3 Data Share).
Changing your segregation scope
Data segregation scope is configured during onboarding and cannot be changed through the Zenoti admin portal. To change your scope β for example, to move from center-level to zone-level, or to add a new zone bucket β contact the Zenoti Implementation team.
Tips
- Start with organization-level scope if you are unsure of your requirements. You can request a scope change later.
- Use zone-level scoping for multi-location businesses that want to separate data by geographic regions or business units.
- Center-level scoping is ideal for franchise models where individual locations need isolated data access.