Matt,
I don't believe this will affect your use case, but, because you mention consuming a Google API within ArcGIS, I wanted to share a word of caution for anyone who may come across this thread...
Carefully read through the Google API TOS... you may find quite a few constraints that make it very difficult to use outside of the Google ecosystem. Take, for instance, the geocoding API... It is strictly for non-commercial, proof-of-concept usage. To use it commercially, you would need to purchase a Google for Work license (minimum 10-20k), and, on top of that, all of the lat/longs you receive from the API absolutely, positively, cannot be used outside of a Google map. That is, you couldn't consume the API and display the points on an Esri basemap, or any map for that matter (aside from Google's map)!
As a matter of fact, they are wary about letting you store the points in a db, too, and only give the go ahead if you make a case for performance needs - they actually want you to geocode your addresses every time you need to display them (on a Google map), which, of course, uses credits.
The reasoning behind this, according to Google, is to maintain a unified user-experience. They want the user to receive up-to-date data and do not want to be associated with any misalignment of features. Honestly, it's a disconnect between what business users need and what Google is willing to offer - fortunately, there are alternatives (like Esri's geocode service).
