How does Parker know where a record is?
A lead can have several locations that mean different things, and Parker keeps them apart. It works out what each address field means from its label and its contents.
A state picklist, such as “I’m interested in opening a franchise in VIC”, is used as a filter. It’s never a point on the map.
What about fields that could mean either?
Some fields, such as a plain Location field, might be a home address or a wanted store. Parker reads each record together with its other location fields and decides record by record. For example, a Location that matches the advertised listing is read as the advertised site. These readings are labelled read by Parker, with a confidence. An admin previews them before turning them on. See Location readings.How precise is each point?
Every result says what located it:- Street address: an exact match to a street address.
- Suburb: shows as Same suburb, or as an approximate distance.
- Postcode: placed at the postcode area.
- State only: counted, but never ranked by distance.
How does Parker stay fast and current?
Parker keeps a location index of your Salesforce records, so a typical search takes a second or two.- It builds itself. When your workspace connects Salesforce, or on your first location question, Parker indexes every record with an address in the background. A large org can take several minutes. You can keep working while it runs.
- It stays current as you use it. Each search picks up records changed since the last update, and a daily check covers the rest. New and edited addresses appear within a search or a day.
- Your first search of the day may be slower. Twice a day, Parker checks in the background that the index covers the records you can see. That first search uses a slower direct path.
- It never shows more than you can see. The index only speeds up finding candidates. Every result is checked against your own Salesforce access before you see it.
How does Parker protect your data?
- Your Salesforce permissions apply. Parker shows only the records, fields, and addresses your own Salesforce login can read. If you can’t read an object, such as Opportunity, Parker says so instead of guessing.
- Open address data comes first. Parker places addresses using the national address file (G-NAF) and Australian Bureau of Statistics boundaries. It uses Google only when that data can’t place an address, and for drive times, routes, and nearby places.
- Google’s terms apply to Google results. Distances and times worked out from Google appear on the card and map only. They never appear in Parker’s written answers, emails, or exports. Parker keeps Google locations for 30 days at most.
- Personal addresses stay off Google. Objects that hold people’s home addresses, such as franchisee applications, are placed with open data only and are never sent to Google. They’re labelled as personal addresses.
- Nothing is written to Salesforce. Locations are stored in Parker. Your Salesforce records are never changed.
What are the current limits?
- Places outside Australia. Records in New Zealand, the UK, and elsewhere are counted as outside Australia and aren’t placed.
- Uploaded files. Location search covers Salesforce records and Parker leads, not member lists or other files you upload.
- Records without an address. A record with only a state, or no address, can be counted and listed, but not ranked by distance.
- Opportunities and cases without account access. Parker locates these through their account, so you need read access to Account and its address fields.
Related
Find records near a place
What to ask, and how to read the table and map.
Location readings (admins)
Preview and turn on Parker’s readings of ambiguous fields.
What Parker can and can't do
What Parker sees, and how to check an answer.