---
title: "Analyze data from multiple apps"
slug: "analyze-data-from-multiple-apps"
updated: 2024-11-19T17:04:13Z
published: 2024-11-19T17:04:13Z
canonical: "support.tulip.co/analyze-data-from-multiple-apps"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://support.tulip.co/llms.txt
> Use this file to discover all available pages before exploring further.

# Analyze data from multiple apps

## How To Analyze Data From Multiple Apps

*Here's how to analyze completion data from multiple apps.*

In the Analytics Builder, you can analyze data stored via the process of "[completing an app.](https://support.tulip.co/docs/how-to-complete-an-app)

However, you may need to analyze data from multiple apps in one place.

For example, you may want to track common types of defects across 10 separate apps in an assembly process. This means that you will want to add 10 apps to one Analysis.

Here's how to analyze this data in one place.

## Setting Up Apps For Analysis

Before using the Analytics Builder, you must make sure that your data is structured correctly.

Let's continue using the example of tracking defects across 10 apps. If you want to analyze all defects at once, you should try to store the defect name **in a variable with the same name in each app.** This is not required, but it will make it easier to understand the analysis at a later time.

This Variable might be called *defect_type* in all 10 apps.

Also, if you are [analyzing a single field from a Table Record across multiple apps](https://support.tulip.co/docs/how-to-get-real-time-visibility-of-work-orders-by-workstation) like a work order ID, ensure that all Record Placeholders have the same name, like *Active Work Order*.

If you are analyzing cycle time data, you will not need to do this, since this data is stored by default with every app completion.

## Setting Up Your Analysis

Choose any template for your analysis. Then, after you enter the Analytics Builder, select the "Apps" tab in the top left of the side pane:

![](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/How%20To%20Analyze%20Data%20From%20Multiple%20Apps_142524077.png)

Then, from the resulting menu, click each app that you would like to include. In this screenshot, two apps are included:

![](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/How%20To%20Analyze%20Data%20From%20Multiple%20Apps_142524911.png)

After that, select the appropriate variables, Table Records of default data that you would like to analyze across the selected apps.

### **Combining Data From Multiple Apps**

To combine variables from multiple apps, you must use the LINK() expression.

For example, if you are tracking defect type in a variable called *defect_type* in every app, you will need to add the variable from each app into the LINK() expression.

Create a LINK() expression to *link* the Variables from each app. Tulip will append _P1, _P2, _P3, etc. to the variable names, depending on which app contains the variable.

Add each variable to the link function: LINK(*App 1 Variable, App 2 Variable, App 3 Variable).*

![](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/How%20To%20Analyze%20Data%20From%20Multiple%20Apps_154757279.png)

Here's what the result will look like in the Expression Editor:

![](https://cdn.document360.io/7c6ff534-cad3-4fc8-9583-912c4016362f/Images/Documentation/How%20To%20Analyze%20Data%20From%20Multiple%20Apps_154757433.png)

## Further Reading

- [How to Use the Expression Editor in the Analytics Builder](https://support.tulip.co/docs/how-to-use-the-expression-editor-in-the-analytics-editor)

---

Did you find what you were looking for?

You can also head to [community.tulip.co](https://community.tulip.co/?utm_source=intercom&utm_medium=article-link&utm_campaign=all) to post your question or see if others have faced a similar question!

**Variable**

**Variables** are a location to store app information. Variables have a specific type that must match the contents they can store.

Variables are only accessible within a single application and are cleared when the app is restarted or completed.

**Table Record Placeholder**

A **Table Record Placeholder** is a reference to a row in a **Tulip Table**. Table Records can be created either from the Table UI or from an App Trigger.

**Table Record**

A **Table Record** is a reference to a row in a **Tulip Table**. Table Records can be created either from the Table UI or from with an App Trigger.

To edit a record it must be loaded into a **Table Record Placeholder.**

**Variables**

**Variables** are a location to store app information. Variables have a specific type that must match the contents they can store.

Variables are only accessible within a single application and are cleared when the app is restarted or completed.

**Expression**

A configured code snippet that returns a calculated value based on certain inputs. **Expressions** have access to all of the variables, Table Records, and any other data available to an application.