{"_id":"582c7059e4a4920f00ff006b","parentDoc":null,"category":{"_id":"582c7058e4a4920f00ff004a","version":"582c7058e4a4920f00ff0045","__v":0,"project":"56c1e50bce02590d006091c9","sync":{"url":"","isSync":false},"reference":false,"createdAt":"2016-02-15T15:12:43.416Z","from_sync":false,"order":3,"slug":"faqs","title":"FAQs"},"version":{"_id":"582c7058e4a4920f00ff0045","project":"56c1e50bce02590d006091c9","__v":2,"createdAt":"2016-11-16T14:42:32.468Z","releaseDate":"2016-11-16T14:42:32.468Z","categories":["582c7058e4a4920f00ff0046","582c7058e4a4920f00ff0047","582c7058e4a4920f00ff0048","582c7058e4a4920f00ff0049","582c7058e4a4920f00ff004a","582c7058e4a4920f00ff004b","582c7058e4a4920f00ff004c","582c7058e4a4920f00ff004d","582c7058e4a4920f00ff004e","582c7058e4a4920f00ff004f","582d97124b2536250038b392"],"is_deprecated":false,"is_hidden":false,"is_beta":false,"is_stable":true,"codename":"","version_clean":"3.0.0","version":"3.0"},"user":"5758182a6a65ec0e004152d1","project":"56c1e50bce02590d006091c9","__v":0,"githubsync":"","updates":[],"next":{"pages":[],"description":""},"createdAt":"2016-06-09T14:59:51.749Z","link_external":false,"link_url":"","sync_unique":"","hidden":false,"api":{"settings":"","results":{"codes":[]},"auth":"required","params":[],"url":""},"isReference":false,"order":7,"body":"This property contains the split and cleaned (for some countries) version of the customer address field. For example, Address and GeolocationAddressParts properties together will look like:\n\n[block:code]\n{\n  \"codes\": [\n    {\n      \"code\": \"...\\n\\\"CustomerInfo\\\"\\n{\\n    \\\"Address\\\" : \\\"Address Line 1#Address Line 2#Address Line 3\\\",\\n    \\\"GeolocationAddressParts\\\": [\\\"AddressLine1\\\", \\\"AddressLine2\\\", \\\"AddressLine3\\\"]\\n}\\n...\",\n      \"language\": \"json\"\n    }\n  ]\n}\n[/block]\nThe reason of this property is to reduce the failures while getting the Geolocation of the customer address by pre-splitting the address field and remove unnecessary texts which would not be useful for getting the geolocation (e.g: buzzer/buzz). \nFor getting the customer geolocation, we suggest using GeolocationAddressParts property with re-tries. Example: \n\n  * First call: **Address Line 1, Address Line 2, Address Line 3, Post Code, City**  ==> Failure\n  * Second call: **Address Line 1, Address Line 2, Post Code, City** ==> Failure\n  * Third call:     **Address Line 1, Post Code, City**","excerpt":"","slug":"geolocationaddressparts-1","type":"basic","title":"A note on address matching"}

A note on address matching


This property contains the split and cleaned (for some countries) version of the customer address field. For example, Address and GeolocationAddressParts properties together will look like: [block:code] { "codes": [ { "code": "...\n\"CustomerInfo\"\n{\n \"Address\" : \"Address Line 1#Address Line 2#Address Line 3\",\n \"GeolocationAddressParts\": [\"AddressLine1\", \"AddressLine2\", \"AddressLine3\"]\n}\n...", "language": "json" } ] } [/block] The reason of this property is to reduce the failures while getting the Geolocation of the customer address by pre-splitting the address field and remove unnecessary texts which would not be useful for getting the geolocation (e.g: buzzer/buzz). For getting the customer geolocation, we suggest using GeolocationAddressParts property with re-tries. Example: * First call: **Address Line 1, Address Line 2, Address Line 3, Post Code, City** ==> Failure * Second call: **Address Line 1, Address Line 2, Post Code, City** ==> Failure * Third call: **Address Line 1, Post Code, City**