Configuration Experiment #R2

Configuration Experiment #R2


Goal
The goal of this experiment is to help you understand how configuration changes impact rewards. For this challenge, you will use a production workspace and enter some configuration. When asked to write down something, please copy the value to a document (along with the step #), as you will be using those values later on.

Difficulty
Easy.

Preparation
Create a CSV file with the following:
  • Date,Unique ID,Owner,Revenue
  • 2021-01-01,ID-1,Daniel Martinez,1
  • 2021-01-01,ID-2,Daniel Martinez,10
  • 2021-02-01,ID-3,Daniel Martinez,100
  • 2021-02-01,ID-4,Daniel Martinez,1000

As you can see, there are 2 transactions in January, and 2 transactions in February. All transactions are assigned to "Daniel Martinez".

Steps
  1. Go to Account > My Workspaces
  2. Create a production workspace
  3. Go to Users > Add Users
  4. Add a user with email DanielMartinez@xyz.com
  5. Go to Transactions > Add Transactions
  6. Import your CSV file
  7. Go to Plans > All Plans
  8. Create plan "Test"
    1. Choose "Monthly"
    2. Choose "By Individual"
    3. Choose "All Workspace Users"
    4. Choose "Revenue" > "Raw Value"
    5. Add a per-transaction reward with the following formula
    6.   
  9. Create the plan
  10. Go to Calculations > All Calculations
  11. Run a calculation for January 2021
  12. Open the calculation
  13. Go to the Credits tab
    1. Write down how many transactions were credited
    2. Why were 2 transactions credited in January?
  14. Click on "Export Credits" (choose "Export All Fields")
    1. Write down transaction unique IDs (ex: "ID-1", "ID-2") and commission amounts
    2. Are calculated commission amounts those you expected?
  15. Go to Transactions > All Transactions
  16. Search for "ID-2" (a January transaction)
  17. Click on the transaction to edit it
  18. Write down the transaction's URL
  19. Change the "Date" to any date in February 2021
  20. Save and select "Allow Overwrites"
  21. Go to Calculations > All Calculations
  22. Run a calculation for February 2021
  23. Open the calculation
  24. Go to the Credits tab
    1. Write down how many transactions were credited
    2. Why were 3 transactions credited in February?
  25. Click on "Export Credits" (choose "Export All Fields")
    1. Write down transaction unique IDs (ex: "ID-3", "ID-4") and commission amounts
    2. Are calculated commission amounts those you expected?
  26. Copy/paste the transaction URL into your browser
  27. Go to the Commissions tab
    1. Did you expect to see the displayed values?
  28. Go to Calculations > All Calculations
  29. Select both calculations
  30. Release credits for both calculations (ignore warnings)
  31. Grab coffee or lunch for ~1 hour
  32. Review alerts (the bell in the top right corner)
    1. Do you see a double-payment warning?
    2. Why is a double-payment warning expected?
    3. If you do NOT see a double-payment warning, please proceed to next steps. It can take 24 hours for this warning to be displayed. Here is what this type of warning looks like. It would of course look different for you.

  33. Go to Plans > All Plans
  34. Edit plan "Test"
  35. Go to the Incentives tab
  36. Change the per-transaction reward to this formula

  37. Save plan changes
  38. Go to Calculations > All Calculations
  39. Re-run the calculation for February 2021 (with delete)
  40. Open the calculation
  41. Click on the Credits tab
  42. Write down how many transactions were credited
    1. Why were 3 transactions credited in February?
  43. Click on "Export Credits" (choose "Export All Fields")
    1. Write down transaction unique IDs (ex: "ID-3", "ID-4") and commission amounts
    2. Are calculated commission amounts those you expected?
  44. Copy/paste the transaction URL into your browser
  45. Go to the Commissions tab
    1. Did you expect to see the displayed values?
  46. Go to Plans > All Plans
  47. Edit plan "Test"
  48. Go to the Limits tab
  49. Configure this filtering formula

  50. Save plan changes
  51. Go to Calculations > All Calculations
  52. Re-run the calculation for February 2021 (with delete)
  53. Open the calculation
  54. Go to the Credits tab
    1. Write down how many transactions were credited
    2. Why were 2 transactions credited in February?

Key Learnings
  • If a transaction's date is moved to a later period, a duplicate commission can be issued
    • Sales Cookie will generate double-payment warnings when this happens
    • Generating those warnings can take time because computationally expensive and ran in the background
  • It is possible to craft a reward formula which lookups the amount already paid to a payee on a transaction, and pay the difference
    • This creates protection against double-payment, but can also be used for cases where facts have changed (ex: revenue is higher / lower) and the commission amount should be re-evaluated 
    • Note: the GetCommission() function takes additional parameters which can make the lookup more specific
  • It is possible to also filter out transactions which already have had a commission paid to a payee
    • This might be a good strategy if we also want to avoid not only double-payment, but also double-crediting
    • If a commission was paid, we return 0, so the transaction will be filtered out
    • If we cannot resolve a transaction's owner to a user, we prefer to let the transaction go through, so we can generate appropriate crediting alerts
  • We recommend reading this KB

    • Related Articles

    • Configuration Experiment #V5

      Goal The goal of this experiment is to help you understand how to use custom variables in your configuration. For this challenge, you will use a demo workspace and enter some configuration. When asked to write down something, please copy the value to ...

    • Configuration Experiment #V3

      Goal The goal of this experiment is to help you understand how to use custom variables in your configuration. For this challenge, you will use a demo workspace and enter some configuration. When asked to write down something, please copy the value to ...

    • Configuration Experiment #V2

      Goal The goal of this experiment is to help you understand how to use custom variables in your configuration. For this challenge, you will use a demo workspace and enter some configuration. When asked to write down something, please copy the value to ...

    • Configuration Experiment #V1

      Goal The goal of this experiment is to help you understand how to use custom variables in your configuration. For this challenge, you will use a demo workspace and enter some configuration. When asked to write down something, please copy the value to ...

    • Configuration Experiment #V4

      Goal The goal of this experiment is to help you understand how to use custom variables in your configuration. For this challenge, you will use a demo workspace and enter some configuration. When asked to write down something, please copy the value to ...