Expand my Community achievements bar.

Applications for the 2024 Adobe Target Community Mentorship Program are open! Click to the right to learn more about participating as either an Aspirant, to professionally level up with a new Certification, or as a Mentor, to share your Adobe Target expertise and inspire through your leadership! Submit your application today.

Geo targeting by city in the UK

Avatar

Level 2

8/20/19

We are currently unable to accurately personalise experiences on a city level in the UK. Instead, we can only personalise on a county level, however this is not granular enough for the type of experiences we want to create. It would be great if you could develop the ability to personalise on a city-level in the UK in the near future.

6 Comments

Avatar

Level 2

8/20/19

Hi Kathy,

We're looking at multiple cities in the UK. When we've consulted Adobe we've been told that: "Unfortunately, City based geo targeting is not a reliable option for the UK at the moment. Instead, we recommend setting up the audiences based on the State field which is less granular but way more accurate." I think the cities/towns you can see may relate to the cities in the US. Have you tried city-based targeting yourself? Would love to hear about any experiences you've had with it.

Avatar

Level 3

8/20/19

Hi Jamie

No, we didn't try any of those. I simply can find lots of UK cities/towns in Geo - city - matches ***. I didn't know that it's not reliable

How can we use State as we don't have states in the UK? How about using IP address?

Avatar

Level 2

8/20/19

You can find UK counties in the state field, so you can target Norfolk, Yorkshire, Cheshire etc. But we aren't able to target Norwich, Leeds, Chester etc. As far as I'm aware, IP address targeting is still only accurate on a county level. See the accuracy table on the below link:

Geo

Avatar

Level 1

10/21/20

I am having the same case but for the cities in the Philippines. We've tried a combination of long-lat and geo city. We also tried 4 points on long-lat but still didn't work. When we checked the responseTokens of our targeted page it's pulling an incorrect geo.city.