Title: Metricool WordPress plugin – Connection
Last modified: June 15, 2026

---

# Metricool WordPress plugin – Connection

 *  [volfan](https://wordpress.org/support/users/volfan/)
 * (@volfan)
 * [1 day, 11 hours ago](https://wordpress.org/support/topic/metricool-wordpress-plugin-connection/)
 * Hi, I’m having an issue with the Metricool WordPress plugin after the recent 
   update.
 * My Metricool brand already exists, and my website is connected/verified inside
   Metricool. I also have my tracking code, and when I click “Verify” in Metricool,
   it confirms that my website is connected.
 * The problem is on the WordPress side. In WordPress, the Metricool plugin will
   not let me access the plugin settings because it keeps asking me to “Connect 
   your brand to your website.” When I try to connect, I get the “Connect your brand”
   screen, but it fails with:
 * “There was an error fetching this data.”
 * What I have already tried:
    - Confirmed I am logged into the correct Metricool account
    - Confirmed the brand exists in Metricool
    - Confirmed the website verifies as connected inside Metricool
    - Tried the connection flow multiple times
    - Tried in an incognito/private browser window
    - Tried incognito 3 times
    - Deactivated, deleted, and reinstalled the WordPress plugin
    - Same issue after reinstall
 * The authorization flow appears to redirect me back to WordPress, but the plugin
   still cannot fetch the brand data, so I cannot get into the plugin settings.
 * Is this a known issue with the current WordPress plugin version? Is there a way
   to bypass the brand-selection screen or manually enter the tracking/brand code
   in the plugin settings? Since Metricool already verifies the website as connected,
   I’m not sure why the WordPress plugin is still requiring this connection step.
 * The page I need help with: _[[log in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Fmetricool-wordpress-plugin-connection%2F%3Foutput_format%3Dmd&locale=en_US)
   to see the link]_

Viewing 1 replies (of 1 total)

 *  Plugin Support [Jarno Vos](https://wordpress.org/support/users/jarnovos/)
 * (@jarnovos)
 * [23 hours, 1 minute ago](https://wordpress.org/support/topic/metricool-wordpress-plugin-connection/#post-18939406)
 * Hi [@volfan](https://wordpress.org/support/users/volfan/).
 * Thanks for the report. There was some scheduled downtime/maintenance on the Metricool
   application side yesterday, which appears to coincide with the time of your report.
 * Could you try reconnecting your Metricool account in the WordPress plugin by 
   logging in once more?
 * I’d expect things to work fine this time around, but just let me know if you 
   do run into any problems.
 * Kind regards, Jarno

Viewing 1 replies (of 1 total)

You must be [logged in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Fmetricool-wordpress-plugin-connection%2F%3Foutput_format%3Dmd&locale=en_US)
to reply to this topic.

 * ![](https://ps.w.org/metricool/assets/icon-256x256.png?rev=1809922)
 * [Metricool - Social media and site statistics](https://wordpress.org/plugins/metricool/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/metricool/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/metricool/)
 * [Active Topics](https://wordpress.org/support/plugin/metricool/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/metricool/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/metricool/reviews/)

## Tags

 * [api](https://wordpress.org/support/topic-tag/api/)
 * [connection](https://wordpress.org/support/topic-tag/connection/)
 * [plugin](https://wordpress.org/support/topic-tag/plugin/)
 * [WordPress](https://wordpress.org/support/topic-tag/wordpress/)

 * 1 reply
 * 2 participants
 * Last reply from: [Jarno Vos](https://wordpress.org/support/users/jarnovos/)
 * Last activity: [23 hours, 1 minute ago](https://wordpress.org/support/topic/metricool-wordpress-plugin-connection/#post-18939406)
 * Status: not resolved