Deep Link Builder Address Parsing Follow
Overview
In some case management systems, address fields aren’t separated into distinct HTML elements (e.g. Address Line 1, City, State, and Postal Code may exist in one <div> field). When this happens, the Ekata Deep Link Builder cannot automatically select the fields for agents to bring into Pro Insight. To remedy this problem, we have enabled custom mapping on the Primary and Secondary Address fields. This way, Admin users can insert a small code snippet (Regular Expression or “Regex”) into their team’s template so their agents can automatically parse the address fields into inputs for Pro Insight.
How to Use
To use this feature, install the Ekata Deep Link Builder from the Chrome Store. Once installed, enter your Ekata username and password. Note: We recommend logging in from the http://app.ekata.com/ domain for the first time, since some applications may block log-in attempts to browser extensions. Once logged in:
- Select Create/edit your team’s template
- For address fields that you want to parse, select Use custom mapping
- By default, some Regex will be prefilled. Here you can either modify the Regex or copy & paste new Regex over the existing Regex. Reference the Regex Building Blocks and Regex Examples below for more information.
- Once your Regex is working as expected, please Save your template
- Now your team members will see addresses automatically parse, using the Regex you created in your template.
Regex Building Blocks
Build custom Regex to parse addresses, please define your fields as the named capturing groups below, using the example snippets to parse.
|
Field |
Named Capturing Group |
Regex Snippet |
|
Address Line 1 |
address_street_line_1 |
^(?<address_street_line_1>.*?)\,\s |
|
Address Line 2 |
address_street_line_2 |
(?<address_street_line_2>.*?)\,\s |
|
City |
address_city |
(?<address_city>.*?)\,\s |
|
State |
address_state_code |
(?<address_state_code>.+)\s |
|
Postal Code |
address_postal_code |
(?<address_postal_code>.+)\s |
|
Country |
address_country_code |
(?<address_country_code>.+)?$ |
Regex Examples
Need some inspiration? Here are a few example Regex parsings you can use to get started!
|
Use Case |
Example Address |
Regex |
|
Address has line breaks in a single div |
123 Main St Seattle, WA 98101 US |
^(?<address_street_line_1>.*?)\n(?<address_city>.*?)\,\s(?<address_state_code>.*?)\s(?<address_postal_code>.+)\n(?<address_country_code>.+)? |
|
Address is in a single line without breaks |
123 Main St, Seattle, WA 98101 US |
^(?<address_street_line_1>.*?)\,\s(?<address_street_line_2>.*?)\,\s(?<address_city>.*?)\,\s(?<address_state_code>.+)\s(?<address_postal_code>.+)\s(?<address_country_code>.+)? |
|
Address does not contain state/region info |
Rudolstaedter Strasse 86, Rheine 48431 DE |
^(?<address_street_line_1>.*?)\,\s(?<address_city>.*?)\s(?<address_postal_code>.+)\s(?<address_country_code>.+)? |
Need Some Help?
Let us know! (Contact Support)
Comments
0 comments
Please sign in to leave a comment.