External Events
1. What Are External Events
External Events are incoming signals from a brand’s systems that describe a fact or status change for a user and are consumed by ResultFly to drive campaigns. Examples include “the customer completed a purchase,” “the member reached a new loyalty tier,” or “the shopper received a bonus outside ResultFly.”
External Events are not outbound notifications, and they are not the clicks or answers a person makes inside a game—they come from the brand’s ecosystem and flow into ResultFly.
2. How External Events Are Used in Campaigns
External Events are the trigger layer for campaign logic. They can grant points, issue attempts, unlock games or journeys, shift a user into a new state, or launch server-driven automations. The user does not have to be active inside ResultFly at the moment the event arrives; the platform queues and applies the change as soon as the event is processed.
3. Pre-Provisioned Users
ResultFly can store users long before they open a campaign. Brands often pre-provision loyalty IDs or anonymous tokens and immediately send events against them. When the person eventually visits the campaign—or even if they never do—the accumulated points, access rights, or rewards are already attached to that user record.
4. Why ResultFly Uses Events Instead of Direct State Updates
Events keep the story behind every balance or entitlement. They preserve why something changed (“bonus for purchase #12345”) rather than only the latest number. This history supports auditing, customer care, and marketing analysis. Event processing also guards against accidental repeats: if a purchase file is resent, ResultFly recognizes it as the same event and skips the duplicate effect. Finally, having a full trail lets teams replay or simulate campaign logic when they adjust mechanics later.
5. Event Identity and Deduplication
Each External Event carries an external identifier supplied by the source system. ResultFly remembers that identifier, so re-sending the same event does not double the reward. This protects campaigns from integration glitches, batch retries, or manual resubmissions, keeping the user’s state accurate.
6. What External Events Can Affect
- Points, bonuses, and multipliers.
- Attempts, lives, or other participation limits.
- Custom user variables that personalize flows.
- Segments and conditions that steer campaigns.
- Prize eligibility or inventory reservations.
7. What External Events Are NOT
External Events are not push notifications, email triggers, clicks in the interface, or ResultFly analytics events. They also are not outbound messages of any kind—the direction is always brand systems sending signals into ResultFly.
8. Typical Business Scenarios
- Offline purchase streams grant points that instantly appear in an in-app game, encouraging shoppers to continue playing.
- Historical loyalty data is backfilled before launch so that the campaign starts with accurate tiers and unlocked experiences.
- Finance teams adjust balances by sending corrective events, keeping rewards aligned with returns or manual reviews.
9. Relationship to Technical Integration
External Events travel through the brand’s server integrations with ResultFly. Implementation specifics—formats, security, sequencing—live in the developer documentation, and ResultFly supports multiple event sources (CRM, POS, loyalty backends) so teams can pick the path that fits their architecture.