Learn business growth with Google Analytics 4 Forums Google Analytics 4 . Google Analytics 4 – Connecting an unlimited number of properties with a Service Account

  • . Google Analytics 4 – Connecting an unlimited number of properties with a Service Account

    Posted by Henry on 17 March 2023 at 3:27 pm

    Hey there! So, here’s our situation. We’ve got a service account set up with Google Analytics 4 (GA4), but we’ve hit a bit of a snag. It seems like we’re limited in the number of properties we can tie to this account to pull data. Do you happen to know if there’s a way to link this service account to an unlimited number of properties? Or maybe there’s a different route we can take to connect through the API for accessing and pulling data for all properties under the account? Any help would really be great, thanks!

    Oh, and by the way, we have been trying to add new properties to this account, but we ran into this annoying error:
    Here’s the error we’re seeing when trying to link a new property

    Harry replied 1 year, 5 months ago 3 Members · 2 Replies
  • 2 Replies
  • Alexander

    Member
    3 June 2023 at 11:20 am

    Hey! So, the issue you’re bumping into is pretty standard. Every user, including service accounts, has a cap on the number of accounts they can access. Last time I checked, this limit was somewhere in the hundreds, which is generally more than enough for most users. You must have a lot going on if you’re hitting those numbers!

  • Harry

    Member
    28 June 2023 at 11:07 am

    Unfortunately, Google Analytics does not currently support an unlimited number of properties per service account. Each service account is tied to a specific set of properties, so you cannot connect it to all properties in your organization at once. You’ll have to manually assign the service account to each property you want to access in Google Analytics 4. As for the error you’re encountering, I am unable to assist without seeing the specific error message. I would recommend consulting Google’s support documentation or directly reaching out to their support for help with this specific issue. They might be able to resolve the issue or provide a workaround.

Log in to reply.