300% mobile bid modifier change for two existing Dudamobile accounts.

Several options are available at this point:

1) Terminate the order for this merchant and create a brand new merchant in lieu of current one. This could be embarrassing for TSA to have to terminate an account just to make a change to the MBM (which is not actually supported in AML… but Duda presumably doesn’t know that).
2) Have Mark and Manasa continue testing the delete campaign(s), redeploy, add campaign(s), redeploy approach which “should” work – but has not been done before by engineering, nor TechOps, to confirm that this will undoubtedly solve the MBM issue. Additionally, this testing could take another few days. Even if this works, TechOps will then need to apply the AML-2387 workaround to this account to correct the presumably incorrect carryover due to the deletion of campaigns.
3) Manually change the MBM setting via Google AdWords UI without further testing. TechOps has done some limited testing changing the MBM directly in Google and hasn’t noticed any problems. They have also seen this work on the similar, yet slightly different, SMS platform. It would appear fairly unlikely that a manual change in the Google AdWords UI to the MBM would break AML… but it hasn’t been fully tested. This option might allow the MBM to change immediately (today) for Duda.
4) Have QA fully test changing the MBM setting via Google AdWords UI. This would require QA to be pulled from Jamestown to confirm that this approach is completely solid. The work involved would be on the order of 2 man-days QA time. Once this test is run, we could approve this to be done to any merchant going forward. This will take several days or longer – especially considering all of the India QA team is on leave next week.

Option 2 is in progress. Option 3 is a backup plan if, by Tuesday, option 2 has not proven successful.

Related TechOps ticket... https://tsasupport.atlassian.net/browse/AMLOPS-329