Enable caching to optimize the number of views

Ask the Community General Questions
1

This is a feature offered by competing solutions:
In order to optimize the number of views and minimize what counts as one view, a setting could be added to enable image caching with a drop-down list, for example 1 hour/6 hours/24 hours.

Some examples:

  • When 24 hours is selected, 1 user who views the feed 10 times in 24 hours is counted as 1 view.
  • When 1 hour is selected, 1 user who views the feed 10 times in 2 hours is counted as 2 views.
  • etc…

What do you think?

1 Like
3

Hi there and welcome to the Community, @user20361 :waving_hand:

Thanks a bunch for the feedback!

You’re right, each view equals one code loading. However, the thing is that each time the widget loads on the website, it also produces a load on our servers. Thus, we simply cannot remove this restriction, increase the current limits or change the views counting logic

However, to make up for it, we decided not to restrict any of the widgets’ features and settings for any of our customers, even those who use the Free plan. We have done it specifically in order to let our customers test the widgets’ functionality in full, before making the decision about upgrading to a paid plan.

I hope this explains the reasons behind the view limit. We rely on your understanding.

If you have any further questions, we’ll be happy to help :slightly_smiling_face: