Welcome to Zuora Product Documentation

Explore our rich library of product information

Set up a test to compare Smart Retry and your existing retry logic

Compare Smart Retry with your existing gateway-response-code retry logic by running an A/B test that replicates your current retry configuration in a dedicated Smart Retry customer group.

To compare Smart Retry with your existing retry logic that is configured based on gateway response codes, set up an A/B test by replicating your current retry logic for a dedicated Smart Retry customer group.

  1. Create a new customer group for Smart Retry.
    1. Name the group so you can easily identify it as a Smart Retry group, for example, Group Smart Retry.
    2. Create filters for the Group Smart Retry customer group.

      To segment customers, select the Custom ZOQL Query option and define a ZOQL filter. For balanced A/B testing, route 50% of customers to the Smart Retry group and keep the other 50% on your existing retry logic. To achieve true A/B testing, use a random filter. You can also add filters such as region, gateway, or other customer attributes.

      The following examples show ZOQL filters that you can adapt:

      (((((Account.AccountNumber like '%6') or Account.AccountNumber like '%7') or Account.AccountNumber like '%8') or Account.AccountNumber like '%9') or Account.AccountNumber like '%0')
      (((((Payment.GatewayResponseCode = '15006') or Payment.GatewayResponseCode = '15007') or Payment.GatewayResponseCode = '15008') or Payment.GatewayResponseCode = '15009') and Payment.Gateway = 'PayPalEC') and (Account.AccountNumber like '%6')
  2. Apply your existing retry logic to the All Remaining Customers group.
  3. Enable Smart Retry on the Group Smart Retry group and configure the retry logic to mimic your existing retry logic.

    For example, if your current retry logic retries payments every 48 hours for 4 attempts, configure the following Smart Retry time constraints:

    • Number of attempts: 4

    • Number of days: 8

    • Optional: Add a workflow on entry into retry, on exit from retry, or both. As a best practice, add an exit workflow to address any outstanding balance on accounts or invoices that were not collected. For example, write off the invoice, suspend or cancel the subscription, or send customer communications.

  4. Ensure that the Group Smart Retry group has a higher priority than the All Remaining Customers group.

Run the A/B test long enough to complete several retry cycles, typically at least 4 to 6 weeks.