Skip to main content

ANALYTICS_SHARED

Look up any column in the ANALYTICS_SHARED Snowflake schema. Covers all 12 models with definitions, primary/foreign keys, linked models, datatypes, and model-specific notes on UTC handling.

ANALYTICS_SHARED Data Dictionary

This article documents every model in the ANALYTICS_SHARED schema of our Snowflake data warehouse. Each section below covers one model, with notes at the top followed by a full list of columns, their definitions, datatypes, and any column-specific notes.


Models in this article

  • CUSTOMERS

  • LINE_ITEMS

  • EVENT_REGISTRATIONS

  • LEAGUE_SEASON_REGISTRATIONS

  • MEMBERSHIP_ATTENDANCE

  • MEMBERSHIP_MEMBERS

  • MEMBERSHIP_MEMBERS_DAILY

  • PAYMENT_FAILURES

  • PAYMENT_LINE_ITEMS

  • SESSION_REGISTRATIONS

  • SLOTS

  • USER_IN_FAMILY_ACCOUNT


CUSTOMERS

Our Snowflake data warehouse stores all datetime columns in UTC by default. The only exception is when a column name explicitly includes the word "local" — in that case, it reflects local time. If a date-type column doesn't have "local" in its name, assume it's UTC.

That said, when viewing data through our Sigma reports, these UTC columns are automatically adjusted to display in the organization's local time. So while the underlying data model is stored in UTC, Sigma handles the timezone conversion so that end users see times in their local context.

Column Header

Definition

Key?

Link Model

Datatype

Notes

CUSTOMER_ID

Unique identifier of the customer. Customer: Organization-specific record representing a user's relationship with a particular Organization. The same user can be a customer at multiple organizations.

Primary

NUMBER(38,0)

ORGANIZATION_ID

Unique identifier for the organization the customer is associated with.

Foreign

ORGANIZATIONS

NUMBER(38,0)

ENTITY_ID

Unique identifier for the entity, could represent a user, family account or organization. User: A global Bond account with a unique email that can be associated with multiple organizations.

Foreign

USERS/internal FamilyAccounts table/ORGANIZATIONS

NUMBER(38,0)

ADDRESS_ID

Unique identifier for the customer’s address.

Foreign

ADDRESSES

NUMBER(38,0)

CREATOR_OGANIZATION_ID

The unique identifier for the organization that created the customer. Customer: Organization-specific record representing a user's relationship with a particular Organization. The same user can be a customer at multiple organizations.

Foreign

ORGANIZATIONS

NUMBER(38,0)

USER_ID

Unique identifier for the user. User: A global Bond account with a unique email that can be associated with multiple organizations.

Foreign

USERS

NUMBER(38,0)

CREATOR_USER_ID

User Id of the person who created this record. User: A global Bond account with a unique email that can be associated with multiple organizations.

Foreign

USERS

NUMBER(38,0)

CREATOR_ID

General ID of the creator.

Foreign

USERS/ORGANIZATIONS

NUMBER(38,0)

ENTITY_TYPE

The type/category of the entity.

VARCHAR(1020)

Tells us the table to look at for "Entity Id"

NAME

The full name customer.

VARCHAR(1020)

EMAIL

Email address.

VARCHAR(1020)

PHONE_NUMBER

Contact phone number.

VARCHAR(1020)

CREATOR_TYPE

Type/category of the creator.

VARCHAR(1020)

Tells us the table to look at for "Creator Id"

FIRST_NAME

Customer’s first name.

VARCHAR(256)

LAST_NAME

Customer’s last name.

VARCHAR(256)

WAIVER_SIGNED_DATE

Date the customer signed a waiver.

DATE

BALANCE

Outstanding balance this customer owes (ie. the sum of the amount due on all unpaid, partially paid, and unfinished scheduled payments for invoices)

FLOAT

Dead column

STORED_CREDIT

Customer's credit balance at the organization.

FLOAT

Stored credit is the amount of money a customer has available to use toward future purchases. It’s created when you refund a paid invoice and choose the refund method “Credit balance”.

IMPORTED_ID

"imported Id" is used when we migrate data from other systems into Bond.

No (reference only)

Imported Id is a legacy / external-system reference used for traceability. It is not a foreign key because it identifies records in other systems

VARCHAR(1020)

_CREATED_AT

Timestamp of when the record was first created.

TIMESTAMP_TZ(9)

_UPDATED_AT

Timestamp of when the record was last updated.

TIMESTAMP_TZ(9)

_DELETED_AT

Timestamp of when the record was soft deleted.

TIMESTAMP_TZ(9)

_LOADED_AT

Timestamp of when the record was last loaded into the data warehouse.

TIMESTAMP_TZ(9)


LINE_ITEMS

Our Snowflake data warehouse stores all datetime columns in UTC by default. The only exception is when a column name explicitly includes the word "local" — in that case, it reflects local time. If a date-type column doesn't have "local" in its name, assume it's UTC.

That said, when viewing data through our Sigma reports, these UTC columns are automatically adjusted to display in the organization's local time. So while the underlying data model is stored in UTC, Sigma handles the timezone conversion so that end users see times in their local context.

Column Header

Definition

Key?

Link Model

Datatype

Notes

_DBT_SOURCE_RELATION

_DBT_SOURCE_RELATION — The fully qualified source table reference (database, schema, and model name) that identifies which upstream dbt model the record originated from. Populated automatically by dbt when unioning multiple sources together.

VARCHAR(16777216)

Metadata column that dbt populates automatically to track record lineage.

LINE_ITEM_ID

Unique identifier for the line item.

Primary

NUMBER(38,0)

In LINE_ITEMS, convenience fees are modeled as line items with a long Line Item Id. The columns Type, Product Type, Product Code, and Product Name indicate the fee.

REFERENCE_LINE_ITEM_ID

Unique identifier for a related line item, if applicable.

Foreign (Self-Referencing)

LINE_ITEMS

NUMBER(38,0)

IS_CONVENIENCE_FEE

Whether this line item is a convenience fee.

BOOLEAN

INVOICE_ID

Unique identifier of the invoice containing this line item.

Foreign

INVOICES

NUMBER(38,0)

LINE_CREATED_AT

Date/time when the line item was created.

TIMESTAMP_TZ(9)

INVOICE_CREATED_AT

Date/time when the invoice was created.

TIMESTAMP_TZ(9)

ORGANIZATION_ID

Unique identifier of the organization associated with the line item.

Foreign

ORGANIZATIONS

NUMBER(38,0)

TYPE

Type/category of the line item.

VARCHAR(256)

PRODUCT_TYPE

Broad classification of the product.

VARCHAR(256)

PRODUCT_SUB_TYPE

More specific classification of the product.

VARCHAR(16777216)

PRODUCT_USER_ID

The unique identifier representing the usage of a product, by user.

Foreign

The table is documented internally as ProductsUsers. It represents ownership / entitlement records that link a user to a product they have purchased, and it is the core way the system determines “what does this user own and can they use it?”

NUMBER(38,0)

PRODUCT_ID

Unique identifier of the product.

Foreign

PRODUCTS

NUMBER(38,0)

PROMO_CODE_ID

Unique identifier of the promo code applied to this line item.

Foreign

PROMO_CODES

NUMBER(38,0)

PAYMENT_STATUS

Status of the payment.

VARCHAR(256)

INVOICE_STATUS

Status of the invoice.

VARCHAR(1020)

PRODUCT_IS_PUNCH_CARD

Whether the product is a punch card.

BOOLEAN

PRODUCT_IS_ADD_ON

Whether the product is an add-on to another product.

BOOLEAN

PARTICIPANT_USER_ID

Unique identifier of the user participating in the activity. User: A global Bond account with a unique email that can be associated with multiple organizations.

Foreign

USERS

NUMBER(38,0)

PAYING_USER_ID

Unique identifier of the user who paid for the item. User: A global Bond account with a unique email that can be associated with multiple organizations.

Foreign

USERS

NUMBER(38,0)

PAYING_USER_NAME

Name of the user who paid. User: A global Bond account with a unique email that can be associated with multiple organizations.

VARCHAR(2041)

PAYING_USER_EMAIL

Email of the user who paid. User: A global Bond account with a unique email that can be associated with multiple organizations.

VARCHAR(1020)

PRODUCT_CODE_ID

Unique identifier for the product code.

Foreign

Our data warehouse does not currently have a ProductCodes model. There is an internal "GlCodes" table in our Postgres database, but it has not been modeled into Snowflake.

NUMBER(38,0)

We rename "Product Code" columns — as that is what they are labeled in the data warehouse — to "GL Code" in our reports, as it is the preferred terminology for our customers.

PRODUCT_CODE

Code representing the product.

VARCHAR(256)

We rename "Product Code" columns — as that is what they are labeled in the data warehouse — to "GL Code" in our reports, as it is the preferred terminology for our customers.

PRODUCT_NAME

Name of the product.

VARCHAR(256)

ORGANIZATION_NAME

Name of the organization providing the product.

VARCHAR(1020)

PARENT_ORGANIZATION_NAME

Name of the parent organization (if applicable).

VARCHAR(256)

PARENT_ORGANIZATION_ID

Unique identifier of the parent organization (if applicable).

Foreign

PARENT_ORGANIZATIONS

NUMBER(38,0)

PROMO_CODE

The promo/discount code applied.

VARCHAR(16777216)

PROMO_CODE_DISCOUNT_ON

What the promo code discount applies to.

VARCHAR(16777216)

PROMO_CODE_DISCOUNT_DETAILS

Description/details of the discount.

VARCHAR(16777216)

PROMO_CODE_DISCOUNT_ID

Unique identifier of the applied discount.

Foreign

DISCOUNTS

NUMBER(38,0)

A promo code is a redeemable code that links to a discount and applies that discount’s pricing rules during checkout.

PROGRAM_CODE

Code representing a program. Programs: Private Lesson, League, Camp, Clinic, Class, Club Team.

VARCHAR(16777216)

SESSION_CODE

Code for a specific session within the program. Sessions sit under the program and can be broken down by skill level, season (e.g., Fall, Winter), age group, or other criteria.

VARCHAR(16777216)

SEGMENT_CODE

Code representing a segment. Segments (Optional): Add organization within a session—use to group events (e.g., Mon/Wed vs. Tue/Thu), weekly or monthly registrations, or specific time blocks.

VARCHAR(16777216)

FACILITY_ID

Unique identifier of the facility where the service is provided.

Foreign

FACILITIES

NUMBER(38,0)

FACILITY_NAME

Name of the facility.

VARCHAR(16777216)

FACILITY_CODE

Code representing the facility.

VARCHAR(16777216)

ACTIVITY_CODE

Code for a specific activity.

VARCHAR(16777216)

INVOICE_PAYMENT_STATUS

Payment status of the invoice.

VARCHAR(256)

HAS_FAILED_PAYMENTS

Whether any payment attempts have failed.

BOOLEAN

HAS_PAYMENT_PLAN

Whether there’s a payment plan associated.

BOOLEAN

ADJUSTMENT_REASON

Reason for any adjustment.

VARCHAR(256)

IS_PROMO_CODE_PRIMARY

Indicates whether this is the primary promo code applied.

BOOLEAN

ORIGINAL_QUANTITY

Quantity originally ordered.

FLOAT

NET_QUANTITY

Final quantity.

FLOAT

DISCOUNT_NON_TAX_AMOUNT

Discount amount excluding tax.

NUMBER(38,3)

GROSS_NON_TAX_AMOUNT

Gross amount excluding tax.

NUMBER(38,3)

GROSS_TAX_AMOUNT

Total tax amount before discounts.

NUMBER(38,3)

GROSS_TOTAL_AMOUNT

Gross amount including tax.

NUMBER(38,3)

NON_TAX_AMOUNT

Amount excluding tax.

NUMBER(38,3)

TAX_AMOUNT

Tax amount charged.

NUMBER(38,3)

TOTAL_AMOUNT

Total charged amount including tax.

NUMBER(38,3)

VOID_AMOUNT

Amount voided from the line item.

NUMBER(38,3)

DISCOUNT_AMOUNT

Total discount amount applied.

NUMBER(38,3)

REFUND_AMOUNT

Total refunded amount.

NUMBER(38,3)

ADJUSTMENT_AMOUNT

Amount adjusted.

NUMBER(38,3)

PAYMENT_AMOUNT

Total payment made for the line item.

NUMBER(38,18)

TAX_PAYMENT_AMOUNT

Portion of payment applied to tax.

NUMBER(38,18)

NON_TAX_PAYMENT_AMOUNT

Payment amount excluding tax portion.

NUMBER(38,18)

PAYMENT_AMOUNT_LESS_TRANSACTION_FEE

Payment received after subtracting transaction fees.

NUMBER(38,18)

BALANCE

Remaining balance for the line item.

NUMBER(38,2)

PROMO_CODE_USED_AT

When the promo code was applied.

VARCHAR(16777216)

Dead (Always null).


EVENT_REGISTRATIONS

The event registrations model shows how session registrations break down into events. While users pay for session/segment registrations, they consume the product at the event level. Our Snowflake data warehouse stores all datetime columns in UTC by default. The only exception is when a column name explicitly includes the word "local" — in that case, it reflects local time. If a date-type column doesn't have "local" in its name, assume it's UTC.

That said, when viewing data through our Sigma reports, these UTC columns are automatically adjusted to display in the organization's local time. So while the underlying data model is stored in UTC, Sigma handles the timezone conversion so that end users see times in their local context.

Column Header

Definition

Key?

Link Model

Datatype

Notes

REGISTRATION_KEY

Unique identifier for each registration record.

Primary

NUMBER(38,0)

The event registrations model shows how session registrations break down into events. While users pay for session/segment registrations, they consume the product at the event level.

CREATED_AT

Date/time the registration was created

TIMESTAMP_TZ(9)

INVOICE_ID

Unique identifier of the invoice linked to the registration.

Foreign

INVOICES

NUMBER(38,0)

LINE_ITEM_ID

Unique identifier of the line item on the invoice.

Foreign

LINE_ITEMS

NUMBER(38,0)

ORGANIZATION_ID

Unique identifier of the organization hosting the event.

Foreign

ORGANIZATIONS

NUMBER(38,0)

PRODUCT_USER_ID

The unique identifier representing the usage of a product, by user. User: A global Bond account with a unique email that can be associated with multiple organizations.

Foreign

The table is documented internally as "ProductsUsers". It represents ownership / entitlement records that link a user to a product they have purchased, and it is the core way the system determines “what does this user own and can they use it?”

NUMBER(38,0)

PARTICIPANT_USER_ID

Identifier of the user participating in the activity. User: A global Bond account with a unique email that can be associated with multiple organizations.

Foreign

USERS

NUMBER(38,0)

PAYING_USER_ID

Identifier of the user responsible for payment. User: A global Bond account with a unique email that can be associated with multiple organizations.

Foreign

USERS

NUMBER(38,0)

CUSTOMER_ID

Unique identifier of the customer. Customer: Organization-specific record representing a user's relationship with a particular Organization. The same user can be a customer at multiple organizations.

Foreign

CUSTOMERS

NUMBER(38,0)

PROGRAM_ID

Unique identifier of the program. Programs: Private Lesson, League, Camp, Clinic, Class, Club Team.

Foreign

Our data warehouse does not currently have a Programs model. There is an internal "Programs" table in our Postgres database, but it has not been modeled into Snowflake.

NUMBER(38,0)

SESSION_ID

Unique identifier of the specific session within the program. Sessions sit under the program and can be broken down by skill level, season (e.g., Fall, Winter), age group, or other criteria.

Foreign

Our data warehouse does not currently have a Sessions model. There is an internal "Sessions" table in our Postgres database, but it has not been modeled into Snowflake.

NUMBER(38,0)

SEGMENT_ID

Unique identifier of the segment. Segments (Optional): Add organization within a session—use to group events (e.g., Mon/Wed vs. Tue/Thu), weekly or monthly registrations, or specific time blocks.

Foreign

Our data warehouse does not currently have a Segments model. There is an internal "Segments" table in our Postgres database, but it has not been modeled into Snowflake.

NUMBER(38,0)

PRODUCT_ID

Unique identifier of the product linked to the registration.

Foreign

PRODUCTS

NUMBER(38,0)

FACILITY_ID

Unique identifier of the facility where the event takes place.

Foreign

FACILITIES

NUMBER(38,0)

EVENT_ADDRESS_ID

Unique identifier of the event’s address.

Foreign

ADDRESSES

NUMBER(38,0)

EVENT_ID

Unique identifier of the event.

Foreign

Our data warehouse does not currently have an Events model. There is an internal "Events" table in our Postgres database, but it has not been modeled into Snowflake. Event Id is a foreign key in EVENT_REGISTRATIONS, referencing the primary key of the "Events" table — the primary key of EVENT_REGISTRATIONS is Registration Key.

NUMBER(38,0)

EVENT_NAME

Name of the event.

VARCHAR(1020)

EVENT_START_DATE

Date/time the event starts.

TIMESTAMP_NTZ(9)

EVENT_END_DATE

Date/time the event ends.

TIMESTAMP_NTZ(9)

PARTICIPANTS_LIMIT

This field is non-informative (values are always null or 0) and should be excluded from consideration.

NUMBER(38,0)

REGISTRATION_STATUS

Status of the registration.

VARCHAR(7)

EVENT_ATTENDANCE_STATUS

Attendance status of the participant.

VARCHAR(12)

CHECKED_IN_AT

Date/time the participant checked in.

TIMESTAMP_TZ(9)

IS_PUNCH_PASS

Whether the registration uses a punch pass.

BOOLEAN

PUNCH_PASS_QUANTITY

This is the punch pass quantity at the time of the purchase.

FLOAT

INVOICE_STATUS

Status of the invoice linked to the registration.

VARCHAR(1020)

Only rental products will have invoices with a status of “Draft.”

INVOICE_CREATED_AT

Date/time the invoice was created.

TIMESTAMP_TZ(9)

ORGANIZATION_NAME

Name of the organization hosting the event.

VARCHAR(1020)

PARTICIPANT_FIRST_NAME

First name of the participant.

VARCHAR(1020)

PARTICIPANT_LAST_NAME

Last name of the participant.

VARCHAR(1020)

PARTICIPANT_GENDER

Gender of the participant.

VARCHAR(6)

PARTICIPANT_BIRTH_DATE

Date of birth of the participant.

DATE

PARTICIPANT_AGE

Age of the participant.

NUMBER(6,0)

PARTICIPANT_PHONE_NUMBER

Phone number of the participant.

VARCHAR(1020)

PARTICIPANT_ADDRESS

Street address of the participant.

VARCHAR(3062)

PARTICIPANT_CITY

City of the participant.

VARCHAR(1020)

CUSTOMER_FIRST_NAME

First name of the customer (payer). Customer: Organization-specific record representing a user's relationship with a particular Organization. The same user can be a customer at multiple organizations.

VARCHAR(1020)

CUSTOMER_LAST_NAME

Last name of the customer (payer). Customer: Organization-specific record representing a user's relationship with a particular Organization. The same user can be a customer at multiple organizations.

VARCHAR(1020)

CUSTOMER_EMAIL

Email address of the customer. Customer: Organization-specific record representing a user's relationship with a particular Organization. The same user can be a customer at multiple organizations.

VARCHAR(1020)

PROGRAM_NAME

Name of the program. Programs: Private Lesson, League, Camp, Clinic, Class, Club Team.

VARCHAR(256)

SESSION_NAME

Name of the session under the program. Sessions sit under the program and can be broken down by skill level, season (e.g., Fall, Winter), age group, or other criteria.

VARCHAR(256)

SEGMENT_NAME

Name of the segment under the session. Segments (Optional): Add organization within a session—use to group events (e.g., Mon/Wed vs. Tue/Thu), weekly or monthly registrations, or specific time blocks.

VARCHAR(256)

PRODUCT_NAME

Name of the product.

VARCHAR(256)

PRODUCT_TYPE

Type of product.

VARCHAR(256)

PRODUCT_SUB_TYPE

Subtype of the product.

VARCHAR(256)

ACTIVITY_NAME

Name of the activity linked to the registration.

VARCHAR(256)

dead column (always null).

FACILITY_NAME

Name of the facility.

VARCHAR(1020)

FACILITY_ADDRESS

Address of the facility.

VARCHAR(3062)

FACILITY_CITY

City where the facility is located.

VARCHAR(1020)

FACILITY_STATE

State where the facility is located.

VARCHAR(1020)

PRODUCT_CODE

Code assigned to the product.

VARCHAR(256)

We rename "Product Code" columns — as that is what they are labeled in the data warehouse — to "GL Code" in our reports, as it is the preferred terminology for our customers.

PROGRAM_CODE

Code assigned to the program. Programs: Private Lesson, League, Camp, Clinic, Class, Club Team.

VARCHAR(256)

FACILITY_CODE

Code assigned to the facility.

VARCHAR(256)


LEAGUE_SEASON_REGISTRATIONS

The central model for leagues, the league season registrations model denotes season registrations by player, ties to the relevant invoice, and give metadata about the League, season, and teams. Our Snowflake data warehouse stores all datetime columns in UTC by default. The only exception is when a column name explicitly includes the word "local" — in that case, it reflects local time. If a date-type column doesn't have "local" in its name, assume it's UTC.

That said, when viewing data through our Sigma reports, these UTC columns are automatically adjusted to display in the organization's local time. So while the underlying data model is stored in UTC, Sigma handles the timezone conversion so that end users see times in their local context.

Column Header

Definition

Key?

Link Model

Datatype

Notes

_DBT_SOURCE_RELATION

_DBT_SOURCE_RELATION — The fully qualified source table reference (database, schema, and model name) that identifies which upstream dbt model the record originated from. Populated automatically by dbt when unioning multiple sources together.

VARCHAR(16777216)

Metadata column that dbt populates automatically to track record lineage.

LINE_ITEM_ID

Unique identifier for an individual line item in an invoice.

Foreign

LINE_ITEMS

NUMBER(38,0)

INVOICE_ID

Unique identifier for the related billing record.

Foreign

INVOICES

NUMBER(38,0)

ORGANIZATION_ID

Unique identifier for the organization running the league.

Foreign

ORGANIZATIONS

NUMBER(38,0)

LEAGUE_ID

Unique identifier for the league entity itself.

Foreign

Our data warehouse does not currently have a Leagues model. There is an internal "Leagues" table in our Postgres database, but it has not been modeled into Snowflake.

NUMBER(38,0)

LEAGUE_SEASON_ID

Unique identifier for the specific season of the league.

Foreign

Our data warehouse does not currently have a LeagueSeasons model. There is an internal "LeagueSeasons" table in our Postgres database, but it has not been modeled into Snowflake.

NUMBER(38,0)

QUESTIONNAIRE_ID

Unique identifier linking any registration-related survey or form.

Foreign

Our data warehouse does not currently have a Questionnaires model. There is an internal "Questionnaires" table in our Postgres database, but it has not been modeled into Snowflake.

NUMBER(38,0)

TEAM_ID

Unique identifier for the registered team.

Foreign

Our data warehouse does not currently have a Teams model. There is an internal "Teams" table in our Postgres database, but it has not been modeled into Snowflake.

NUMBER(38,0)

PARTICIPANT_USER_ID

Unique identifier of the user participating. User: A global Bond account with a unique email that can be associated with multiple organizations.

Foreign

USERS

NUMBER(38,0)

PAYING_USER_ID

Unique identifier for the user making the payment. User: A global Bond account with a unique email that can be associated with multiple organizations.

Foreign

USERS

NUMBER(38,0)

FACILITY_ID

Unique identifier of the facility.

Foreign

FACILITIES

NUMBER(38,0)

PARENT_ORGANIZATION_ID

Unique identifier of the parent organization (if applicable).

Foreign

PARENT_ORGANIZATIONS

NUMBER(38,0)

SEASON_NAME

Name of the season.

VARCHAR(1020)

LEAGUE_NAME

Name of the league.

VARCHAR(1020)

TEAM_NAME

Name of the team.

VARCHAR(1020)

FACILITY_NAME

Name of the facility.

VARCHAR(1020)

SIGNED_UP_AT

Timestamp of when registration occurred.

TIMESTAMP_TZ(9)

SEASON_START_DATE

Timestamp of when the season starts.

TIMESTAMP_TZ(9)

SEASON_END_DATE

Timestamp of when the season ends.

TIMESTAMP_TZ(9)

TOTAL_AMOUNT

Total cost charged for the registration.

NUMBER(38,3)

BALANCE

Outstanding amount remaining for payment.

NUMBER(38,2)

PRODUCT_NAME

Name of the product.

VARCHAR(256)

PARTICIPANT_FIRST_NAME

Participant’s first name.

VARCHAR(1020)

PARTICIPANT_LAST_NAME

Participant’s last name.

VARCHAR(1020)

PARTICIPANT_GENDER

Gender of the participant.

VARCHAR(6)

PARTICIPANT_BIRTH_DATE

Participant’s date of birth.

DATE

PARTICIPANT_AGE

Age of the participant.

NUMBER(6,0)

PARTICIPANT_ADDRESS

Participant’s address.

VARCHAR(3062)

PARTICIPANT_CITY

Participant’s city.

VARCHAR(1020)

PARTICIPANT_PHONE_NUMBER

Participant’s phone number.

VARCHAR(1020)

CAPTAIN_EMAIL

Email address of the team captain.

VARCHAR(1020)

CAPTAIN_FIRST_NAME

First name of the team captain.

VARCHAR(1020)

CAPTAIN_LAST_NAME

Last name of the team captain.

VARCHAR(1020)

TEAM_MEMBER_ROLE_NAME

Participant’s role within the team.

VARCHAR(16777216)

ORGANIZATION_NAME

Name of the organization running the league.

VARCHAR(1020)

PARENT_ORGANIZATION_NAME

Name of the parent organization (if applicable).

VARCHAR(256)

USER_ID

Unique identifier for the user. User: A global Bond account with a unique email that can be associated with multiple organizations.

Foreign

USERS

NUMBER(38,0)


MEMBERSHIP_ATTENDANCE

Shows check ins (initiated by a scanning of their Bond ID) at each location and time. Our Snowflake data warehouse stores all datetime columns in UTC by default. The only exception is when a column name explicitly includes the word "local" — in that case, it reflects local time. If a date-type column doesn't have "local" in its name, assume it's UTC.

That said, when viewing data through our Sigma reports, these UTC columns are automatically adjusted to display in the organization's local time. So while the underlying data model is stored in UTC, Sigma handles the timezone conversion so that end users see times in their local context.

Column Header

Definition

Key?

Link Model

Datatype

Notes

ATTENDANCE_ID

Unique identifier of the attendance record.

Foreign

Our data warehouse does not currently have an Attendance model. There is an internal "Attendance" table in our Postgres database, but it has not been modeled into Snowflake.

NUMBER(38,0)

MEMBERSHIP_ID

Unique identifier of the membership linked to the attendance.

Foreign

MEMBERSHIPS

NUMBER(38,0)

PARTICIPANT_USER_ID

Unique identifier of the participant user who attended. User: A global Bond account with a unique email that can be associated with multiple organizations.

Foreign

USERS

NUMBER(38,0)

ORGANIZATION_ID

Unique identifier of the organization.

Foreign

ORGANIZATIONS

NUMBER(38,0)

FACILITY_ID

Unique identifier of the facility where attendance was recorded.

Foreign

FACILITIES

NUMBER(38,0)

MEMBERSHIP_NAME

Name of the membership associated with the attendance.

VARCHAR(256)

MEMBERSHIP_TYPE

Type of membership.

VARCHAR(256)

CHECKED_IN_AT

Date/time of when the member checked in.

TIMESTAMP_TZ(9)

ORGANIZATION_NAME

Name of the organization.

VARCHAR(1020)


MEMBERSHIP_MEMBERS

High level view of current membership information including renewals, sign ups, cancellations, and expirations. Use the Range Start/End to see what member is active during what time period. Our Snowflake data warehouse stores all datetime columns in UTC by default. The only exception is when a column name explicitly includes the word "local" — in that case, it reflects local time. If a date-type column doesn't have "local" in its name, assume it's UTC.

That said, when viewing data through our Sigma reports, these UTC columns are automatically adjusted to display in the organization's local time. So while the underlying data model is stored in UTC, Sigma handles the timezone conversion so that end users see times in their local context. NOTE: Range Start/End - no timezone, Pause Start/End dates - no timezone.If you try to sign up for a membership at 8PM in LA on 3/25, our system will actually block you from doing so, as 3/25 will be considered in the past. You would have to select 3/26 as the start date. So, our system does not log a timestamp for sign up, but it is effectively gated by a UTC timezone.

Column Header

Definition

Key?

Link Model

Datatype

Notes

MEMBERSHIP_MEMBER_ID

Unique identifier of the membership member.

Primary

NUMBER(38,0)

MEMBERSHIP_ID

Unique identifier of the membership.

Foreign

MEMBERSHIPS

NUMBER(38,0)

INVOICE_ID

Identifier of the invoice linked to the membership.

Foreign

INVOICES

NUMBER(38,0)

PARTICIPANT_USER_ID

Identifier of the participant user. User: A global Bond account with a unique email that can be associated with multiple organizations.

Foreign

USERS

NUMBER(38,0)

PAYING_USER_ID

Identifier of the paying user. User: A global Bond account with a unique email that can be associated with multiple organizations.

Foreign

USERS

NUMBER(38,0)

ORGANIZATION_ID

Unique identifier of the organization linked to the membership.

Foreign

ORGANIZATIONS

NUMBER(38,0)

MEMBERSHIP_STATUS

Status of the membership.

VARCHAR(16777216)

RENEWAL_STATUS

Renewal status of the membership.

VARCHAR(16777216)

RANGE_START

Date of the membership range starting.

DATE

RANGE_END

Date of the membership range ending.

DATE

MEMBERSHIP_TYPE

Type of membership.

VARCHAR(256)

MEMBERSHIP_NAME

Name of the membership.

VARCHAR(256)

MEMBERSHIP_SIGNED_UP_AT

The date/time of sign-up.

TIMESTAMP_NTZ(9)

MEMBERSHIP_START_DATE

Date/time of the membership starting.

DATE

MEMBERSHIP_END_DATE

Date/time of the membership ending.

DATE

MEMBERSHIP_EXPIRATION_DATE

Date/time of the membership expiration.

DATE

MEMBERSHIP_CANCELLED_AT

Date/time of when the membership was canceled.

TIMESTAMP_NTZ(9)

MEMBERSHIP_CANCELLATION_STATUS

Status of the membership cancellation.

VARCHAR(256)

MEMBERSHIP_PAUSE_START_DATE

Date/time of the membership pause starting.

TIMESTAMP_TZ(9)

MEMBERSHIP_PAUSE_END_DATE

Date/time of the membership pause ending.

TIMESTAMP_TZ(9)

MEMBERSHIP_DURATION

Duration of the membership.

VARCHAR(7)

MEMBERSHIP_RENEWAL_DATE

Date/time of the membership renewal.

DATE

MEMBER_NAME

Name of the member.

VARCHAR(513)

MEMBER_EMAIL

Email of the member.

VARCHAR(1020)

MEMBER_DATE_OF_BIRTH

The member’s date of birth.

DATE

MEMBER_AGE

Age of the member.

NUMBER(6,0)

MEMBER_GENDER

Gender of the member.

VARCHAR(6)

CUSTOMER_NAME

Name of the customer. Customer: Organization-specific record representing a user's relationship with a particular Organization. The same user can be a customer at multiple organizations.

VARCHAR(513)

CUSTOMER_EMAIL

Email of the customer. Customer: Organization-specific record representing a user's relationship with a particular Organization. The same user can be a customer at multiple organizations.

VARCHAR(1020)

CURRENT_RENEWAL_STATUS

Current renewal status of the membership.

VARCHAR(16777216)

CURRENT_MEMBERSHIP_STATUS

Current status of the membership.

VARCHAR(16777216)

ORGANIZATION_NAME

Name of the organization.

VARCHAR(1020)

PARENT_ORGANIZATION_NAME

Name of the parent organization (if applicable).

VARCHAR(256)

PRODUCT_NAME

Name of the product linked to the membership.

VARCHAR(256)

PRODUCT_TYPE

Type of product linked to the membership.

VARCHAR(256)

The last [MEMBERSHIP_MEMBERS/Range Start] value, where [MEMBERSHIP_MEMBERS/Product Type] = 'package' is 2024-12-30 00:00:00. Other than that, this column always has a value of 'membership'

PRODUCT_CODE

Code of the product linked to the membership.

VARCHAR(256)

We rename "Product Code" columns — as that is what they are labeled in the data warehouse — to "GL Code" in our reports, as it is the preferred terminology for our customers.


MEMBERSHIP_MEMBERS_DAILY

Shows Member information trended against dates. Reporting date can be used to view data "as of". Our Snowflake data warehouse stores all datetime columns in UTC by default. The only exception is when a column name explicitly includes the word "local" — in that case, it reflects local time. If a date-type column doesn't have "local" in its name, assume it's UTC.

That said, when viewing data through our Sigma reports, these UTC columns are automatically adjusted to display in the organization's local time. So while the underlying data model is stored in UTC, Sigma handles the timezone conversion so that end users see times in their local context.

Column Header

Definition

Key?

Link Model

Datatype

Notes

REPORTING_DATE

Date/time the report was generated.

DATE

MEMBERSHIP_ID

Unique identifier of the membership.

Foreign

MEMBERSHIPS

NUMBER(38,0)

MEMBERSHIP_MEMBER_ID

Unique identifier of the membership member.

Foreign

MEMBERSHIP_MEMBERS

NUMBER(38,0)

MEMBERSHIP_STATUS

Status of the membership.

VARCHAR(16777216)

RENEWAL_STATUS

Renewal status of the membership.

VARCHAR(16777216)

INVOICE_ID

Unique identifier for the invoice.

Foreign

INVOICES

NUMBER(38,0)

PARTICIPANT_USER_ID

Identifier of the participant user. User: A global Bond account with a unique email that can be associated with multiple organizations.

Foreign

USERS

NUMBER(38,0)

PAYING_USER_ID

Unique identifier of the user responsible for payment. User: A global Bond account with a unique email that can be associated with multiple organizations.

Foreign

USERS

NUMBER(38,0)

ORGANIZATION_ID

Unique identifier of the organization.

Foreign

ORGANIZATIONS

NUMBER(38,0)

MEMBERSHIP_TYPE

Type of membership.

VARCHAR(256)

MEMBERSHIP_NAME

Name of the membership associated with the attendance.

VARCHAR(256)

MEMBERSHIP_SIGNED_UP_AT

Date/time of sign-up.

TIMESTAMP_NTZ(9)

MEMBERSHIP_START_DATE

Date/time of the membership start.

DATE

MEMBERSHIP_END_DATE

Date/time of the membership end.

DATE

MEMBERSHIP_EXPIRATION_DATE

Date/time of the membership expiration.

DATE

MEMBERSHIP_CANCELLED_AT

Date/time of the membership cancellation.

TIMESTAMP_NTZ(9)

MEMBERSHIP_CANCELLATION_STATUS

Status of the membership cancellation.

VARCHAR(256)

MEMBERSHIP_PAUSE_START_DATE

Date/time of the membership pause start.

TIMESTAMP_TZ(9)

MEMBERSHIP_PAUSE_END_DATE

Date/time of the membership pause end.

TIMESTAMP_TZ(9)

MEMBERSHIP_DURATION

The length of the membership.

VARCHAR(7)

MEMBERSHIP_RENEWAL_DATE

Date/time of when the membership is scheduled to renew.

DATE

MEMBER_NAME

Full name of the member associated with the membership.

VARCHAR(513)

MEMBER_EMAIL

Email address of the member.

VARCHAR(1020)

MEMBER_DATE_OF_BIRTH

Member’s date of birth.

DATE

MEMBER_AGE

Age of the member.

NUMBER(6,0)

MEMBER_GENDER

Gender of the member.

VARCHAR(6)

CUSTOMER_NAME

Name of the customer. Customer: Organization-specific record representing a user's relationship with a particular Organization. The same user can be a customer at multiple organizations.

VARCHAR(513)

CUSTOMER_EMAIL

Email address of the customer. Customer: Organization-specific record representing a user's relationship with a particular Organization. The same user can be a customer at multiple organizations.

VARCHAR(1020)

ORGANIZATION_NAME

The name of the organization where the membership is active.

VARCHAR(1020)

PARENT_ORGANIZATION_NAME

If applicable, the larger parent organization tied to the sub-organization.

VARCHAR(256)

PRODUCT_NAME

Name of the product.

VARCHAR(256)

PRODUCT_TYPE

The type or category of product.

VARCHAR(256)

PRODUCT_CODE

The code assigned to the product.

VARCHAR(256)

We rename "Product Code" columns — as that is what they are labeled in the data warehouse — to "GL Code" in our reports, as it is the preferred terminology for our customers.


PAYMENT_FAILURES

Our Snowflake data warehouse stores all datetime columns in UTC by default. The only exception is when a column name explicitly includes the word "local" — in that case, it reflects local time. If a date-type column doesn't have "local" in its name, assume it's UTC.

That said, when viewing data through our Sigma reports, these UTC columns are automatically adjusted to display in the organization's local time. So while the underlying data model is stored in UTC, Sigma handles the timezone conversion so that end users see times in their local context.

Column Header

Definition

Key?

Link Model

Datatype

Notes

PAYMENT_FAILURE_ID

Unique identifier for the failed payment attempt.

Primary

NUMBER(38,0)

PAYMENT_ID

Unique identifier for the associated payment record.

Foreign

PAYMENTS

NUMBER(38,0)

INVOICE_ID

Unique identifier for the invoice tied to the payment attempt.

Foreign

INVOICES

NUMBER(38,0)

ORGANIZATION_ID

Unique identifier for the organization associated with the payment attempt.

Foreign

ORGANIZATIONS

NUMBER(38,0)

CUSTOMER_NAME

Full name of the customer linked to the failed payment. Customer: Organization-specific record representing a user's relationship with a particular Organization. The same user can be a customer at multiple organizations.

VARCHAR(2041)

PAYMENT_TYPE

Method of payment attempted.

VARCHAR(256)

CREDIT_CARD_LAST_4

The last four digits of the credit card used in the payment attempt.

VARCHAR(256)

PAYMENT_FAILURE_DATE

The date the payment failure occurred.

DATE

PAYMENT_FAILURE_TIME

The time the payment failure occurred.

TIME(9)

PAYMENT_FAILURE_ERROR_MESSAGE

The specific error message returned by the payment processor.

VARCHAR(512)

ORGANIZATION_NAME

Name of the organization associated with the failed payment.

VARCHAR(1020)


PAYMENT_LINE_ITEMS

Our Snowflake data warehouse stores all datetime columns in UTC by default. The only exception is when a column name explicitly includes the word "local" — in that case, it reflects local time. If a date-type column doesn't have "local" in its name, assume it's UTC.

That said, when viewing data through our Sigma reports, these UTC columns are automatically adjusted to display in the organization's local time. So while the underlying data model is stored in UTC, Sigma handles the timezone conversion so that end users see times in their local context.

Column Header

Definition

Key?

Link Model

Datatype

Notes

_DBT_SOURCE_RELATION

_DBT_SOURCE_RELATION — The fully qualified source table reference (database, schema, and model name) that identifies which upstream dbt model the record originated from. Populated automatically by dbt when unioning multiple sources together.

VARCHAR(16777216)

Metadata column that dbt populates automatically to track record lineage.

LINE_ITEM_ID

The unique identifier for a line item.

Foreign

LINE_ITEMS

NUMBER(38,0)

REFERENCE_LINE_ITEM_ID

Unique identifier for a related line item, if applicable.

Foreign

LINE_ITEMS

NUMBER(38,0)

IS_CONVENIENCE_FEE

Whether this line item is a convenience fee.

BOOLEAN

In LINE_ITEMS, convenience fees are modeled as line items with a long Line Item Id. The columns Type, Product Type, Product Code, and Product Name indicate the fee.

PAYMENT_ID

Unique identifier for the payment transaction.

Foreign

PAYMENTS

NUMBER(38,0)

INVOICE_ID

Unique identifier for the invoice associated with the payment.

Foreign

INVOICES

NUMBER(38,0)

ORGANIZATION_ID

Unique identifier for the organization receiving the payment.

Foreign

ORGANIZATIONS

NUMBER(38,0)

FACILITY_ID

Unique identifier for the facility where the service/product is offered.

Foreign

FACILITIES

NUMBER(38,0)

PRODUCT_ID

Unique identifier for the product purchased.

Foreign

PRODUCTS

NUMBER(38,0)

PRODUCT_USER_ID

The Unique identifier representing the usage of a product, by user.

Foreign

The table is documented internally as ProductsUsers. It represents ownership / entitlement records that link a user to a product they have purchased, and it is the core way the system determines “what does this user own and can they use it?”

NUMBER(38,0)

PARTICIPANT_USER_ID

Unique identifier of the user participating in the activity. User: A global Bond account with a unique email that can be associated with multiple organizations.

Foreign

USERS

NUMBER(38,0)

PROMO_CODE_ID

Unique identifier for a promo code applied to this line item.

Foreign

PROMO_CODES

NUMBER(38,0)

PROMO_CODE_DISCOUNT_ID

Unique identifier for a discount linked to the promo code.

Foreign

DISCOUNTS

NUMBER(38,0)

PROMO_CODE

Promotional code applied to the purchase.

VARCHAR(16777216)

PROMO_CODE_DISCOUNT_ON

What the promo code discount applies to.

VARCHAR(256)

PROMO_CODE_DISCOUNT_DETAILS

Details of the promo code discount.

VARCHAR(1020)

ADJUSTMENT_REASON

Reason for any adjustment (e.g., Employee discount, Void Balance).

VARCHAR(256)

IS_PROMO_CODE_PRIMARY

Indicates whether this is the primary promo code applied.

BOOLEAN

PAYING_USER_ID

Unique identifier of the user making the payment. User: A global Bond account with a unique email that can be associated with multiple organizations.

Foreign

USERS

NUMBER(38,0)

PAYOUT_ARRIVAL_DATE

Date of the payout arrival.

TIMESTAMP_NTZ(9)

TAX_PAYMENT_AMOUNT

Portion of the payment that represents taxes.

NUMBER(38,3)

NON_TAX_PAYMENT_AMOUNT

Payment amount excluding taxes.

NUMBER(38,3)

PAYMENT_AMOUNT

Total amount of the payment.

NUMBER(38,3)

TRANSACTION_FEE

Fee charged by the payment processor for this transaction.

NUMBER(38,3)

PAYMENT_AMOUNT_LESS_TRANSACTION_FEE

Net payment amount after transaction fees are subtracted.

NUMBER(38,3)

PAYMENT_METHOD

The method used to complete a transaction.

VARCHAR(267)

PAYOUT_ID

Unique identifier for the payout batch containing this payment.

Foreign

Links to Stripe Tables

VARCHAR(16777216)

STRIPE_AMOUNT_PAID

Total amount processed through Stripe.

FLOAT

STRIPE_FEE

Fee charged by Stripe for processing the payment.

FLOAT

STRIPE_NET

Net amount after Stripe's fees are deducted.

FLOAT

BOND_AMOUNT_PAID

Total amount processed through Bond.

NUMBER(38,13)

BOND_FEE

Fee charged by Bond for processing the payment.

FLOAT

BOND_NET

Net amount after Bond's fees are deducted.

FLOAT

AMOUNT_IN_TRANSIT

Funds that have been paid but are not yet settled.

FLOAT

DIFF_AMOUNT_PAID

Difference between expected and actual amount paid.

FLOAT

DIFF_TRANSACTION_FEE

Difference between expected and actual transaction fee.

FLOAT

DIFF_NET

Difference between expected and actual net payment.

FLOAT

PAYMENT_NUMBER

Internal ID (system reference).

NUMBER(18,0)

REAL_PAYMENT_NUMBER

Internal ID (system reference).

NUMBER(13,0)

PRECEDING_REAL_PAYMENT_COUNT

Internal ID (system reference).

NUMBER(13,0)

PAYMENT_NOTES

Notes related to the payment.

VARCHAR(16777216)

PAYMENT_METHOD_INFO

Last 4 digits on card, or check number given at time of purchase.

VARCHAR(256)

SUB_PAYMENT_METHOD

Debit or credit, etc

VARCHAR(256)

CREDIT_CARD_BRAND

Brand of the credit card used for the payment.

VARCHAR(256)

CURRENCY

Currency code for the payment.

VARCHAR(256)

PAYMENT_STATUS

Current status of the payment.

VARCHAR(256)

PRODUCT_CODE

The code assigned to the product.

VARCHAR(256)

We rename "Product Code" columns — as that is what they are labeled in the data warehouse — to "GL Code" in our reports, as it is the preferred terminology for our customers.

PAYING_USER_EMAIL

Email address of the paying user. User: A global Bond account with a unique email that can be associated with multiple organizations.

VARCHAR(1020)

PAYING_USER_NAME

Name of the paying user. User: A global Bond account with a unique email that can be associated with multiple organizations.

VARCHAR(2041)

ORGANIZATION_NAME

Name of the organization receiving the payment.

VARCHAR(1020)

PARENT_ORGANIZATION_ID

Unique identifier of the parent organization (if applicable).

Foreign

PARENT_ORGANIZATIONS

NUMBER(38,0)

PARENT_ORGANIZATION_NAME

Name of the parent organization (if applicable).

VARCHAR(256)

FACILITY_NAME

Name of the facility providing the product/service.

VARCHAR(16777216)

PROGRAM_CODE

Code identifying the program linked to the product.

VARCHAR(16777216)

INVOICE_PAYMENT_STATUS

Status of the payment for the invoice.

VARCHAR(16777216)

INVOICE_STATUS

Current status of the invoice.

VARCHAR(1020)

SESSION_CODE

Code for a specific session within the program. Sessions sit under the program and can be broken down by skill level, season (e.g., Fall, Winter), age group, or other criteria.

VARCHAR(16777216)

PRODUCT_NAME

Name of the product purchased.

VARCHAR(16777216)

PRODUCT_TYPE

Type or category of the product.

VARCHAR(16777216)

SEGMENT_CODE

Code representing a segment. Segments (Optional): Add organization within a session—use to group events (e.g., Mon/Wed vs. Tue/Thu), weekly or monthly registrations, or specific time blocks.

VARCHAR(16777216)

ACTIVITY_CODE

Code for a specific activity.

VARCHAR(16777216)

FACILITY_CODE

Code identifying the facility.

VARCHAR(16777216)

PAYMENT_CREATED_AT

Date/time of when the payment record was created.

TIMESTAMP_TZ(9)

INVOICE_CREATED_AT

Date/time of when the invoice record was created.

TIMESTAMP_TZ(9)

LINE_CREATED_AT

Date/time of when the line item record was created.

TIMESTAMP_TZ(9)

GROSS_NON_TAX_AMOUNT

Total amount before taxes are applied.

NUMBER(38,3)

TOTAL_AMOUNT

Total billed amount including taxes and fees.

NUMBER(38,3)


SESSION_REGISTRATIONS

The core model for programming, the session registrations model denotes session and segment registrations by user, ties to the relevant invoice, and gives metadata about the programs and sessions. Our Snowflake data warehouse stores all datetime columns in UTC by default. The only exception is when a column name explicitly includes the word "local" — in that case, it reflects local time. If a date-type column doesn't have "local" in its name, assume it's UTC.

That said, when viewing data through our Sigma reports, these UTC columns are automatically adjusted to display in the organization's local time. So while the underlying data model is stored in UTC, Sigma handles the timezone conversion so that end users see times in their local context.

Column Header

Definition

Key?

Link Model

Datatype

Notes

REGISTRATION_KEY

Unique identifier for each registration record (see Notes columns).

Primary

VARCHAR(16777216)

A compound key that uniquely identifies a session registration record, constructed as either a combination of a Segment ID and a Season Attendee ID (e.g., seg_{segment_id}_sa_{season_attendee_id}) for segment-based registrations, or a combination of a Session ID and a Line Item ID (e.g., ses_{session_id}_li_{line_item_id}) for session-based registrations.

REGISTRATION_STATUS

Status of registration.

VARCHAR(7)

INVOICE_ID

Unique identifier of the invoice.

Foreign

INVOICES

NUMBER(38,0)

LINE_ITEM_ID

Unique identifier of the specific line item on the invoice.

Foreign

LINE_ITEMS

NUMBER(38,0)

ORGANIZATION_ID

Unique identifier of the organization.

Foreign

ORGANIZATIONS

NUMBER(38,0)

PARTICIPANT_USER_ID

Unique identifier of the user participating. User: A global Bond account with a unique email that can be associated with multiple organizations.

Foreign

USERS

NUMBER(38,0)

PAYING_USER_ID

Unique identifier of the user responsible for payment. User: A global Bond account with a unique email that can be associated with multiple organizations.

Foreign

USERS

NUMBER(38,0)

CUSTOMER_ID

Unique identifier of the customer. Customer: Organization-specific record representing a user's relationship with a particular Organization. The same user can be a customer at multiple organizations.

Foreign

CUSTOMERS

NUMBER(38,0)

PROGRAM_ID

Unique identifier of the program. Programs: Private Lesson, League, Camp, Clinic, Class, Club Team.

Foreign

Our data warehouse does not currently have a Programs model. There is an internal "Programs" table in our Postgres database, but it has not been modeled into Snowflake.

NUMBER(38,0)

SESSION_ID

Unique identifier of the session. Sessions sit under the program and can be broken down by skill level, season (e.g., Fall, Winter), age group, or other criteria.

Foreign

Our data warehouse does not currently have a Sessions model. There is an internal "Sessions" table in our Postgres database, but it has not been modeled into Snowflake.

NUMBER(38,0)

SEGMENT_ID

Unique identifier of the segment. Segments (Optional): Add organization within a session—use to group events (e.g., Mon/Wed vs. Tue/Thu), weekly or monthly registrations, or specific time blocks.

Foreign

Our data warehouse does not currently have a Segments model. There is an internal "Segments" table in our Postgres database, but it has not been modeled into Snowflake.

NUMBER(38,0)

PRODUCT_ID

Unique identifier of the product.

Foreign

PRODUCTS

NUMBER(38,0)

FACILITY_ID

Unique identifier of the facility.

Foreign

FACILITIES

NUMBER(38,0)

PRODUCT_CODE_ID

Unique identifier of the product code.

Foreign

Our data warehouse does not currently have a ProductCodes model. There is an internal "GlCodes" table in our Postgres database, but it has not been modeled into Snowflake.

NUMBER(38,0)

We rename "Product Code" columns — as that is what they are labeled in the data warehouse — to "GL Code" in our reports, as it is the preferred terminology for our customers.

PROGRAM_CODE_ID

Internal system code ID for the program. Programs: Private Lesson, League, Camp, Clinic, Class, Club Team.

Foreign

Our data warehouse does not currently have a ProgramCodes model. There is an internal "ProgramCodes" table in our Postgres database, but it has not been modeled into Snowflake.

NUMBER(38,0)

FACILITY_CODE_ID

Unique identifier for the facility code.

Foreign

Our data warehouse does not currently have a ProgramCodes model. There is an internal "FacilityCodes" table in our Postgres database, but it has not been modeled into Snowflake.

NUMBER(38,0)

REGISTERED_AT

Date/Time of when the registration was made.

TIMESTAMP_TZ(9)

SESSION_START_DATE

Date of the session starting. Sessions sit under the program and can be broken down by skill level, season (e.g., Fall, Winter), age group, or other criteria.

DATE

SESSION_END_DATE

Date of the session ending. Sessions sit under the program and can be broken down by skill level, season (e.g., Fall, Winter), age group, or other criteria.

DATE

MAX_PARTICIPANTS

Maximum participants allowed.

NUMBER(38,0)

MAX_MALE_PARTICIPANTS

Maximum male participants allowed.

NUMBER(38,0)

MAX_FEMALE_PARTICIPANTS

Maximum female participants allowed.

NUMBER(38,0)

PRICE

Price charged.

NUMBER(10,3)

AMOUNT_PAID

Amount paid towards the invoice.

NUMBER(10,3)

BALANCE

Remaining balance on the invoice.

NUMBER(10,3)

PAYMENT_PLAN_BALANCE

Outstanding payment plan balance.

NUMBER(10,3)

MIN_AGE_YEARS

Minimum age allowed to participate (in years).

NUMBER(16,8)

MAX_AGE_YEARS

Maximum age allowed to participate (in years).

NUMBER(16,8)

ACTIVITY_NAME

Name of the activity linked to the session.

VARCHAR(256)

PROGRAM_NAME

Name of the program. Programs: Private Lesson, League, Camp, Clinic, Class, Club Team.

VARCHAR(256)

SESSION_NAME

Name of the session. Sessions sit under the program and can be broken down by skill level, season (e.g., Fall, Winter), age group, or other criteria.

VARCHAR(256)

SEGMENT_NAME

Name of the segment. Segments (Optional): Add organization within a session—use to group events (e.g., Mon/Wed vs. Tue/Thu), weekly or monthly registrations, or specific time blocks.

VARCHAR(256)

PRODUCT_CODE

The code assigned to the product.

VARCHAR(256)

We rename "Product Code" columns — as that is what they are labeled in the data warehouse — to "GL Code" in our reports, as it is the preferred terminology for our customers.

SESSION_CODE

Code for the session.

VARCHAR(256)

PROGRAM_CODE

Code for the program. Programs: Private Lesson, League, Camp, Clinic, Class, Club Team.

VARCHAR(256)

FACILITY_CODE

Code for the facility.

VARCHAR(256)

INVOICE_STATUS

Status of the invoice.

VARCHAR(1020)

INVOICE_CREATED_AT

Date/time of when the invoice record was created.

TIMESTAMP_TZ(9)


SLOTS

Note, Programs break down into events, which when tied to a physical space, get entered into the calendar and become "Slots". For that reason, the Slots table contains both programming slots, and "reservation" (rental) slots. For programming, the price is determined up top down (via the registration), breaking into events and slots. For rentals, it's the opposite - rentals are composed of slots and can be grouped together into invoices. Because of this, when slots are associated with a Rental, you'll see the specific price of the slot. When they are associated with a program, slots will not show the value of the slot because it's dynamic based on the number of registrations the session might have. Our Snowflake data warehouse stores all datetime columns in UTC by default. The only exception is when a column name explicitly includes the word "local" — in that case, it reflects local time. If a date-type column doesn't have "local" in its name, assume it's UTC. That said, when viewing data through our Sigma reports, these UTC columns are automatically adjusted to display in the organization's local time. So while the underlying data model is stored in UTC, Sigma handles the timezone conversion so that end users see times in their local context.

Column Header

Definition

Key?

Link Model

Datatype

Notes

SLOT_ID

Unique identifier of the slot. Slots represent distinct events or times (e.g., daily rental times across a week).

Primary

NUMBER(38,0)

SPACE_ID

Unique identifier for the space (e.g., specific courts, fields).

Foreign

Our data warehouse does not currently have a Spaces model. There is an internal "Spaces" table in our Postgres database, but it has not been modeled into Snowflake.

NUMBER(38,0)

ORGANIZATION_ID

Unique identifier of the organization.

Foreign

ORGANIZATIONS

NUMBER(38,0)

PARENT_ORGANIZATION_ID

Unique identifier of the parent organization (if applicable).

Foreign

PARENT_ORGANIZATIONS

NUMBER(38,0)

SLOT_TYPE

Classification of the slot.

VARCHAR(256)

EVENT_ID

Unique identifier of the event.

Foreign

Our data warehouse does not currently have an Events model. There is an internal "Events" table in our Postgres database, but it has not been modeled into Snowflake. Event Id is a foreign key in EVENT_REGISTRATIONS, referencing the primary key of the "Events" table — the primary key of EVENT_REGISTRATIONS is Registration Key.

NUMBER(38,0)

RENTAL_SEGMENT_ID

Unique identifier of a segment within a rental program or schedule.

Foreign

Our data warehouse does not currently have a Segments model. There is an internal "Segments" table in our Postgres database, but it has not been modeled into Snowflake.

NUMBER(38,0)

EVENT_PARENT_TYPE

Category of the parent entity that owns the event.

VARCHAR(1020)

Tells us the table to look at for "Event Parent Id"

EVENT_PARENT_ID

Unique identifier of the parent entity that owns the event.

Foreign

ProgramSeasons,Teams,Reservations

NUMBER(38,0)

RESERVATION_ID

Unique identifier of the reservation occupying the slot.

Foreign

Our data warehouse does not currently have a Reservations model. There is an internal "Reservations" table in our Postgres database, but it has not been modeled into Snowflake.

NUMBER(38,0)

PARENT_SLOT_ID

Unique identifier of the slot this slot is linked to.

Foreign (Self-Referencing)

SLOTS

NUMBER(38,0)

Maintenance slots have parent slots

PROGRAM_SEASON_ID

Unique identifier of a specific season within a program.

Foreign

Our data warehouse does not currently have a Sessions model. There is an internal "ProgramSeasons" table in our Postgres database, but it has not been modeled into Snowflake. This table is used for relationships between Programs, Sessions, and Segments.

NUMBER(38,0)

PROGRAM_SEASON_PARENT_ID

Unique identifier of the main program the season belongs to.

Foreign

Our data warehouse does not currently have a Sessions model. There is an internal "ProgramSeasons" table in our Postgres database, but it has not been modeled into Snowflake. This table is used for relationships between Programs, Sessions, and Segments.

NUMBER(38,0)

SESSION_ID

Unique identifier of the session. Sessions sit under the program and can be broken down by skill level, season (e.g., Fall, Winter), age group, or other criteria.

Foreign

Our data warehouse does not currently have a Sessions model. There is an internal "Sessions" table in our Postgres database, but it has not been modeled into Snowflake.

NUMBER(38,0)

SEGMENT_ID

Unique identifier of the segment. Segments (Optional): Add organization within a session—use to group events (e.g., Mon/Wed vs. Tue/Thu), weekly or monthly registrations, or specific time blocks.

Foreign

Our data warehouse does not currently have a Segments model. There is an internal "Segments" table in our Postgres database, but it has not been modeled into Snowflake.

NUMBER(38,0)

PROGRAM_ID

Unique identifier of the program. Programs: Private Lesson, League, Camp, Clinic, Class, Club Team.

Foreign

Our data warehouse does not currently have a Programs model. There is an internal "Programs" table in our Postgres database, but it has not been modeled into Snowflake.

NUMBER(38,0)

PRODUCT_ID

Unique identifier of the product.

Foreign

PRODUCTS

NUMBER(38,0)

FACILITY_ID

Unique identifier of the facility.

Foreign

FACILITIES

NUMBER(38,0)

ROUND_ID

Unique identifier of the competition round.

Foreign

Our data warehouse does not currently have a Rounds model. There is an internal "Rounds" table in our Postgres database, but it has not been modeled into Snowflake.

NUMBER(38,0)

SEASON_ID

Unique identifier of the season.

Foreign

Our data warehouse does not currently have a LeagueSeasons model. There is an internal "LeagueSeasons" table in our Postgres database, but it has not been modeled into Snowflake.

NUMBER(38,0)

LEAGUE_ID

Unique identifier of the league.

Foreign

Our data warehouse does not currently have a Leagues model. There is an internal "Leagues" table in our Postgres database, but it has not been modeled into Snowflake.

NUMBER(38,0)

PRODUCT_CODE_ID

Unique identifier of the product code.

Foreign

Our data warehouse does not currently have a ProductCodes model. There is an internal "GlCodes" table in our Postgres database, but it has not been modeled into Snowflake.

NUMBER(38,0)

We rename "Product Code" columns — as that is what they are labeled in the data warehouse — to "GL Code" in our reports, as it is the preferred terminology for our customers.

PROGRAM_CODE_ID

Internal system code ID for the program. Programs: Private Lesson, League, Camp, Clinic, Class, Club Team.

Foreign

Our data warehouse does not currently have a ProgramCodes model. There is an internal "ProgramCodes" table in our Postgres database, but it has not been modeled into Snowflake.

NUMBER(38,0)

SESSION_CODE_ID

Internal system code ID for the session. Sessions sit under the program and can be broken down by skill level, season (e.g., Fall, Winter), age group, or other criteria.

Foreign

Our data warehouse does not currently have a SessionCodes model. There is an internal "SessionCodes" table in our Postgres database, but it has not been modeled into Snowflake.

NUMBER(38,0)

LINE_ITEM_ID

Unique identifier for the line item.

Foreign

LINE_ITEMS

NUMBER(38,0)

INVOICE_ID

Unique identifier of the invoice.

Foreign

INVOICES

NUMBER(38,0)

ACTIVITY_START_LOCAL

Date/time when the activity starts.

TIMESTAMP_NTZ(9)

ACTIVITY_END_LOCAL

Date/time when the activity ends.

TIMESTAMP_NTZ(9)

SLOT_DURATION

Slot Duration (minutes).

NUMBER(18,0)

BOOKED_ACTIVITY_START

Start date/time of the activity.

TIMESTAMP_NTZ(9)

BOOKED_ACTIVITY_END

End date/time of the activity.

TIMESTAMP_NTZ(9)

BOOKED_SLOT_DURATION

Duration of the slot in minutes.

NUMBER(18,0)

MAINTENANCE_ACTIVITY_START

Date/time the maintenance activity started.

TIMESTAMP_NTZ(9)

MAINTENANCE_ACTIVITY_END

Date/time the maintenance activity ended.

TIMESTAMP_NTZ(9)

MAINTENANCE_SLOT_DURATION

Duration of the maintenance activity (minutes).

NUMBER(18,0)

SLOT_PRICE

Price assigned to the slot.

FLOAT

SLOT_INVOICE_PRICE

Price of the slot as shown on the invoice.

FLOAT

SLOT_COUNT

The number of slots on the calendar.

NUMBER(18,0)

SLOT_PAYMENT_AMOUNT

Amount paid toward the slot.

NUMBER(38,9)

SLOT_BALANCE

Remaining unpaid balance for the slot.

FLOAT

ORGANIZATION_NAME

Name of the organization managing the booking.

VARCHAR(1020)

PARENT_ORGANIZATION_NAME

Name of the parent organization (if applicable).

VARCHAR(256)

EVENT_NAME

Name of the event.

VARCHAR(1020)

PROGRAM_NAME

Name of the program. Programs: Private Lesson, League, Camp, Clinic, Class, Club Team.

VARCHAR(256)

RESOURCE_NAME

Resource name associated with the slot (e.g., Community Rink, Field 1).

VARCHAR(1020)

SLOT_NAME

Name of the slot.

VARCHAR(1020)

SLOT_APPROVAL_STATUS

Approval status of the slot.

VARCHAR(1020)

SLOT_PAYMENT_STATUS

Payment status of the slot.

VARCHAR(1020)

SLOT_RESERVATION_TYPE

Type of reservation occupying the slot.

VARCHAR(1020)

SLOT_PUBLIC_NOTES

Public-facing notes about the slot.

VARCHAR(512)

SLOT_PRIVATE_NOTES

Internal notes about the slot.

VARCHAR(512)

LEAGUE_NAME

Name of the league.

VARCHAR(1020)

RESERVATION_NAME

Name of the reservation.

VARCHAR(1020)

RESERVATION_TYPE

Category of reservation.

VARCHAR(1020)

RESERVATION_STATUS

Status of the reservation.

VARCHAR(1020)

SESSION_NAME

Name of the session. Sessions sit under the program and can be broken down by skill level, season (e.g., Fall, Winter), age group, or other criteria.

VARCHAR(16777216)

SEGMENT_NAME

Name of the segment. Segments (Optional): Add organization within a session—use to group events (e.g., Mon/Wed vs. Tue/Thu), weekly or monthly registrations, or specific time blocks.

VARCHAR(16777216)

PRODUCT_NAME

Name of the product.

VARCHAR(256)

PRODUCT_TYPE

Category of the product.

VARCHAR(256)

PRODUCT_SUB_TYPE

Subcategory of the product (e.g., rental, Birthday Parties).

VARCHAR(256)

LEAGUE_SEASON_NAME

Name of the league season.

VARCHAR(1020)

FACILITY_NAME

Name of the facility.

VARCHAR(1020)

RENTAL_SEGMENT_NAME

Name of the rental segment.

VARCHAR(1020)

ACTIVITY_NAME

Name of the activity.

VARCHAR(256)

SESSION_CODE

Code assigned to the session. Sessions sit under the program and can be broken down by skill level, season (e.g., Fall, Winter), age group, or other criteria.

VARCHAR(256)

PROGRAM_CODE

Code assigned to the program. Programs: Private Lesson, League, Camp, Clinic, Class, Club Team.

VARCHAR(256)

PRODUCT_CODE

The code assigned to the product.

VARCHAR(256)

We rename "Product Code" columns — as that is what they are labeled in the data warehouse — to "GL Code" in our reports, as it is the preferred terminology for our customers.

ACTIVITY_CODE

Code assigned to the activity.

VARCHAR(256)

INVOICE_CREATED_AT

Date/time of when the invoice record was created.

TIMESTAMP_TZ(9)

INVOICE_STATUS

Status of the invoice.

VARCHAR(1020)

PAYING_USER_ID

Unique identifier of the user making payment. User: A global Bond account with a unique email that can be associated with multiple organizations.

Foreign

USERS

NUMBER(38,0)

CUSTOMER_ID

Unique identifier of the customer. Customer: Organization-specific record representing a user's relationship with a particular Organization. The same user can be a customer at multiple organizations.

Foreign

CUSTOMERS

NUMBER(38,0)

CUSTOMER_FIRST_NAME

Customer’s first name. Customer: Organization-specific record representing a user's relationship with a particular Organization. The same user can be a customer at multiple organizations.

VARCHAR(256)

CUSTOMER_LAST_NAME

Customer’s last name. Customer: Organization-specific record representing a user's relationship with a particular Organization. The same user can be a customer at multiple organizations.

VARCHAR(256)

CUSTOMER_EMAIL

Customer’s email address. Customer: Organization-specific record representing a user's relationship with a particular Organization. The same user can be a customer at multiple organizations.

VARCHAR(1020)

CUSTOMER_PHONE_NUMBER

Customer’s phone number. Customer: Organization-specific record representing a user's relationship with a particular Organization. The same user can be a customer at multiple organizations.

VARCHAR(1020)

CUSTOMER_ADDRESS_LINE

Address of the customer. Customer: Organization-specific record representing a user's relationship with a particular Organization. The same user can be a customer at multiple organizations.

VARCHAR(3062)

CUSTOMER_CITY

Customer's city. Customer: Organization-specific record representing a user's relationship with a particular Organization. The same user can be a customer at multiple organizations.

VARCHAR(1020)

CUSTOMER_STATE

Customer's state. Customer: Organization-specific record representing a user's relationship with a particular Organization. The same user can be a customer at multiple organizations.

VARCHAR(1020)

CUSTOMER_ZIP

Customer's zip code. Customer: Organization-specific record representing a user's relationship with a particular Organization. The same user can be a customer at multiple organizations.

VARCHAR(1020)


USER_IN_FAMILY_ACCOUNT

Our Snowflake data warehouse stores all datetime columns in UTC by default. The only exception is when a column name explicitly includes the word "local" — in that case, it reflects local time. If a date-type column doesn't have "local" in its name, assume it's UTC.

That said, when viewing data through our Sigma reports, these UTC columns are automatically adjusted to display in the organization's local time. So while the underlying data model is stored in UTC, Sigma handles the timezone conversion so that end users see times in their local context.

Column Header

Definition

Key?

Link Model

Datatype

Notes

ID

Unique identifier of the record in the USER_IN_FAMILY_ACCOUNT model.

Primary

NUMBER(38,0)

When creating a family account in Bond, you don't need to create a new customer to serve as the admin (primary family member). Instead, navigate to an existing customer and use the 'Link to Account' feature to set up the family account from there. The primary customer acts as the payment holder and has access to all other family members' details.

FAMILY_ACCOUNT_ID

Unique identifier of the family account.

Foreign

Our data warehouse does not currently have a FamilyAccounts model. There is an internal "FamilyAccounts" table in our Postgres database, but it has not been modeled into Snowflake.

NUMBER(38,0)

USER_ID

Unique identifier for the user. User: A global Bond account with a unique email that can be associated with multiple organizations.

Foreign

USERS

NUMBER(38,0)

IS_ADMIN

Whether or not the user is the primary family member.

BOOLEAN

The primary family member. The primary customer is the payment holder and can access all other family members' details.

_CREATED_AT

Timestamp of when the record was first created.

TIMESTAMP_NTZ(9)

_UPDATED_AT

Timestamp of when the record was last updated.

TIMESTAMP_NTZ(9)

_DELETED_AT

Timestamp of when the record was soft deleted.

TIMESTAMP_NTZ(9)

_LOADED_AT

Timestamp of when the record was last loaded into the data warehouse.

TIMESTAMP_NTZ(9)


Did this answer your question?