midigitalsolution
Forum Replies Created
-
Forum: Plugins
In reply to: [Sticky Header Effects for Elementor] Shrinking Down HeaderHello, this is still an issue is the most recent update. Can you please take another look? Thanks. Seems like others are making threads for the same issue.
Forum: Plugins
In reply to: [Sticky Header Effects for Elementor] Shrinking Down Header@divyangposimyth We had default settings on. I tried adding this but same issue occurs.
Forum: Plugins
In reply to: [Sticky Header Effects for Elementor] Shrinking Down HeaderWe have numerous websites this is effecting. Any assist would be appreciated.
Thank you for the clarification and for escalating this issue internally. I understand the current limitations due to the 200-account request limit imposed by Google, and that this constraint makes it challenging to manage numerous accounts under one primary Google umbrella, especially for agencies managing multiple clients.
However, this limitation places a significant burden on agencies like ours, which manage hundreds of websites, as we face frequent disconnections—often following WordPress or Elementor updates. This leads to repeated manual interventions to reconnect the proper accounts, disrupting workflow and creating unnecessary overhead.
We believe this challenge could be better addressed by:
1.Enhancing Account Retrieval: Investigating if a more dynamic retrieval system can be implemented, such as allowing selective or paginated requests from the user’s account, rather than fetching the entire account list at once.
2.Persisting Connections Post-Update: Exploring the possibility of persisting Google account connections even after plugin or CMS updates to avoid frequent disconnects.
3.Offering an Agency Mode: Developing an “Agency Mode” in the plugin that supports multiple clients, tailored for large account structures, allowing for smoother management of multiple Google accounts under one agency.
In the interim, we are considering limiting the plugin use to Search Console only, as frequent disconnections with Analytics accounts create havoc in our workflow. We appreciate the current workaround of using alternate Google accounts with fewer connections but feel this isn’t a sustainable solution for agencies working at scale.
Could this issue be flagged for further review and potential roadmap consideration? Agency support is a critical aspect, and we believe improved functionality in this area would greatly enhance the plugin’s appeal to a significant user base.
Thank you again for your support, and we hope for more robust solutions in the future.
I understand from your reply that we’re not the only ones facing this issue, and the need for agencies to have primary umbrella accounts connected won’t be addressed. Given that agencies often represent multiple clients, and our agency wants to continue supporting your product, how can this be escalated for an official review?
Restructuring an agency’s Google accounts to accommodate a plugin tweak isn’t ideal from a security perspective. I thought this plugin was designed with agencies in mind, and being recommended by agencies should carry weight. Is there any solution you can provide that doesn’t involve restructuring our entire agency to fit the plugin’s requirements?