Should I avoid using deprecated plugins?

I want to use this plugin to track impressions of products on a marketplace (i.e. count how many times a buyer views a product listing). I noticed it is deprecated. I am ~4 months into using Bubble so I have some knowledge but not an expert.

Should I avoid using this plugin because it might run errors in the short/medium term, or is it generally ok to use deprecated plugins? Any guidance would be really valuable.

(Indeed if anyone knows of a still-current alternative plugin - let me know!)

1 Like

Depends on your risk tolerance for this particular feature.
Will it break your entire app if it fails? If so, you better get a paid plugin to increase your chances and/or be ready to hire a paid plugin maker to fix it in case it breaks.

If it is not something urgent, then feel free to use it :wink:

3 Likes

Is there a paid one you would recommend perchance?

Why not just build the marketplace click counter into the DB?

1 Like

Hi Mac2 - I can do the click counter, but not sure how I could do impressions (e.g. if a product listing shows on the screen). Could you let me know how you might approach that?

Ultimately I’m trying to build a seller analytics funnel so they can see

  • Impressions count
  • Product page visit count
  • Order count

If I understand correctly, here’s the simple way I would do it:

In the database, add a field to your product data type. Something like Impressions_Count and set it to be a number.

Whenever a user clicks a product from your main page, in the workflow that will bring them to the product page, add a step that makes a change to the parent groups product. The change is Impressions_Count = parent groups product’s impressions_count count +1.

You can even add a conditional to this step which will bypass it if the current user is an admin or someone that shouldn’t be recorded.

For product page visits, I’d some a similar database set up in the product data type. To record the page visit, add a workflow step on page load that runs a similar workflow I laid out above.

For order count, I imagine you’ll be recording orders in your database. So to get the total order of numbers, you can simply use something like parent’s groups product’s order’s count.

Hope that helps.

1 Like

Thanks mac2 - that works for the 2nd two pieces, but for Impressions what I am trying to track is the following

When a user scrolls down on the list of products (i.e. the search/filter page where you can see lots of product listings), if a particular product is shown on the screen (not necessarily clicked), I’d like to count that. I’m trying to get to the total number of times a user “sees” a listing (they don’t have to engage with the listing). Does that help in what I’m trying to do?

Hmm. I’m not too sure how you’d go about (even with a plugin).

One hacky way to do it would be to limit the product results in the repeating group to something like 12. On page load, make changes to the list of results in the repeating group adding an impression to each product.

Below the repeating group, add a ‘See More’ button which shows the next 12 products. When they click that, make changes to those items’ impressions as well.

If you want to get even more in depth, one route could be to add conditional trigger workflows based on scroll position of the page. So if the first two rows (for example) of the repeating group end at 500px, have a workflow that triggers at that point and adds impressions to the repeating groups first two items. This will be a pain because the scroll position on mobile will be different than desktop. Additionally, this is quite the heavy load for Bubble to handle. This is probably a terrible idea, but worth sharing I suppose.

At the end of the day, perhaps ask yourself how necessary the exact feature is and if there is a way to clunk it up and get similar results in a less load-bearing way for the app (like my first thought).

Hopefully someone has a perfect solution and will chime in! Good luck!

1 Like

We’re using Element Viewport Detection Plugin | Bubble, and it’s fantastic. You can track impressions for things in a repeating groups, too, and decide on whether one view per page load = 1 impression or whether an impression is counted each time the thing enters the viewport (e.g., if they scroll away, then scroll back). We’re using it for metrics on paid plans, and it’s great. Well worth the money.