Does in-built Geographic Address data use WF Units?

Hey bubblers!

Bit of an odd one here, but I am building out a complex shipping fulfilment service, and am wondering if anyone knows whether the built in geographical addresses uses WF units everytime it is requested - since it is linked to google geocoding. My current setup only uses the geocoding feature of bubble to search for addresses, but then I go and save these exact addresses as a data-type, instead of just saving the users location as a geographical address, and using :extract everytime I need to fetch their various address credentials (i.e. city, zipcode, country, etc.).

My understanding is that WU are charged if the API calls to Google are coming from Bubble’s server (e.g. run from Backend Workflows) but not from the Front End (e.g. in a dynamic expression such as a Search box with a Geographical Address, or in a page workflow dynamic expression). Front end elements as I understand it, will call Google Maps APIs directly from the user’s browser.

1 Like

I’ll be doing a bit of trial and error over the next month on testing this out. Most of my calls are backend, so I think using geolocation on frontend and pre-saved individual address credentials for backend calls might be my best bet. Will respond in this forum with my results :slight_smile:

2 Likes