Welcome to Village

Explore our guides & examples to get started.

Our Guides

Our guides introduce you to the core concepts of Village by showing them in action. Each guide links to our knowledge base for a deeper dive on specific components of Village.
Popular Use Cases
More Guides
Advanced
Point Redemption Programs
🛠️
Coming soon
🛠️
Subscriptions & Stored Value
🛠️
Coming soon
🛠️
Long Term Incentives: Bonus Pools
🛠️
Coming soon
🛠️
Loyalty Program Basics
🛠️
Coming soon
🛠️
Churn Reduction Basics
🛠️
Coming soon
🛠️
Interstitial Point Systems
🛠️
Coming Soon
🛠️
Multi-Tier Referral Programs
🛠️
Coming Soon
🛠️
Leveraging Expiration
🛠️
Coming Soon
🛠️

About Village

Welcome to Village! 👋
If you’re non-technical (ie. not writing any code), this is your Village Home Base. If you're a developer, this will be helpful too, and we’ll link to developer documentation everywhere it’s relevant.
If you want to skip ahead, navigate using the sidebar 👈 or the search bar 👆; also, here's a link to the Developer Quickstart ->.

Why Village

Village creates stronger, more valuable relationships with your users. Whether they are customers buying your product, or suppliers earning on your platform, Village's goal is to turn all your users into power users.
We do this by driving exactly the right behavior, at exactly the right time, through a wide range of automated incentives, segmentation, and messaging.
You can think of Village as the brains and machinery driving your user relationships. Village connects to your data, enables your team to drive business outcomes, then empowers you to analyze and iterate on your performance.
That means businesses and platforms of all sizes can benefit from the same tools and capabilities that the most sophisticated platform companies use (like Uber, Airbnb, and Amazon) in order to create strong, sticky, and higher value user relationships.
Village Overview

Rules: The Building Blocks of Village

Village is built on a system of logic called Rules. Everything that happens in Village is a result of a Rule being executed.
The basic components of a Rule are:
  1. 1.
    Triggers
  2. 2.
  3. 3.
    Output Operations (Add to Segment, Issue Award)
Triggers are usually some event happening on your platform, Conditions let you restrict triggers by things like time of day, and Output Operations allow you execute actions such as awarding your users with promotions, loyalty points, cash bonuses, and more.
You can also use output operations to do other things, like segment users and send emails.
Rules can be conveniently combined into Programs, which can be used as functional groups of business logic and shared Conditions. For example, you may want to group all Rules associated with with customer loyalty into one Program, and all the Rules associated with referrals into another.
Simple Rule Examples

Triggers: Connecting User Activity to Outcomes

Triggers tell a Rule when to fire. The most common types of Triggers are:
  1. 1.
    A user does an action, such as tapping a button or making a delivery
  2. 2.
    A user buys or sells something on your platform
  3. 3.
    A user meets a minimum Award balance
  4. 4.
    A user completes a minimum number of actions
  5. 5.
    A user reaches a defined goal
  6. 6.
    A user joins or leaves a segment
  7. 7.
    You have scheduled a recurring trigger event
What drives Rule Triggers?

Conditions: Controlling the Scope of Rule Execution

You can configure Conditions at both the Rule and Program level to be evaluated whenever a Rule is triggered. Rule Conditions allow you to limit (or amplify) the Output Operation of a Rule.
Conditions are grouped into the following categories:
  1. 1.
    Segment Conditions: Restrict Output Operations to users that are "in" and/or "not in" predefined user segments.
  2. 2.
    Time Conditions: Restrict Rule evaluation to a fixed period (example: July 2023) and/or a recurring period (example: every Wednesday from 9AM to 11AM).
  3. 3.
    Max Budget: Set budget – whether it's dollars, loyalty points or any other Award type – restrict the payout for a given Program or Rule. Max budgets can be set on the basis of per user, per time, per award, per program, per rule, and more.
  4. 4.
    Segment Multipliers: If you want to increase or decrease a user Award size in the Output Operation, you can apply a multiplier (including down to 0) based on a user's segment(s).

Output Operations: The Outcome of a Rule

The Output Operation is the action that Village takes after a Rule is triggered and its Conditions are met. This is where the magic happens.
Common Output Operations include:
  1. 1.
    Issuing an Award, like loyalty points, cash, badges, access to a bonus pool, or status
  2. 2.
    Adding or removing a user from a Segment
  3. 3.
    Triggering another Rule, such as triggering a higher order Goal-based Rule when a certain number of Activities have been completed
  4. 4.
    Sending comms through your existing CRM platform using Village data connections (or directly through Village for simple event-based communications)

Where next? Here are some ideas:

To begin data integration with Village
To start configuring Rules & Programs through your Admin Dashboard