We often like to use a shortened version of an address in automations.
There are many uses, but one easy example is to send an automated message to a lead stating âAre you interested in selling 123 Main Street?â
This format is better than âAre you interested in selling 123 Main Street, Somewhere City, Big State, USA 88888?â
In the automations, Tape shows the ability to âdrill downâ on address field components and supposedly grab just the âStreet Onlyâ line of the address as shown below.
Unfortunately, this consistently comes back as a mixed up/incorrect value.
For example with
123 Main Street, Somewhere City, Big State, USA 88888 the Street Address variable comes back as
âMain Street 123â rather than â123 Main Streetâ
With a ârealâ example - for â1600 Pennsylvania Avenue NW, Washington, DC 20500, USAâ the Street Address variable comes back as
âPennsylvania Avenue Northwest 1600â
but we want to see it as â1600 Pennsylvania Avenue Northwestâ
thanks for bringing this to our attention. This is most likely a localisation issue, as some countries prefer the number to be in front, and some after listing the street. I will look into this and post the solution here once I have it.
@CarsonRedCliffLabs I went back and investigated this, and indeed the street address had not been localized properly in the past, which would yield invalid results for countries such as the US, where the number is in front.
We just deployed a fix for this, and US addresses should now be formatted properly when using the âStreet addressâ token. Kindly confirm this resolves your issue. Note that you will need to update those location fields first once (to regenerate the map and meta info).
Cheers & thank you for bringing this to our attention.
Tim
Hi @Tim , I have the same iusse but my location is Australia. Is is possible to deploy a fix for Australia to have the street number at the front?
Thanks, Matt