TapCub is live — analytics, insights and live chat, free on one platform
Glossary

What is a data model? Levels, types and an event-model example

A data model describes the entities, attributes and relationships in your data. The three levels, common types, and a worked event model showing how events, users and properties connect.

Su He Reviewed by Ethan Brooks Also called data modeling Last updated Nov 19, 2026 Glossary

Quick answer

A data model describes what a dataset contains and how it connects: the entities you keep records about, the attributes of each, and the relationships between them. In analytics, the core of the model is how events, users and their properties link together.

What is a data model?

A data model is a written description of what a dataset contains and how the pieces connect: which entities exist (things you keep records about), which attributes each one has, and which relationships link them. It is the blueprint that comes before tables, dashboards or queries.

A shop's data model, in one sentence: "A customer places many orders; an order contains many products; each product has a price and a category." Three entities, three relationships, a handful of attributes. Anyone who reads it knows what questions the data can answer, and which it cannot.

For analytics, the most important part of the model is how three things connect: events (what happened), users (who did it) and properties (the details of each). Get that right and funnels, retention and segments all follow; get it wrong and numbers disagree between reports.

What are the three levels of a data model?

Models are drawn at three levels of detail, each for a different reader.

LevelDescribesWritten forExample (shop)
ConceptualThe main entities and how they relate, in business wordsBusiness owners, product managersCustomer — places — Order
LogicalEvery entity's attributes, keys and relationship rules, independent of any databaseAnalysts, data designersOrder has order_id (key), customer_id, placed_at, total
PhysicalThe actual tables, columns, data types and indexes in a specific systemEngineersorders(order_id BIGINT PRIMARY KEY, customer_id BIGINT, placed_at TIMESTAMP, total DECIMAL(10,2))

Work top-down: agree the conceptual picture first, because arguments about column types before agreeing on what an "order" is waste time. Codd's relational model (1970) and Chen's entity–relationship diagrams (1976) are the roots of this vocabulary.

What are the common types of data model?

TypeShapeGood forWatch out for
RelationalTables joined by keysTransactions, consistent business recordsJoins get slow at very large event volumes
Dimensional (star schema)A central fact table of events or sales surrounded by descriptive dimension tablesReporting and BINeeds planning of which dimensions you query by
DocumentNested records (JSON)Flexible, changing attributesHarder to enforce the same fields everywhere
GraphNodes and edgesNetworks of relationshipsLess natural for plain aggregates
Event-basedAn append-only stream of "who did what, when, with what details"Behavioral analyticsNeeds strict naming, or the same action gets recorded under many names

Most product-analytics tools use an event-based model on top of a dimensional layout: one big fact table of events, plus a profile for each user.

What does an event model look like?

Sample data: a three-row slice of an event model for a web shop.

eventtimevisitoruser (after login)properties
page_view10:02:11v_8f3—page = /pricing, source = google
signup10:04:40v_8f3u_204plan = free
purchase10:19:05v_8f3u_204order_total = 49.00, currency = USD

And the user profile, stored once:

useremail domaincountrycreated
u_204example.comDE10:04:40

Read the model off the example:

  • An event has a name, a time and a person. The same name always means the same action.
  • Event properties describe that one occurrence (the page, the order total). They are different for every row.
  • User properties describe the person and live on the profile (country, plan). They change slowly.
  • Identity is the join: visitor v_8f3 became user u_204 at signup, so the earlier page view can be attributed to the same person.

Where should a property live: on the event or on the user?

Ask: is this a fact about this moment, or about the person?

  • "Order total", "page path", "button label" → event property.
  • "Country", "signup date", "plan today" → user property.
  • "Plan at the time of purchase" → copy it onto the event, because the user property will change later and history should not.

The cost of getting it wrong is real. Sample data: 10,000 users with 120 events each is 1,200,000 event rows. Copying six user attributes onto every row stores 1,200,000 × 6 = 7,200,000 values; keeping them on the profile once stores 10,000 × 6 = 60,000. Duplicates also drift: if one row says "plan = free" and another says "pro" for the same person, which is right? Store what must stay constant on the event, and keep the rest in one place.

What are the design principles for an analytics data model?

  1. One name per action. signup everywhere, never sign_up, Signup and registered. Names are the key to every report.
  2. Few events, many properties. Twenty well-named events with properties beat five hundred one-off events. Put "which button" in a property rather than creating a button_a_click event.
  3. Consistent types. A property is a number everywhere or a string everywhere. A price stored as "49.00" in some rows and 49 in others breaks sums.
  4. Define keys on purpose. Decide which id means a visitor, a device, a person and an account, and how they join.
  5. Write it down. A model nobody can read is not shared. A data dictionary lists each field's meaning, and an event schema pins down the structure of each event.

For how several systems are merged into one model, see unified data model.

What mistakes do teams make with data models?

  • Modeling the screen, not the behavior. Events named after UI elements break every redesign. Name the action (add_to_cart), not the widget.
  • Free-text values where a list belongs. "Plan = Pro", "pro", "PRO" are three values to a computer.
  • No owner. If nobody decides whether a new property is allowed, the model grows without bound.
  • Changing meaning silently. If purchase used to include trials and no longer does, old and new data are no longer comparable. Record the change date.
  • Collecting everything "just in case". Every property you do not use still has to be maintained, and some may be personal data you should not keep.

How does TapCub model your data?

TapCub's model is event-based with user and account layers, and it is built to be written down before it is built. Following the web-shop example:

  1. Plan the events first. In All-platform analytics › Data › Tracking plan, each row records an event you intend to collect: name, display name, category, platforms, trigger, properties (name, type, required or not, example), owner and status. Planned events can be listed before any code is written.
  2. Check what arrives. Turn on live verification (24 h) to see, per event, how many hits arrived and how complete the required properties are. New events nobody planned land in All-platform analytics › Data › Event inbox to be claimed.
  3. Control the properties. All-platform analytics › Data › Property dictionary has separate User, Event and Account tabs. Each key has a type (String, Number, Boolean, Datetime or List), a sensitivity label and optional validation rules such as allowed values.
  4. Connect people. An anonymous visitor has a visitor id; after your site calls tapcub.login, the person appears in All-platform analytics › Users › People, and earlier anonymous activity on that device is attached to them. Login needs identified mode, which depends on your plan. Counting by visitor, device, person or account is a choice you make per analysis.
  5. Add the account layer if you sell to companies. After tapcub.group('company', 'acme', {...}), people roll up to accounts in All-platform analytics › Users › Accounts.

TapCub does not design the model for you or enforce a particular warehouse schema; the plan, dictionary and validation rules are the tools for keeping your own model consistent.

Sources

Was this explanation clear?

We use your answers to fix and expand this page.

Su He

Data Analyst

Explores traffic sources, conversion funnels, and retention, using clear metric definitions and concrete examples to explain what the numbers mean.

FAQ

Questions people ask

Short answers to the follow-up questions that come up most.

Still have a question?

Chat with the team behind TapCub — we usually reply within a few hours on business days.

What are the three types of data model?

Conceptual, logical and physical. The conceptual model shows entities and relationships in business terms. The logical model adds attributes, keys and rules independent of any database. The physical model is the actual tables, columns, types and indexes in one system.

What is the difference between a data model and a database schema?

A data model is the design: what entities exist and how they relate. A schema is one implementation of it in a particular database, with exact tables and column types. One model can be implemented as different schemas, and a schema without a model is hard to understand.

What data model do analytics tools use?

Most behavioral analytics tools use an event-based model: a stream of events, each with a name, a time, a person and properties, plus a profile of properties for each user. Some add an account layer for business customers.

Should a property be stored on the event or on the user?

Store facts about that moment on the event, such as order total or page path. Store slowly changing facts about the person on the user profile, such as country. If you need the value as it was at the time, such as plan at purchase, copy it onto the event.

See this number on your own site

Add one script tag for web and apps, and the first reports fill in within minutes.

See your data clearly. Find your growth.

Every click, backed by data. Install one line of code and see your first numbers in a minute.

No credit card · Free plans for analytics and chat · Cookieless analytics