Allow comma-separated values for segment search
Using a range for zip codes isn't precise enough. Pasting a comma separated value list or importing an XML to the rule logic would help. The goal would be to create segments for each of the shipping zones from our warehouse to custom message customers of when our shipping cutoff dates and times are for their specific mailing address for the holiday season. GeoIP is not exact enough either.
Kristine McNerney commented
Hello - Our team is in need of this to use for zip code segmentation, is there any update on when this is going to be put into action/development?
Import/Upload a .csv list to a Segment Rule!
For example, if i wanted to create a segment that included or exluded a list of Shipping Post Codes or Suburbs, you should be able to upload a .csv (or similar) list into the rule, rather than manually typing potentially hundreds or thousands of post codes/suburbs.
Geo IP is unreliable.
Want to be able to send to contacts within a certain radius from a zip code. Other automation platforms allow you to upload a list via spreadhseet and have a segment created if the value for the zip code matches a zip code in the uploaded file. Looking for the same functionality as opposed to manually entering zip codes one by one.
I'm building a segment and have a batch of data (approx. 400 entries) that I would like to enter into my builder. The use case for this is external data analysis that is completed and results in a list of postal codes/zip codes being outputted.
I would like to easily paste this batch of post codes into segment builder. The paste string can be comma separated if required.
Since the UI doesn't allow for this, a simple pop up box would suffice where the string can be pasted into.
Charlotte McMullan commented
Similar to GeoIP segments it would be good to base segments around distance from the customers postcode, address based rather than where they open emails.
Daria Ragonese commented
We create zipcode based segments for our stores. We'd like to suggest an enhancement that will allow you to upload a CSV file containing the data being used to define new segment. In our case it would be a list of zipcodes that are uploaded rather than having to enter each one individually.
Viktor Beall commented
Reference: Support Case #: 00108185
There is (in my opinion) a huge issue with targeting customer zip code information, for which we would prefer a fix asap.
We collect zip code information outside of Bronto's internal geo-tracking and use this customer-supplied geographic information to target based on location. There is a problem however, because the bronto supplied ZIP field is a text field, you cannot target a range. To input every single zip code is way too time intensive and unrealistic; there are thousands of zips.
My solution for this was to create a numerical field for zipcode targeting purposes. The way I target ranges is to have rules that say grab records with a zipcode that's "greater than x; but less than y". This worked ok until I saw 2 issues.
One being that all leading 0's are removed, and the range doesn't incorporate 9 digit zips as well. Thus, when a customer goes to their preference center, they could hypothetically just see 2-3 digits if they have several leading zeros. This is confusing for our customers. Another issue is that when a user loads their preference center, Bronto automatically adds a comma after 3 digits in number fields. While this is incorrect of a zipcode, the worst issue is that if a customer goes to save their preference center, they are not able to because of the comma that bronto injects into the number field after 3 digits. Thus, even though the customer does nothing wrong but load their preference page, bronto adds a comma upon load which prevents the customer from savng their preferences altogether (unless they remove it).
I see a few solutions:
1. remove formatting for numerical fields
2. create a zipode-specific field that resolves these issues as zip fields would be handled differently.
3. add range targeting to text fields.
We've also come across this issue. We mail customers local to our stores based on a drive time from our postcode, GeoIP with mileage isn't accurate enough.
It would be excellent to have the ability to import a list or manually create a statement (IF POSTCODE CONTAINS x OR x OR x...) to produce the segment.
Copying/pasting each postcode individually into the segment builder is a long old task.
I, too, had this problem. I was hoping that regular expressions would solve this problem, but a csv would be an option: http://ideas.bronto.com/forums/74207-ideas/suggestions/3293157-segments-allow-field-matching-by-regular-expressi
Jon Morgan commented
Bumping this one. We just joined Bronto and while I love just about everything else, this is one thing that I feel is a hinderance. We are a southern California business that targets SoCal addressees for our local events. I have a list of 60+ zip codes that currently have to be setup across 3 separate segments. Then when we send the email, we send it to all three segments. I'm definitely glad that a workaround like this exists but it sure would be nice to expand the segments to allow more than 20 values.
When creating a segment, it would be really helpful if we could match field certain values by using a regular expression (regexp). This would have saved me from adding a bunch of or's to our segment.
Regular expressions are powerful and (in the right hands) can save a lot of time.