Lara Google Analytics - Support

Hello @power33,

Could you please let me know the plugin name, so that I can test it, and see what was going wrong ?

Hello @whateverfree2,

It seems that, you have created a Google APP with “Web Application” type.

When creating your Google App, be sure to choose “Other” instead of “Web Application”, in the “Application type” menu.

Hello @power33,

Are you using Disable admin notices individually plugin ?

Hello @mmcginnis,

I have no idea how GADWP flow works, but for our widget, things are different.

When you authorize a google account and enable tracking, the tracking profile will be saved locally in the WordPress database, and will be served from there.

If the authorization was revoked from Google Analytics website, the widget will no longer be able to fetch data, but the tracking code will remain intact.

The only way to change or disable the tracking code [after initial authorization], is from the widget’s settings tab.

Furthermore, with the upcoming version, there will be an option to lock settings by an administrator, which will prevent your clients from changing them, even if they have access to the settings tab.

Great, expect this to be included in the next update, which should be released within the next few days.

Stay tuned, as it will also include some awesome features.

Just a quick thought, if we added an option to lock the account/view, with a notice explaining that, if the user has access to the database or files, and some technical knowledge, he/she will be able to overcome the restriction, will that be sufficient ?

• This reply was modified 4 years, 9 months ago by Lara Google Analytics - Support.

Hello @smhcis,

The moment you authorize any app to connect to your GA account, and the “access_token” is saved in your client’s WordPress database, you are essentially giving him/her access to “read” the entire account’s data.

The way the other plugins are forcing you to re-authorize doesn’t change this fact.

Before the re-authorization, the access_token was in the database, and after the re-authorization, the new access_token will be also saved in the database.

So, to keep things really secure :

1 – If you are hosting your clients websites, then you can give them a role other than administrator, and restrict their access to prevent them from installing plugins or accessing the database (then you can use our plugin’s permission tab, to restrict their access to the plugin’s settings).

2 – If you are not hosting their websites, then, give them restricted access to your GA views, as discussed before, which will require them to have a google account (btw, they can create a google account using their own, non-gmail email address).

I hope it is clear now.

Hello @milouze,

If you are giving your clients Administrator rights, they can edit plugins files and database records, as they will have full control over the WordPress installation.

Also, If you enforced the permissions via some code in wp-config, they can easily install a plugin, and edit the file to remove any restrictions.

The only way-out I see, is to give them a role that will not allow them to manage/install plugins.

[ Signature deleted ]

• This reply was modified 4 years, 9 months ago by Jan Dembowski.

Hello @milouze,

Yes, this can be done with our pro version.

Since version 3.0, you have full control on users permissions, including the ability to stop them from accessing the settings tab completely (works also with multi-networks and multi-sites).

So, for your customers, assuming they have the Editor – or any custom – role, you as the Administrator can go to the permissions tab and disable both “Super Administrator [Change Permissions]” and “Administrator [Change Settings]” permissions for their role , as in this image.

Now, they will only have access for viewing the other tabs, without the ability to even see the settings/permissions tab.

[ Signature deleted ]

• This reply was modified 4 years, 9 months ago by Jan Dembowski.

Hello @nesoor,

Thank you for your nice words ??

We are working on our premium update service, and will let you know as soon as it is ready.
[ Signature deleted ]

• This reply was modified 4 years, 9 months ago by Jan Dembowski.

Hello @steingoesnorth,

I am happy to inform you, that we have just release version 3.0.0 of the widget, which supports full control over roles permissions [Pro version only].

[ Signature deleted ]

• This reply was modified 4 years, 9 months ago by Jan Dembowski.

Hello @alangautham,

Could you please update to the latest version (2.0.7) and see if the problem persists ?

We have pushed v2.0.7 for both, our free and pro versions of the plugin.

[ Signature deleted ]

• This reply was modified 4 years, 9 months ago by Jan Dembowski.

Hello @ericbuzin,

Could you please update to the latest version (2.0.5) and see if the problem persists ?

We have just released an update, to do further checks on POST variables.

[ Signature deleted ]

• This reply was modified 4 years, 9 months ago by Jan Dembowski.

@radev,

You can go to the settings tab, then click on “Reset all data and start over”.

This will reset the widget data, and then you may connect your new google analytics account.

Thanks,
Lara Team.

Hello @alangautham,

Thank you so much for your nice words ??

I have replied to your support question, in the support thread.

[ Signature deleted ]

• This reply was modified 4 years, 9 months ago by Jan Dembowski.