Details
-
Type: Bug
-
Status: Closed
-
Priority: Critical
-
Resolution: Duplicate
-
Affects Version/s: None
-
Fix Version/s: Bing v9
-
Component/s: None
-
Labels:None
Description
In the Bing Ad-center radii value is not updating in location target after changing the multiplier value and redeployed.
Following are the scenarios that we have tried, please find the details below
Account 1 (InvdTg2101)
Scenario 1:
Deployed a new account with radii multiplier values being 1. The radius in adcenter is 8kms and the value in campaignProximityTargetMap table is 5miles.
Scenario2:
Changed the radii multiplier value to 2 and redeployed the account. The radius value in campaignProximityTargetMap still remains 5 miles and in adcenter, an additional row of 8kms is added to location targets.
Scenario 3:
Changed the multiplier value from 2 to 1 back and redeployed the account. In adcenter, it continues to show 2 rows of 8 km as it was earlier.(there was no change in location), and the same applies to campaignProximityTargetMap table. [screenshot - TagetLocation-Multiplier(2 to 1)RD.jpg]
Scenario 4:
Changed the multiplier value from 1 to 5 and redeployed the account. On doing so, it adds another row of 8kms to the location and value campaignProximityTargetMap remains the same. [Screenshot- TagetLocation-Multiplier(5)RD.jpg]
Account 2 (InvdTg2102)
Scenario 1:
Deployed new account with multiplier value as 5. In adcenter location target section, it shows radii as 32 kms , and the value in campaignProximityTargetMap is 20 miles.[ Screenshot - TagetLocation-Multiplier(5)ND.jpg]
mysql> SELECT c.* FROM content_editor_bing.bce_campaignProximityTargetMap c , bce_campaign cp WHERE c.campaignID =cp.id and cp.name like 'InvdTg2102%';
--------------------------------------------------------------------------+
campaignID | targetID | latitudeInDegrees | longitudeInDegrees | radius | radiusUnits |
--------------------------------------------------------------------------+
1853 | 261 | 52.451454162597656 | -0.9916589856147766 | 20 | miles |
1857 | 261 | 52.451454162597656 | -0.9916589856147766 | 20 | miles |
--------------------------------------------------------------------------+
2 rows in set (0.00 sec)
Scenario 2:
Changed the multiplier value from 5 to 1 and redeployed the account. On doing so, it shows 2 rows of 32 kms each and the values in campaignProximityTargetMap remain the same. [ Screenshot - TagetLocation-Multiplier(5 to 1)RD.jpg]
mysql> SELECT c.* FROM content_editor_bing.bce_campaignProximityTargetMap c , bce_campaign cp WHERE c.campaignID =cp.id and cp.name like 'InvdTg2102%';
--------------------------------------------------------------------------+
campaignID | targetID | latitudeInDegrees | longitudeInDegrees | radius | radiusUnits |
--------------------------------------------------------------------------+
1853 | 261 | 52.451454162597656 | -0.9916589856147766 | 20 | miles |
1857 | 261 | 52.451454162597656 | -0.9916589856147766 | 20 | miles |
--------------------------------------------------------------------------+
2 rows in set (0.00 sec)
Note:
The location that we have used for our account deployment is 733. Please find its details below.
select * from pointRadius where locationID=733;
-----------------------------------------------------------
id | locationID | latitudeDegrees | longitudeDegrees | radiusMeters |
-----------------------------------------------------------
7191 | 733 | 52.451455 | -0.991659 | 4634 |
-----------------------------------------------------------
1 row in set (0.01 sec)
Attachments
Issue Links
- blocks
-
YELL-831 Global Radii Fix
- Closed