1. Open an account with Metalitix®
2. Purchase a project plan. For information on project tiers, see here
3. Follow our documentation to configure your project and install the easy-to-use Metalitix® scripts into your experience on your platform of choice
8th Wall, Aframe, ThreeJS, BabylonJS, PlayCanvas, Unity, Unreal Engine.
Enterprise users have access to iOS, Android, Decentraland, and other custom platforms.
Metalitix prices are based on two criteria:
1. Features - There are 3 project tiers that have different features and metrics available. For information on project tiers, see here.
2. Data points - You prepay for the number of data points that your project can collect from users. If you exceed this amount, there are overage fees.
For information on project tiers, see here.
You can prepay for anywhere between 100k and 10M data points. This is approximately 5000 to 50,000 three minute sessions.
A “data point” is a package of information sent from your experience to Metalitix®. By default, a data point is sent every second during a user’s playthrough. This frequency can be changed by your developers when they install the Metalitix® logger scripts into your experience. The logger scripts record the package information such as position data, camera information, custom metrics, and more.
A “session” is a user playthrough of your experience consisting of multiple data points. A session starts when the developer chooses to begin recording data points and ends either when the user closes the experience or the developer chooses to stop recording data points.
“Data retention period” is the lifetime of each individual data point saved in Metalitix®. It begins when Metalitix® receives a data point. Any data points older than the retention period are automatically deleted.
The number of data points in a session depends on collection frequency and session length. For example if the developer configures Metalitix® to collect data 2 times a second, a 1 minute session will have 120 data points (2 data points/second * 60 seconds = 120 data points).
For data collection to work, developers must install and configure the easy-to-use Metalitix® script into their experience. By default, this script collects data once per second, but developers can increase or decrease this frequency. Additionally, developers choose when data collection begins and ends. However, data collection only occurs when users access an experience. It does not persist outside of the experience during other device activities. For more information, see our Data Collection page
Metalitix® does not collect personal information and is anonymous, though we require you to confirm Metalitix® data collection complies with your local privacy laws. For more information on what data is being tracked, see our Data Collection page
Yes, though we require you to confirm Metalitix® data collection complies with your local privacy laws. For more information on what data is being tracked, see our Data Collection page
Developers can collect true/false values, numbers, and text data. Collecting personal information is forbidden.
We expect Metalitix® to have no noticeable impact on your experience's performance. The Metalitix® logger is extremely lightweight, so its footprint across all platforms is minimal.
The exact size of the Metalitix® logger depends on the platform, but it is relatively small. Our ThreeJS logger is about 1 MB. Our Unity package is about 600 KB.
By default, the Metalitix® logger will send about 5 KB of data every 5 seconds. This is based on the default logger configuration that collects data points once every second. If you were to configure the logger to collect data more frequently, then you can expect larger bandwidth requirements. For example, requiring data points four times a second results in 20 KB of data sent every 5 seconds.
So, while bandwidth is small, the exact amount of bandwidth depends on how frequently you configure Metalitix® to collect data from your experience. More frequent data collection results in larger bandwidth requirements. You can expect no more than 25 KB of data to be sent at any transmission.
