Hi ​@KazooCat, Welcome to the community!

This is a common one, sections often look great on desktop but doesn’t scale well for mobile.
this carousel is a prime example.

The easiest workaround is to duplicate the section and use Klaviyo’s Display settings to show:

• one version on desktop only (The Current Version)

• and a separate, cleaner version on mobile only (either showing 1 review at a time maybe as a gif or having them all stacked vertically in a different style)

This can be done by going to the Display tab and select “Desktop only” for one and “Mobile only” for the other.
---------
I will also add that i am seeing that a lot of merchants are leaning into mobile-first content now, especially since most traffic is mobile anyway, plus Desktop email width is still capped around 600px so the viewport is still small in comparison to that of a desktop website.

What works for mobile tends to work everywhere, where as what works on desktop often does not translate to mobile. I would also say it is worth checking your mobile vs desktop % to guide how much time you spend on each version!

Hope that helps

Thanks
Tim

Hello ​@TimMartinHarvey,

Thank you for commenting on my question. After a few minutes of trying to find the display tab in my shopify site theme editor. I realized I was not specific in my original question. Which is my mistake, sorry about that.

I am applying the Klaviyo widget “Featured Reviews Carousel” to my shopify website in the Fabric Theme.
Having the same display tab for that would be so wonderful 

While I did not clarify for my current question, knowing I can use hide/show logic in my Klaviyo email marketing is really helpful!

Thank you!
KazooCat

I tried again and made some progress, but it was still not working well after an hour. I decided it was faster for me to make a custom section and add images where I add the reviews. I'll be removing that widget since it is not properly optimized for mobile websites for some reason, and would take a lot of troubleshooting to do something that should be a part of the widget in the first place.