Location are targeted to 'All countires and territories' for the District, region and country seLocationlevel

There were 7 seLocationLevel are there in location table. We used all type of seLocationLevel to deploy an account (not sure in production we are using all these seLocationlevel) with production and point radii build. Here is our observation.

mysql> select distinct(seLocationLevel) from locations;
------------------

------------------

------------------
7 rows in set (0.00 sec)

seLocationlevel: district

• We deployed an account in both production and point radii build using district id(1162) as Serviceareaid in CPP and there is a discrepancy in production and point radii build.
• Production build has target location as London, England, United Kingdom (city) in Google Adwords. Please refer ProductionBuild-1162-district.jpg
• Radii build has target location as All Countries and territories in Google Adwords. Please refer PointRadiiBuil-1162-district.jpg

mysql> select * from locations where id=1162;
-------------------------------------------------------------------------------------------------------

-------------------------------------------------------------------------------------------------------

-------------------------------------------------------------------------------------------------------
1 row in set (0.00 sec)

seLocationlevel: Region

• We deployed an account in both production and point radii build using district id(1040) as Serviceareaid in CPP and there is a discrepancy in production and point radii build.
• Production build has target location as Scotland, United Kingdom (Province) in Google Adwords. Please refer ProductionBuild-1040-region.jpg
• Radii build has target location as All Countries and territories in Google Adwords. Please refer PointRadiiBuil-1040-Region.jpg

mysql> select * from locations where id=1040;
-------------------------------------------------------------------------------------------------------

-------------------------------------------------------------------------------------------------------

-------------------------------------------------------------------------------------------------------
1 row in set (0.00 sec)

seLocationlevel: Country

• We deployed an account in both production and point radii build using district id(1042) as Serviceareaid in CPP and there is a discrepancy in production and point radii build.
• Production build has target location as, United Kingdom (country) in Google Adwords. Please refer ProductionBuild-1042- country.jpg
• Radii build has target location as All Countries and territories in Google Adwords. Please refer RadiiBuild-1042-country.jpg

mysql> select * from locations where seLocationLevel like '%country%' order by id desc limit 10;
----------------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------------

----------------------------------------------------------------------------------------------------------
1 row in set (0.00 sec)

seLocationlevel: city, coverage_package, proximity, coverage_area

• We deployed an account in both production and point radii build using City, coverage_package, proximity , coverage_area ids and its working as expected i.e. adding proximity targets.