A. B. C. D. E. F. G. H. I. J. K. L. M. N. O. P. Q. R. S. T. U. V. W. X. Y. Z.
A |
|
---|---|
Account |
A personal account set up when you register or join mtribes for the first time. You can create multiple organizations under one account. |
Active days (Tribe filter) |
The average number of days that interactions (clicks, views, etc.) occurred on your platform. |
Active user |
A signed in audience member who has interacted (clicked, viewed, etc.) in the last 30 days. |
Activity definition |
The number of audiences who have interacted (clicked, viewed, etc.) in the last 30 days. |
Activity (metric) |
A line graph showing the number of active users associated with a Tribe per day for the last 30 days. |
Admin (or Administrator) |
A member of your mtribes organization with full administration permissions and privileges. See also Member. |
Allocation |
The percentage of your audience that will be targeted with a Scenario. |
App |
Your application. This could be a website or mobile app etc. |
At-risk user |
A signed in audience member who has not interacted (clicked, viewed, etc.) in over 30 days. |
Average session time (Tribe filter) |
The average length of the interactions (clicks, views, etc.) on your platform across the last 30 days. |
Audience |
The total number of signed in and not signed in audience who use your product. Your audience can be grouped into Tribes. See also Tribes. |
C |
|
CLI |
Command Line Interface. A text-based interface used to view and manage computer files. Our CLI has been built to automate some of the mtribes installation process. |
Collection (template) |
A Collection is a group of Experiences. Each Collection represents a group of components on your app that can be scheduled and served to audiences. |
Contextual properties |
Unique user traits organically identified during the runtime of your app. mtribes can support string (characters), number, Boolean (true.false) and date format. Example: users who match a seasonal campaign or belong to a specific subscription model. |
Created (Tribe filter) |
The data a database record is created on mtribes. |
D |
|
Dashboard (organization) |
The control panel for your organization, where you can create and delete Spaces, invite teammates view activity metrics, and more. |
Dashboard (Space) |
The control panel for your Space. Each Space has its own dashboard which displays a range of audience, Tribe and Scenario metrics and teammate activity. |
Device type (Tribe filter) |
The type of device (e.g. mobile, desktop) used in the last session. |
E |
|
Experience (template) |
An Experience template represents a component or element in your app, like a call-to-action banner, video, or form. Once you've set one up, it can be added to a Collection. |
F |
|
First seen (Tribe filter) |
The first date a session is identified on mtribes. |
I |
|
Invite / Invitation |
An email sent by an administrator to a new member, inviting them to join your organization. |
J |
|
Joined (Tribe filter) |
The date a visitor becomes a user on your platform. |
K |
|
Known (Tribe filter) |
The date a visitor becomes a user and known to mtribes (can also be the ingestion date). |
L |
|
Last seen (Tribe filter) |
The last date an interaction occurred on your platform. |
Least active (Tribe filter) |
The Tribes who were the least active (clicks, views, etc.) in the last 30 days (calculated across audience). |
Least improved (Experience) |
The least active Experiences (clicks, views, etc.) in the last 7 days (determined by traffic). |
Least served (Experience) |
The Experiences served the least number of times in the last 7 days (determined by traffic). |
Location (Tribe filter) |
The location (continent, country, city, subdivision, or postal/zip code) of the last session. |
Lost user |
A signed-in audience member who has not interacted (clicked, viewed, etc.) in over 60 days. |
M |
|
Member |
The person who belongs to your metrics organization without administration permissions and privileges. See also Teammate. |
Metrics |
The quantifiable measure used to track and assess the activity of your audience, Tribes, or Scenarios. |
Most active (Tribe) |
The Tribes who were the most active (clicks, views, etc.) in the last 30 days (calculated across audience). |
Most improved (Experience) |
The most active Experiences (clicks, views, etc.) in the last 7 days (determined by traffic). |
Most served (Experience) |
The Experiences served the most number of times in the last 7 days (determined by traffic). |
N |
|
New user |
A signed in audience member who has interacted (clicked, viewed, etc.) for the first time in 30 days. |
Next day (Scenario scheduling) |
A Scenario that is scheduled to end the day after it starts. |
O |
|
One-off (Scenario scheduling) |
A Scenario that has been scheduled to serve on a one-off basis. |
Organization |
A unique tenant of the mtribes platform representing a customer. It is the administrator for managing the creation or deletion of your Spaces, and for monitoring activity, etc. Multiple organizations can be held by one account holder. See also Account. |
P |
|
Platform |
The type of platform (e.g., iOS, Android) used in the last session. |
Properties |
The characteristics that personalize your Experience (start and end date, tags, color, etc.) |
R |
|
Reach |
The estimated percentage of audience who may receive your content or campaign based on the Tribes rules you've selected. |
Recurring (Scenario scheduling) |
A Scenario that has been s scheduled to serve at a repeating cadence. |
S |
|
Same day (Scenario scheduling) |
A Scenario that is scheduled to end on the same day as it starts. |
Scenario |
A Scenario is a variant of an Experience that has been personalized for a specific Tribe. Scenarios can be served at a one-off or recurring date and time. See also Schedule. |
Scenario activity |
The trackable behavior or engagement of selected Tribes from a served Scenario. |
Schedule |
The setting of a date and time for serving your Scenario. This can be a one-off or a recurring schedule. |
SDK |
Software Development Kit. Used by your developer to integrate mtribes with your app. |
Section |
A placeholder in a Collection template that can support up to 20 Experiences. A section is configured in the templating stage and can be edited in the targeting stage. |
Served experiences |
The number of Experiences served to audiences in your organization in the last 30 days. |
Space |
A Space is a self-contained project or workspace. Each Space has its own configuration, content, audience base and dashboard. |
Success rate |
Scenario success rate is calculated by dividing two metrics (primary and secondary). The outcome is expressed as a percentage. Example: promotion/completed out of promotion/viewed = success % |
T |
|
Teammate |
A term for fellow members of your mtribes organization with permissions and privileges set by the administrator. See also Member. |
Templates (Experience and Collection) |
Templates represent components in your app. ‘Templates’ is the collective word we use for Experience and Collection templates. See also Experience and Collection. |
Tracked events |
The total number of tracked interactions (clicks, views etc.) in the last 30 days. |
Tribe |
A group of users and/or visitors in your Space, who share common traits like demographics, behavior, interests, or any other defining characteristic from your database. |
Tribe card |
The visual summary of the size, activity and rules of each of your Tribes. |
Tribe category |
A group of Tribes defined by you, based on specific characteristics, similarities, or targeting activity. |
Tribe of the week |
The most active Tribes from the past 7 days, including non-targeted Tribes that contain the same users and visitors. |
Tribe rules |
The segmentation rules used to identify and group audiences into Tribes. Rules can be based on attributes, behavior, custom contextual traits, or user tags. |
Tribe theme |
The colors, wallpaper, and logo used to customize or brand your Tribes. |
U |
|
User |
Signed-in audiences in your organization, Space or Tribe. |
User agent (Tribe filter) |
The technical data (e.g. operating system, browser) of the last session. |
User and visitor |
The total number of signed-in and not signed-in audiences. |
User breakdown |
The breakdown of the Tribe rules applied as a percentage of the estimated audience size. |
User tags |
These represent the segmentation from your application. They can be ingested via our SDK, or added manually. |
V |
|
Visitor |
Not signed in audiences in your organization, Space, or Tribe.
|