Skip to main content
Reporting: Overview

Explore insights into various reports within Xoxoday, empowering users to effectively optimize rewards, incentives, and payments.

R
Written by Rishabh Kumar
Updated over 2 weeks ago

This article provides an overview of the reports available within Xoxoday Plum, a platform for managing rewards, incentives, and payments efficiently. Below are the different report types offered:

  1. Rewards API Report:

    • This report provides detailed insights regarding the usage of the Rewards API within Xoxoday Plum. Users can track API usage, performance metrics, and any issues encountered during API transactions.

  2. Reward Code Report:

    • The Reward Code report offers a comprehensive overview of all reward codes generated and redeemed within the platform. Users can monitor the distribution of reward codes, redemption rates, and any associated trends or patterns.

  3. Reward Link Report:

    • Users can leverage the Reward Link report to analyze the effectiveness of reward links distributed through Xoxoday Plum. This report provides insights on link clicks, conversions, and overall engagement with the reward links.

  4. Integration Report:

    • The Integration report provides insights into Xoxoday Plum's integration with external systems. Users can monitor integration status, track data synchronization, and troubleshoot any related issues.

  5. Payment and Wallet Report:

    • This report focuses on providing users with a detailed overview of payment transactions and wallet activities within Xoxoday Plum. Users can track payments, withdrawals, account balances, and any financial transactions processed through the platform.

Through these reports, users can effectively monitor, analyze, and optimize their reward, incentive, and payment strategies within Xoxoday Plum. Whether it's tracking API performance, analyzing reward distribution, or monitoring financial transactions, these reports offer valuable insights to drive informed decision-making and enhance overall platform performance.

Did this answer your question?