- Which users should we include in our data integration?
- How should we allocate agents across our users?
Which Users Should We Include in Our Data Integration?
We find that customers have the best results when they do the following:- Send all customer info to Aampe (users, events, etc.)
- Use Aampe audiences to manage the total number of addressable users
Why We Usually Recommend This Approach
This approach offers several advantages:- Dynamic users: Having extra users available within Aampe makes it easy to pull in new users when other users naturally exit.
- Easier maintenance: Priorities change! Aampe customers with limited agents often want to try agentic personalization on different subsets of their customer base. This is much easier to do when audience logic lives in Aampe.
Keeping Audiences Consistent Across Tools
One important consideration is how Aampe and its audiences interact with other tools. When other tools need to know which users are eligible for Aampe, it can still make sense to send the full customer base to Aampe. Message eligibility, however, would be managed outside of Aampe and passed to Aampe via a user attribute.How Should We Allocate Agents Across Our Users?
Users receive an Agent as soon as they are eligible to receive messages.The best way to manage an Aampe-eligible subset of users depends on what you’re hoping to accomplish. Here are our recommendations based on different scenarios: If you’re unsure where agents can be most effective: We suggest starting with a comprehensive cross-section of users. Aampe has proven effective across diverse user segments:
- New users just getting started
- Long-time, established users
- Highly engaged active users
- Inactive or dormant customers