Configuration Experiment #C2

Configuration Experiment #C2


Goal
The goal of this experiment is to help you understand how configuration changes impact crediting. For this challenge, you will use a demo workspace and alter the 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.

Steps
  1. Create a demo workspace
  2. Go to Calculations > All Calculations
  3. Open the calculation
  4. Go to the Alerts tab
    1. How many warnings do you see?
  5. Go to the Credits tab
  6. Write down how many transactions were credited to "Daniel Martinez"
  7. Click on "Daniel Martinez" to view credited transactions
  8. Click on any transaction to edit it
  9. Change the "Sold By" from "danielmartinez@example.com" to "HELLO" (upper case)
    1. What do you think this will do?
  10. Save and select "Allow Overwrites"
  11. Go to Calculations > All Calculations
  12. Re-run the calculation (with delete)
  13. Open the calculation
  14. Go to the Alerts tab
    1. How many warnings do you see?
    2. What does the warning mean?
  15. Go to the Credits tab
  16. Write down how many transactions were credited to "Daniel Martinez"
    1. Is the new total different from your previous one?
  17. Go to Users > All Users
  18. Edit user "Daniel Martinez"
  19. Go to the Aliases tab
  20. Add an alias of "hello" (lower case)
    1. What do you think this will do?
  21. Go to Calculations > All Calculations
  22. Re-run the calculation (with delete)
  23. Open the calculation
  24. Go to the Alerts tab
    1. How many warnings do you see?
    2. Why is the warning gone?
  25. Go to the Credits tab
  26. Write down how many transactions were credited to "Daniel Martinez"
    1. Is the new total different from your previous one?
  27. Go to Users > All Users
  28. Edit user "Eric Smith"
  29. Go to the Aliases tab
  30. Add an alias of "heLLO" (mixed case)
    1. What do you think this will do?
  31. Go to Calculations > All Calculations
  32. Re-run the calculation (with delete)
  33. Open the calculation
  34. Go to the Alerts tab
    1. How many warnings do you see?
    2. What does the warning mean?
  35. Go to the Credits tab
  36. Write down how many transactions were credited to "Daniel Martinez"
    1. Is the new total different from your previous one?
  37. Go to Plans > All Plans
  38. Edit plan "One-Off Sales Contest"
  39. Go to the Targets tab
  40. Choose "If Multiple Users Match" = "Assign Full Credits To All Users"
    1. What do you think this will do?
  41. Save plan changes
  42. Go to Calculations > All Calculations
  43. Re-run the calculation (with delete)
  44. Open the calculation
  45. Go to the Alerts tab
  46. How many warnings do you see?
    1. How many warnings do you see?
    2. Why is the warning gone?
  47. Go to the Credits tab
  48. Write down how many transactions were credited to "Daniel Martinez"
    1. Is the new total different from your previous one?
  49. Go to Aliases > Review Aliases
  50. Click on "View User Aliases"
  51. Search for "hello"
    1. How many entries do you see?
  52. Clear the search criteria
  53. Check "Only Duplicates"
    1. How many entries do you see?

Key Learnings
  • You can credit users via aliases
  • Aliases are case-insensitive
  • Setting the same alias on multiple users can result in multi-user crediting
    • Assuming those users with the alias are plan targets
  • Plan-level configuration options control how multi-target crediting behaves
    • Ex: assign full credit to each credited target
  • There is a tool to review aliases and find duplicates

    • Related Articles

    • Configuration Experiment #D1

      Goal The goal of this experiment is to help you understand how configuration changes impact transactions. For this challenge, you will use a production workspace and enter some configuration. When asked to write down something, please copy the value ...

    • Configuration Experiment #V6

      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 production workspace and enter some configuration. When asked to write down something, please copy the ...

    • Configuration Experiment #D2

      Goal The goal of this experiment is to help you understand how configuration changes impact transactions. For this challenge, you will use a production workspace and enter some configuration. When asked to write down something, please copy the value ...

    • Configuration Experiment #D3

      Goal The goal of this experiment is to help you understand how configuration changes impact transactions. For this challenge, you will use a production workspace and enter some configuration. When asked to write down something, please copy the value ...

    • 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 ...