How can I track redemptions?

In this section:

  1. Redemption overview
  2. Failure reasons
  3. Redemption details
  4. Redemption filters
  5. Detailed logs

The Redemptions view lists every redemption attempt of any of the code created within Voucherify. Its goal is to help you track what happens to your codes. The most important feature of the view is the filter panel. Read on to learn how it supports you in drawing insights from redemption data.

Overview

As mentioned, whether successful or failed, each attempt is noted in Voucherify. What's more, every failed redemption has a failure reason.

Failure reasons

Because Voucherify supports complex coupon validation rules, the redemption can fail because of multiple reasons. The following list shows all of them: 

  • voucher did not exist
  • voucher was not active yet
  • voucher expired
  • voucher was disabled
  • redemption quantity exceeded
  • gift voucher amount exceeded
  • order did not match validation rules
  • customer did not match to the segment
  • redemption conditions not met
  • order was specified incorrectly
  • order amount was specified incorrectly
  • order amount was not specified
  • order items was not specified
  • customer was not specified
  • of invalid input data 

Redemption details

You can click on any redemption to display all details. The basics contain:

  • timestamp
  • status
  • customer who has redeemed the code
  • campaign details
  • optional metadata

Depending on the campaign the voucher comes from, the details view can additionally include:

  • order information
  • customer details

Here's an example of a failed redemption

Filters

Redemptions view provides you with a set of filters to track every redemption based on:

Detailed logs

If for some reason, you require more information about the history of the voucher, you might want to visit LOGS tab. This allows you to filter and investigate every API call related to the selected voucher.

On top of basic information such as: HTTP method, URL, Channel and Date you can tap into low-level request details:

  • Request body
  • Response body
  • IP address
  • Request origin
  • User agent