devmozay

Forum Replies Created

Viewing 2 replies - 1 through 2 (of 2 total)
  • Thread Starter devmozay

    (@devmozay)

    Got some more info on this. Hopefully this helps put things in perspective.

    Here are our API stats for the past 30 days
    Geocoding API: 121,176
    Maps JavaScript API: 45,229

    Here are our user session stats for the past 30 days
    map page pageviews: 43,897
    of those, 35,361 were unique pageviews.

    About 8,500 users should have had that page cached since only 43,897 were unique visitors.

    So that means on average, each time that page was loaded (regardless of cache) it was making 2.76 geocoding API calls and a little over 1 javascript call.

    Does that sound right to you? Is there anything we can do here?

    • This reply was modified 4 years, 10 months ago by devmozay.
    • This reply was modified 4 years, 10 months ago by devmozay. Reason: updated pageview data
    Thread Starter devmozay

    (@devmozay)

    Thanks for the reply, Tijmen.

    We do have referrer restrictions on, so API usage is limited to our live site and one other site that’s still in development.

    It’s been slowly increasing week by week, and I’m trying to track down analytics with our marketing team to see if it matches user sessions on that page. I suspect that each user’s interaction is making more calls than necessary, and I’m wondering if there’s anything else we can do to minimize that.

    I’ve applied for the beta program –?that sounds like a good option. We were looking at another map solution that used OpenStreetMaps, but I was worried that it had an API call limit that we were already surpassing.

    Do you know when the beta version will be available for use? We paid over $500 last month for Google API calls and need to cut down on that cost as soon as we can.

    Thanks!

Viewing 2 replies - 1 through 2 (of 2 total)