Actually, I'm just going to copy/paste what I wrote to Google. See below:
To briefly explain the setup:
- My website is a search engine.
- We add listings imported from a spreadsheet with the location (suburb, state) auto-filled into a custom field on the website.
- Those listings automatically 'link' with Google maps. (I haven't tested what happens if we make a spelling mistake, yet)
- On the front-end: people can then search their local area (X kilometers from Y center-point) for all the listings in our database listed at those locations. - (Geolocation and, I think, autocomplete APIs, or Places API, or whichever it is)
- On the search results page is even a map that has 'pin points' on it, dynamically showing the results on that page. (Geocoding? Dynamic API?)
- If a person clicks on a listing for more information about that specific one, the content template has a map on it, too. (Embed API)
And now, for some screenshots:
This is the front-end search function: (zoomed out to fit and map-relevant sections circled)
(I made a video instead of images for you guys, for Toolset) - hidden link
And the front-end of a single entry: (also zoomed out and circled)
(See Video)
This is the code/setup I'm using for Embed Maps:
(See Video)
The actual code, itself, is:
"<iframe width="1800" height="250" style="border:0" loading="lazy" allowfullscreen="" referrerpolicy="no-referrer-when-downgrade" src="hidden link
field='suburb-of-offender' output='raw'][/types]
</iframe>"
_
So, basically, someone will search an area and then click through multiple listings in that area - Meaning 1 Geo/Place/Dynamic API usage per 1-40 Embed API usage. (up-to 40 results per page)
And, actually, now that I think about it. If someone clicks OFF the search page (eg. to a listing) and then clicks the BACK button (to go back to the search results) will that count as one or two Geo/Paces/Dynamic API usages? (If two, would 'opening in a new tab' make it into just one?)
But, regardless, if there's zero Embed API usage, but the maps are still working on the pages, that's a big problem; I'm probably being charged at the Dynamic API rate.
_
My only last thought is that on the individual pages (screenshot 2), in the smaller drawn circle ("Blue Mountains" in this case) - is THAT using the "Dynamic API" because it's part of a template that dynamically pulls the content from the custom post type? It's the source for the Embed API map above it; could it be somehow using the Dynamic API (keeping in mind the 'import' function I explained above - how we just import the address field and Google somehow automatically attaches the map location to it)
_
Anyway, I wanted to be as thorough as I could be. Let me know if there's anything else I can do to get to the bottom of all this.