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

What is data unification? Steps and a before/after example

Data unification matches and merges records about the same person or entity from several systems into one profile. The steps, a before and after example, and how to test a matching rule.

Su He Reviewed by Ethan Brooks Also called unified data Last updated Nov 20, 2026 Glossary

Quick answer

Data unification is the process of matching, deduplicating and reconciling records about the same person, account or thing from several systems so each appears once, with consistent fields and one stable identifier, for example one profile instead of separate web, app and chat records.

What is data unification?

Data unification is the process of taking records about the same people, accounts or things from several systems and turning them into one consistent set: the same entity appears once, its fields are reconciled, and it carries one stable identifier. A web visit, an app session and a support chat from one person become one profile instead of three unrelated rows.

It is more than moving data. A research paper on the Data Tamer system describes data curation as discovering sources, cleaning and transforming the new data, integrating it with other local sources, and then deduplicating the combined result. The last step is what unification adds: after copying, the same person is still in your data three times until you match the records.

What are the steps of data unification?

One vendor's documentation for a customer-data product (linked in Sources) describes unification as four steps. The names are theirs, but the sequence is the general one:

StepQuestion it answersExample
1. Select and map source dataWhich tables describe the entity, and which column is the email, the phone, the name?Map mail, email_addr and e-mail to one "email" field
2. Deduplicate within a sourceAre there several rows for one person in the same table, and which row is best?Two web profiles for one login: keep the most recent
3. Match across sourcesWhich rows in different tables are the same entity?App user 4127 and billing customer 88 share a login id
4. Build the unified viewWhich columns are kept, merged or dropped?Six email columns merge into one

Two further points from the same documentation matter in practice. Activity data, such as purchases, is kept out of the profile because it has a one-to-many relationship to the customer. And the unified profile gets an identifier that stays the same between runs except when profiles merge (two profiles become one) or split (one becomes two), which is recorded as a "previous ID". Plan for both, because every report keyed on the old ID changes when it happens.

What does unification look like for one user?

Sample data: one person, Ada, uses a product on the web, in a mobile app and through live chat, and pays by invoice.

Before: four records, four identifiers

SystemIdentifierWhat it holds
Website analyticsVisitor id 3FA2C12 sessions from a newsletter link, pricing page viewed 3 times
Live chatThe same visitor id 3FA2C1One conversation asking about annual billing
Mobile appDevice id d_41App opened 5 times, checkout started, not completed
Order systemLogin id u_123One paid order, $240

After: one profile keyed by u_123

LayerWhat the profile now shows
IdentityVisitor 3FA2C1 and device d_41 both bound to u_123
TimelineNewsletter click → pricing views → chat about billing → app checkout started → order
Answer it enables"She asked about annual billing, started checkout in the app and paid on the web" is one story instead of four

Chat and web already shared an id because they come from one script; the app device and the order record joined only when a shared key (the login id) was present. That is the general rule: unification can only be as good as the keys the sources share.

The effect on numbers is just as concrete. Sample data: 1,000 web visitors, 400 app devices and 150 chat visitors. The chat visitors are a subset of the web visitors. 180 of the app devices belong to people who are also among the web visitors, matched by login.

  • Counting every system's "users" and adding: 1,000 + 400 + 150 = 1,550.
  • After unification: 1,000 + 400 − 180 = 1,220 distinct people. The naive count overstates by 27.0%.
  • With 61 buyers, the conversion rate is 61 ÷ 1,550 = 3.9% on the naive count and 61 ÷ 1,220 = 5.0% on the unified count.

The business did not change. The denominator did.

How are records matched?

There are two families of rules, and most real projects use both in order.

  • Deterministic matching joins on a stable key that two systems both hold: a login id, a hashed email address, an order id. It is simple and explainable, and it is the rule you should try first.
  • Probabilistic (fuzzy) matching scores how similar two records are on several fields (name, address, device details) and merges above a threshold. It finds links that no shared key reveals, but it will sometimes be wrong.

Measure a matching rule instead of trusting it. Sample data: a rule proposes 200 pairs as "same person". A reviewer checks them: 190 are correct and 10 are not. The reviewer also finds 30 true pairs the rule missed.

  • Precision = 190 ÷ (190 + 10) = 95%, so 5% of merges are wrong.
  • Recall = 190 ÷ (190 + 30) = 86.4%, so 13.6% of real matches were missed.

A false merge is usually worse than a missed one: it mixes two people's histories and is hard to notice, while a missed match only leaves one person split in two. When in doubt, set the threshold so precision stays high, and keep the weaker rule for suggestions a human confirms.

How is data unification different from data integration?

TermWhat it doesOutput
Data integrationMoves and combines data from several systemsData in one place, still possibly duplicated
Data unificationMatches, deduplicates and reconciles records about the same entityOne record per entity with one id
Single customer viewThe result for people: one profile per customerA profile you can read
Unified data modelOne shared structure for events and entities across sourcesSame event names and fields everywhere

Customer data platforms bundle unification with other functions. Whatever tool you use, the unification step is the same four questions above.

What goes wrong in unification?

  • False merges. Two people sharing a family tablet or a work computer end up as one profile. Prefer a login id over a device id for the merge key.
  • Missed merges. An anonymous visitor who never logs in cannot be linked to anything, and some identifiers expire. If the visitor id rotates daily, today's browser and tomorrow's browser are different visitors.
  • Changing ids. A merge or split changes the unified id. Keep the old id so history can be joined.
  • No consent. Combining records is processing personal data. Link only what your privacy configuration and the person's consent allow, and keep anonymous aggregates anonymous.
  • Unreconciled meanings. Matching rows is not the same as matching fields: "revenue" with and without tax, or two time zones, produces a profile that is wrong in a confident way.

A checklist before you unify

  1. List the sources and, for each, the identifier it holds (visitor id, device id, login id, email, order id).
  2. Choose the strongest shared key and write down the order of fallback keys.
  3. Decide what happens on a merge or split, including how old ids are kept.
  4. Sample 200 proposed matches by hand and compute precision and recall before applying a rule to everyone.
  5. Use the unified count, not the sum of systems, as the denominator for conversion and retention rates.

How does this work in TapCub?

Take Ada's four records above. Here is how they come together in TapCub, and where the limits are.

  1. Web and chat share one visitor id. They run from one script, so a chat conversation already carries the visitor's source, current page and the last two days of browsing, and View in analytics opens the same visitor's profile. All data sources in a project (website, App, mini program) share one identity model and one event table.
  2. Call tapcub.login() after sign-in with your own user id. The first time a device binds to a login id, that session and the device's earlier anonymous events receive the user id; the same user on the app joins through the same id. See identify users.
  3. Read the result in People. A person appears in All-platform analytics › Users › People after login. One login id is one person across web, App and mini program, and the profile shows a day-by-day timeline that merges the bound devices.
  4. Send the order from your server with the same user id, so purchases join the timeline. See send server-side events.

The limits are the ones above. Identified mode needs a plan that includes it, the console has no switch for it yet (contact support to turn it on), and visitors who never log in stay in aggregates and do not get a profile. On the strict privacy preset the visitor id rotates every day, so there is no single profile across days. See identified vs anonymous. TapCub does not match records by name or address; it joins on the ids you send.

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 is data unification in simple terms?

It means making records from different systems about the same person or thing into one record. A web visit, an app session and a support chat become one profile with one id, instead of three rows nobody can connect.

What is the difference between data unification and data integration?

Integration moves and combines data from several systems, so duplicates can still exist. Unification goes further: it matches records about the same entity, deduplicates them and reconciles their fields into one record with one id.

How do you match records from different systems?

Start with deterministic matching on a stable shared key such as a login id or a hashed email. Add fuzzy matching on name or address only if needed, and measure it: in the example, 190 correct, 10 wrong and 30 missed pairs gave 95% precision and 86.4% recall.

Why does unification change my user count?

Because systems count in different units. Adding web visitors, app devices and chat visitors counted the same people repeatedly: 1,550 in the example against 1,220 distinct people, which moves a conversion rate from 3.9% to 5.0%.

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