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

Incorrect Slosh Factor calculation at distribution level for Bing

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Not a Bug
    • Affects Version/s: Mercury
    • Fix Version/s: Mercury
    • Component/s: Campaign Service
    • Labels:
      None
    • Environment:

      Core #342
      Bidmgr #743

    • Sprint:
      Sprint 3, Sprint 4

      Description

      Incorrect Slosh Factor calculation at distribution level for Bing

      1) Set the Slosh Factor as follows
      SELECT * FROM `st-tracker`.admaxSloshFactors
      id elementType elementID startDate endDate sloshFactor
      1 global 0 2012-01-01 \N 1
      2 distribution 147 2015-01-01 \N 0.4

      2) Deployed an order and ran admax.sh for 2 days
      SELECT * FROM `st-tracker`.admaxActualDailyBudgets WHERE admaxCampaignID IN (989)
      id admaxCampaignID type date budget
      5430 989 boosted 2015-07-13 6.12903
      5431 989 boosted 2015-07-14 12.2581
      5432 989 boosted 2015-07-15 18.3871

      SELECT * FROM `st-tracker`.admaxCarryovers WHERE admaxCampaignID IN (989);
      id admaxCampaignID type date dedicatedCarryover commonCarryover pooledCarryover
      5448 989 boosted 2015-07-13 0 0 0
      5449 989 boosted 2015-07-14 3.67742 2.45161 2.45161
      5450 989 boosted 2015-07-15 7.35486 4.90324 4.90324

      => As expected a slosh factor of 0.4 is applied to common carryover.

      3) Changed the Slosh Factor as follows
      SELECT * FROM `st-tracker`.admaxSloshFactors
      id elementType elementID startDate endDate sloshFactor
      1 global 0 2012-01-01 \N 1
      2 distribution 147 2015-01-01 \N 0.7

      4) Ran abu for the rest of the days
      SELECT * FROM `st-tracker`.admaxActualDailyBudgets WHERE admaxCampaignID IN (989)
      id admaxCampaignID type date budget
      5430 989 boosted 2015-07-13 6.12903
      5431 989 boosted 2015-07-14 12.2581
      5432 989 boosted 2015-07-15 18.3871
      5440 989 boosted 2015-07-16 24.5161
      5441 989 boosted 2015-07-17 30.6451
      5442 989 boosted 2015-07-18 36.7741
      5443 989 boosted 2015-07-19 42.9031
      5444 989 boosted 2015-07-20 49.0321
      5445 989 boosted 2015-07-21 55.1611

      SELECT * FROM `st-tracker`.admaxCarryovers WHERE admaxCampaignID IN (989);
      id admaxCampaignID type date dedicatedCarryover commonCarryover pooledCarryover
      5448 989 boosted 2015-07-13 0 0 0
      5449 989 boosted 2015-07-14 3.67742 2.45161 2.45161
      5450 989 boosted 2015-07-15 7.35486 4.90324 4.90324
      5456 989 boosted 2015-07-16 9.19356 9.19354 9.19354
      5457 989 boosted 2015-07-17 11.0323 13.4838 13.4838
      5458 989 boosted 2015-07-18 12.871 17.7741 17.7741
      5459 989 boosted 2015-07-19 14.7097 22.0644 22.0644
      5460 989 boosted 2015-07-20 16.5484 26.3547 26.3547
      5461 989 boosted 2015-07-21 18.3871 30.645 30.645

      Actual Result:
      Different Slosh Factors are applied for each day.
      0.5 for 16th
      0.55 for 17th
      0.58 for 18th
      0.6 for 19th

      Unstable as it works fine sometimes and sometimes the percentage of Slosh Factor applied is unpredictable.

      Expected Result:
      I am expecting 0.7 to be applied for all

      I tried to bounce the server and worked again. Still the same.

        Attachments

          Activity

            People

            • Assignee:
              varshini.padmanabhan Varshini Padmanabhan (Inactive)
              Reporter:
              varshini.padmanabhan Varshini Padmanabhan (Inactive)
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: