Uploaded image for project: 'AdMaxLocal'
  1. AdMaxLocal
  2. AML-5134

ABU carryover distribution assigns pooled carryover to campaigns with 0 slosh factor

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: Mars
    • Fix Version/s: Orion
    • Component/s: None
    • Labels:
      None
    • Story Points:
      3
    • Sprint:
      Sprint 1

      Description

      Steps to reproduce:
      1. Launch an account with a campaign with custom budget so that the slosh limit for this campaign is set to 0.
      2. Let ABU run for this account and distribute common and pooled carryover.
      3. The pooled carryover is calculated for each campaign and 0 pooled carryover is assigned to the custom campaign as expected.
      4. Now check the total common carryover and total pooled carryover for the account.

      Expected Behavior:
      The total pooled carryover must be equal to the total common carryover

      Actual Behavior:
      The total pooled carryover is lesser than the total common carryover.

      Reason:
      The ABU slicing mechanism considers the custom campaign having slosh limit 0, where as it should exclude that campaign from slicing. Excluding the custom campaign having slosh limit set as 0 will fix this issue and the entire common carryover will get distributed among campaigns having slosh limit > 0.

        Attachments

          Activity

            People

            • Assignee:
              Madhan Madhan Pulipati [X] (Inactive)
              Reporter:
              gurpreet.singh Gurpreet Singh
            • Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: