Getting StartedPOWER Commerce
3D ViewerAugmented realityPOWER Engage
Why POWER Engage?Engagement programsOur ModulesCollectiblesQuestsRewardsSDKAsset Manager
3D Files🕹️ Quests
What is a quest?
A quest is a list a action(s) a program member has to complete within the brand’s ecosystem as part of an engagement program.
Our quest manager allows any marketing manager to create & configure gamified journeys
In this section we’ll be detailing:
- How to configure a quest & its available business rules
- Every quest trigger that we currently support natively
- How to create custom trigger to fit your needs
Create gamified journeys for your consumers
1. Quest configuration When creating a quest on our platform a user has to :
- Fill in quest general configuration (often content that will be used in program’s front end, specific configuration to the quest itself)
- Name of the quest
- Description of the quest
- Validity dates
- A media representing the quest
- Quest Trigger(s) (see below)
- Linked reward (see reward section)
2. Triggers
Whether you’re selecting a native trigger template or creating a custom one, you’ll have through our platform to configure the following :
- A name : ‘collect a badge at our official 2024 event’
- A description: ‘find our hidden official collectible at our event!
- A type
- Collectible (collect a badge) & select linked collectible collection
- 3D/AR Viewer (access a 3D/AR viewer) & select linked viewer
- “Custom” → this type will be used for any trigger created where the actual lifecycle will be handled by the integrator
- Configuration depending on type: → Collectible : → Access AR / viewer : linked viewer → etc → custom
- Linked quest(s)
Example: As part of quest a user has created 2 native triggers : Native trigger 1:
Name: Music festival 2024 Description: Attend our Music festival & find our official collectible ! Type: collectible , collection: Music festival 2024 Linked quest: 2024 program quest
Native trigger 2: Name: Augmented reality experience Description: Find our AR experience, enter it & find your secret promo code Type: 3D/AR viewer (access a 3D/AR viewer) , viewer: Augmented reality experience Linked quest: 2024 program quest
3. Custom triggers
When creating a trigger where type = custom. Same parameters will have to be configured as when re-using ones natively supported within our solution. The only main difference is that the customer/integrator is actually responsible for its lifecycle. Through a technical capability tbd, integrators are able to notif METAV.RS that a user has completed a custom trigger: - Trigger id - user id - completion status
Example: As part of quest a user has created the following custom trigger
Name: E-commerce purchase Description: Purchase at least one product from our new webstore using the promo code you found ! Type: custom Linked quest: 2024 program quest
Check out our integration documentation
Features overview
Native triggers | Description |
Collect badges | Find & collect a brand’s collectible |
3D - AR experience | Visualise a 3D model, access an Augmented reality experience |
Token gated experience | Access an experience/ file or content page depending on user’s collectibles |
E-commerce purchase | Do an e-commerce purchase |
Twitter interaction | Like, retweet, attend a space or follow an account |
Discord interaction | join a discord, join a channel.. |
Instagram interaction | Like, comment a post / follow an account |