This means that each campaign or keyword can be assigned a city. It is also possible to use the same ad texts for campaigns that refer to different cities. When creating an ad, you also open the selection here with the curly brackets and can then select the attribute you want to access under “Ad customizations”. In our case, the placeholder looks like this: {CUSTOMIZER.City:Berlin}.
The attributes for ad customization can help simplify setup and individualize ads for RSAs. However, a dynamic data feed cannot be stored for RSAs. Nor can a feed be stored that delivers different content depending on the user's location, date or time of day. At least for customization based on location, there is another solution for RSAs.
Location placeholder for RSAs
The location placeholder is only available for RSAs and can thus provide a remedy for the unusable location feed.
With the Location Ad Customizer, you can insert the user's location into the ad texts and thus personalize the ads. You can choose whether the city, state or country should be displayed.
But be careful, by using the location placeholders, all cities that senegal mobile numbers list are in the areas defined under "Locations" in your campaign can be displayed in the ad texts. Here you have to consider whether this makes sense in your case.
standard placeholder RSAs
The ad customizers offer a number of advantages. By using ad customization, you can save time and respond individually to users and their circumstances. In our experience, this leads to a significant increase in click rates and can therefore also contribute to an increase in conversions and an improvement in the cost per conversion.
Therefore: Clear recommendation to try out and use the ad customizer.
It is very annoying that the ad customizers cannot be used to their full extent with RSAs. Since the RSAs already capture a large proportion of search queries and no new ETAs can be created from June 2022, I hope that Google will soon enable the use of data feeds with RSAs.