Learn what an event-based Tribe is and how to set one up.*
This article describes what an event-based Tribe is and how to set one up.
Topics covered here:
- What are event-based Tribes?
- How do I add an event to a Tribe?
- Example event-based Tribe
- How do I define a custom event?
- How long does it take for the reach to update?
- What do I do if the estimated reach isn’t updating?
What are event-based Tribes?
Events are user interactions with your application, such as clicked, viewed, or watched. mtribes allows you to create Tribes based on these events so that you can target your users with more personalized experiences.
How do I add an event to a Tribe?
On the Tribe details page, select the add filter button and select Events from the dropdown. Select from a list of received events (e.g., Ad/Clicked) or specify a custom event.
Once you've selected the event, you can configure the following properties:
Condition indicates whether users and/or visitors have or have not performed the event. The condition default is ‘have done.'
Frequency determines how many times users and/or visitors have performed the event, e.g., more than twice. Select from the following options:
- More than
- Less than
- Any amount
Timeframe determines the period (in days) within which users and/or visitors performed the event,e.g., less than 7 days ago. The timeframe is limited to 30 days in accordance with data privacy rules. Select from the following options:
- More than
- Less than
- At any time (last 30 days)
Metadata provides context to the event in the form of key-value pairs, which will need to be defined by your developer in the SDK. This determines what your users and/or visitors are interacting with, e.g., the specific video, advertisement, or genre of video.
A maximum of three key-value pairs can be accepted per event. Some examples of key-value pairs are:
- Metadata: Key: Premier League | Value: Liverpool
- Metadata: Key: Fantasy | Value: Lord of the Rings
- Metadata: Key: Documentary | Value: History
Example event-based Tribe
Let’s say you want to target FIFA World Cup fans with more engaging football content. You could create a Tribe based on users who have watched FIFA game content more than twice in the last week, and then target this Tribe with more relevant football content. The configuration might look like this:
- Event: video/completed
- Condition: Have done
- Frequency: More than 2 times
- Timeframe: Less than 7 days
- Metadata: Key: Football | Value: FIFA
How do I define a custom event?
To define your own custom event, select the add filter button on the Tribe details page and select Events from the dropdown. A menu with a list of events will open where you’ll see + Custom event. Clicking this button will open a modal on the screen that prompts you to enter a Custom event.
There are certain formatting rules to note when entering your event type. It:
- Must be entered in string format
- Must be written out as: category/action
- Cannot include a reserved category name
Once you’ve entered your custom event successfully, click Save. You can now configure the event properties in the filter.
How long does it take for the reach to update?
It can take up to 15 minutes before you can expect to see an estimated reach for an event-based Tribe. For this reason, we suggest you do not use this Tribe in any Scenarios until the calculation is complete. Once the calculation is complete, you will see an updated reach on the Tribe card, Tribe details, and any Experience the Tribe is used in.
What do I do if the estimated reach isn’t updating?
If the estimated reach isn't updating, please check the following:
- Your developer is correctly triggering and sending the accurate event.
- The event contains accurate metadata in key-value pair format.
- You aren’t sending more than 3 key-value pairs per event.
- You're entering the metadata exactly as it's being sent by your developer. Check the spelling, casing, and spacing of your entries.
If you need further support, please contact email@example.com
Next - What are user tags?