Below is a list of frequently asked questions curated by us.

If you have a different question, contact us on info@mtribes.com or leave a message on the chat widget at the bottom of the page.

----------------------------------------------------------------------------------------------------------------------------

Q: How do I control content within mtribes?

A: mtribes isn't a Content Management System (CMS) and doesn't ingest content, so you can't directly manage content in the platform. Instead, mtribes lets you control the configuration of your content in your application.

For example:
You have a component in your app that loads in a list of content. With mtribes, you can model this component (or 'Experience' in mtribes) and configure the properties (List ID or URL etc.) to control when and who it gets served to.

Q: How do I target audiences on a particular device or platform?

A: mtribes lets you create audience groups called Tribes based on a specific device or platform.

When configuring a Tribe, select the device or platform rule and match this to the device or platform of interest. Combine multiple device or platform rules as needed (e.g. audience on iOS and a tablet device).

Once the Tribe is created, you can target it with personalized Experience Scenarios.

Q: How do I target audience in a particular location?

A: mtribes lets you create audience groups called Tribes based on a particular location or set of locations.

When configuring your Tribe, select the location rule and match this to the country of interest. If you want the Tribe to contain multiple countries, create multiple rules matching each of the countries needed.

Once the Tribe is created, you can target it with personalized Experience Scenarios.

Q: What happens if my app loses connectivity with the mtribes server?

A: mtribes has been developed with the end user experience in mind, even in times of connectivity issues. Experience fallbacks have been built into the generated code. The default Scenario on an Experience provides this fallback state.

If the default Scenario on an Experience is switched off, the Experience will not show as a fallback. If switched on, the Experience will display with the properties set within that default Scenario.

Did this answer your question?