API error

  • Resolved plainrane

    (@plainrane)


    1 year, 4 months ago

    I just started seeing this error in the admin dashboard today:

    Google Analytics for WordPress by MonsterInsights failed to retrieve the new report data. Error message: Non numeric shard id returned: “shard0” in go/debugonly input_key { property_key { property_id: xxxxxxx } } status: ALLOWED internal: false shard { explicit_shard_spec { reporting_shard { shard_name: “shard0” } processing_shard { shard_name: “shard0” } } } translated_key { property_key { account_id: xxxxxxxxx property_id: xxxxxxxx entity_id: xxxxxxx } } . Either this isn’t a Gold property or it hasn’t been migrated yet and you should specify a scion_profile_id instead.; on /bns/it/borg/it/bns/analytics-be-reporting-service-prod-jobs/reporting-service-prod.server/10

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Support Michelle D.

    (@devmich)

    Hi @plainrane,

    Thanks for reaching out. I’m sorry for the trouble here.

    To ensure you continue to have access to analytics data, it is necessary to create and authenticate a GA4 property, as Google Analytics is sunsetting the older UA-style properties.

    To create a new property for your website, please follow the instructions provided in the following link: How to Add a Property in Google Analytics.

    Once you have successfully created the GA4 property, you will need to reconnect MonsterInsights to Google Analytics. This process is quick and straightforward.

    You can find detailed steps in this link: Connecting MonsterInsights to Google Analytics.

    Please note that when transitioning to a new property, there may be an initial delay of 24-48 hours before data is visible in Google Analytics. Rest assured that no data will be lost, and your website will continue to be tracked during this time.

    If you have any questions or concerns throughout this process, please don’t hesitate to let us know.

    Thank you,

    Thread Starter plainrane

    (@plainrane)

    Awesome, thanks. I had dual tracking setup, so assumed it would just switch automatically.

    Same.

    Have dual tracking setup also and assumed no further action was required. Is this not the case?

    Plugin Support Tim H

    (@tharg3)

    Hi @plainrane and @jesseislil,

    This issue affecting users who were dual tracking in reverse to what was recommended. This means using UA as primary and GA4 as secondary, rather than the other way around.

    Because the API endpoints for UA are pretty much gone at this point, your version of MonsterInsights is trying to still reach what is no longer there.

    To resolve this, please make sure you are updated to the latest version of MonsterInsights, and authenticate into Google Analytics once again.

    Thanks,
    Tim

    Plugin Support Michelle D.

    (@devmich)

    Hi @plainrane,

    We haven’t heard back from you in about a week, so I’m going to go ahead and close this thread for now. But if you’d like for us to assist further, please feel welcome to continue the conversation.

    Thanks!

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘API error’ is closed to new replies.