Social share buttons: do people still share products? (Yes, but differently)

Open a fresh PrestaShop install and you'll notice something: depending on your version and theme, the product page may not expose a "share this product" button by default. It's worth being precise about which module does what. PrestaShop ships ps_socialfollow in the footer, links to your Facebook and Instagram accounts, but that is the opposite of what people mean by share buttons. It points customers away to your profiles; it doesn't let them send a product to a friend. The actual product-sharing module is a separate one, ps_sharebuttons, and many installs don't ship or enable it. So the real question isn't "are the default share buttons worth keeping". On plenty of stores there are none to keep. It's "do people still share products at all, and if so, which mechanism actually earns its place on the page?" The honest answer is yes, they share more than ever, but almost none of it looks like the Facebook-wall sharing those old buttons were built for.

This guide is specifically about share buttons on a PrestaShop store: where sharing actually happens in 2026, which buttons get clicked, where to put them in the theme, and how to add them without dragging three tracking scripts onto your product page. It's the share-mechanism piece of the wider cluster. For which networks are worth your marketing time, see which social platforms actually drive sales.

Last updated: June 2026.

The shift: from broadcast sharing to dark social

A decade ago a "share" meant a public broadcast, a post on someone's Facebook timeline, a tweet, a Pin. That behaviour has collapsed. Most product sharing today happens in private channels: WhatsApp, Messenger, iMessage, a copied link pasted into a group chat, an email to a partner. The industry calls this dark social, and the name describes the analytics problem precisely: a friend opens the link your customer sent and arrives at your store with no referrer. In GA4 that visit lands in Direct traffic, indistinguishable from someone typing your URL. It's real, often substantial traffic that your reports systematically under-credit.

The "so what" for a store owner is concrete. If your product pages only carry Facebook, X and Pinterest buttons, you are putting buttons in front of customers for the channels they've largely stopped using, and offering nothing for the channels they actually share through. You're not just missing clicks, you're spending page weight and screen space on the wrong mechanism.

Which share buttons actually get clicked

Click rates on share buttons are low everywhere, a single-digit percentage of visitors at best, so the goal isn't a wall of icons, it's the two or three that match how your customers behave. Rough order of usefulness for a typical store, calibrated to product type:

The pattern: two universal buttons (WhatsApp, Copy link) plus one or two matched to your catalogue (Pinterest for visual, Email for considered) cover the overwhelming majority of real sharing without cluttering the page. Pinterest deserves its own note here because it behaves unlike any other share. A Pin sits on a board and keeps sending traffic for months. We make the full case in Pinterest for e-commerce; if visual discovery is your game, that channel earns more than just a share button.

Build the buttons as plain links, no JavaScript widgets

This is the decision that separates a fast share button from a slow one. Each platform offers an "official" share button. A JavaScript snippet that, when added, can pull in third-party JavaScript, an iframe and extra network requests, often with cookie and consent implications. Three official buttons can mean several extra third-party requests on every product page, hurting the Core Web Vitals Google now weighs. You don't need any of it. Every share action you actually want is a plain URL the browser opens, zero scripts, zero external requests, zero cookie-consent implications:

• WhatsApp: https://wa.me/?text= followed by the URL-encoded product link.
• Pinterest: https://pinterest.com/pin/create/button/?url=...&media=...&description=..., pass the product image URL as media so the Pin carries the photo.
• Email: mailto:?subject=...&body=..., opens the customer's own mail client.
• Copy link: a one-line navigator.clipboard.writeText() call on click. The only JavaScript you need, and it's a single browser API, not a third-party script.

Because these are ordinary anchors, they belong in the theme directly. The clean integration point is a hook on the product page. displayProductAdditionalInfo renders just under the price/add-to-cart block, and displayReassurance sits in the reassurance area; either keeps the buttons in front of the customer without editing core. If you'd rather hard-place them, the markup goes in themes/your-theme/templates/catalog/product.tpl (or the relevant product-add-to-cart.tpl partial), reading the link as {$product.canonical_url} and the image as {$product.cover.large.url} so each button shares the canonical URL rather than a filtered or paginated variant.

Here is the whole set as plain Smarty in a product template, no third-party scripts, the only JavaScript being the one-line clipboard call for copy-link:

{assign var=shareUrl value=$product.canonical_url|escape:'url'}
{assign var=shareImg value=$product.cover.large.url|escape:'url'}
{assign var=shareTxt value=$product.name|escape:'url'}

<a href="https://wa.me/?text={$shareUrl}" target="_blank" rel="noopener">WhatsApp</a>
<a href="https://pinterest.com/pin/create/button/?url={$shareUrl}&media={$shareImg}&description={$shareTxt}" target="_blank" rel="noopener">Pinterest</a>
<a href="mailto:?subject={$shareTxt}&body={$shareUrl}">Email</a>
<button type="button" class="js-copy-link" data-url="{$product.canonical_url}">Copy link</button>

<script>
document.querySelectorAll('.js-copy-link').forEach(function (b) {
  b.addEventListener('click', function () {
    navigator.clipboard.writeText(b.dataset.url);
  });
});
</script>

Note the |escape:'url' filter on every value. The product URL, image and name must be URL-encoded or a space or ampersand in a product name will break the share link. That single detail is the difference between a button that works and one that silently truncates.

Placement decides whether they're used at all

A perfect set of buttons in the wrong place gets ignored. Sidebar share buttons on every product page are scrolled past; buttons that appear at a natural sharing moment get clicked. The high-value moments on a PrestaShop store:

• On the product page, near the image and price, not buried in the footer. On mobile, where most sharing happens, they need to be reachable without a long scroll. The displayProductAdditionalInfo hook above puts them there.
• On the order-confirmation page, the order-confirmation controller, hook displayPaymentReturn or displayOrderConfirmation. A customer has just bought; "show your friends what you got" lands at the one moment they're most enthusiastic, and it costs them nothing.
• On the wishlist. Saving a product is a sharing intent. If you run a wishlist module, a "share this list" link turns one shopper into a referral channel (and a gift-buyer's shopping list).
• On blog articles. Content gets shared far more readily than product pages, so prominent share buttons earn their place there even when they're marginal on a product. If you publish with Blog Revolution, give posts visible share links.

Track shares, including the dark-social traffic you currently can't see

Two layers of tracking turn share buttons from decoration into a measurable channel.

The click itself. Fire a GA4 event when a button is clicked, a share event with the method (whatsapp, copy_link, pinterest) and the product id. This tells you which products get shared most (often quiet bestsellers worth promoting) and which channels your customers actually prefer, so you can prune the buttons nobody touches.

The visit that results. This is how you finally see dark social. Append UTM parameters to the URL the button shares, not just the one it links to, so the link your customer sends to a friend is ?utm_source=whatsapp&utm_medium=social&utm_campaign=share. Now when the friend clicks, GA4 attributes the visit to your WhatsApp share channel instead of dumping it in Direct. You're not eliminating dark social, but you're converting the share clicks you generated from invisible into measured. For how the platform-side pixels and tags fit alongside this UTM tracking, see social tracking explained simply.

Where share buttons end and social selling begins

Share buttons are a small, cheap lever, worth doing well, not worth obsessing over. They let your existing customers do a little marketing for you for free. They are not a substitute for the channels that actually drive volume, and it's worth being clear about the boundary so you put effort where it pays:

• If you want to show your catalogue inside social apps rather than just link out, that's a Facebook/Instagram shop, it displays your products inside Meta's surfaces, with whether shoppers check out in-app or get sent to your site depending on country and account setup. It's not a share button, see selling on social media with a Facebook shop.
• If you want other people's audiences sharing your products, that's influencer work, which pays off at small scale too, see micro-influencers for small stores.
• If you're running paid social and want the shares and visits to feed retargeting, the tracking foundation matters more than the buttons. Start with the Facebook Pixel for PrestaShop.

Frequently asked questions

Do people still share products in 2026? More than ever, but the sharing moved from public broadcast (a Facebook timeline post, a tweet) to private channels: WhatsApp, Messenger, a link pasted into a group chat. The old Facebook-and-X buttons can't follow it there, which is why they feel dead while sharing itself is alive.

What is "dark social" and why does it matter? It's the private sharing that arrives at your store with no referrer, a friend opens the link your customer sent and GA4 files the visit under Direct, indistinguishable from someone typing your URL. It's real, often substantial traffic your reports under-credit. Tagging your shared links with UTMs converts those share clicks from invisible into measured.

Which share buttons should a typical store actually keep? Two universal ones, WhatsApp and Copy link, plus one or two matched to your catalogue: Pinterest if your products are visual, Email if your purchases are considered. Drop X unless your audience is clearly there. A wall of icons just adds page weight; two or three matched to behaviour cover almost all real sharing.

Should I use each platform's official share button? No. The official buttons pull in third-party JavaScript, iframes and extra network requests, often with cookie and consent implications, and they hurt the Core Web Vitals Google weighs. Every share action you want is a plain URL the browser opens, zero scripts, zero external requests, zero consent implications. Build them as ordinary anchors (see the code above).

Where should the buttons go? Near the image and price on the product page (the displayProductAdditionalInfo hook puts them there), on the order-confirmation page where the customer is most enthusiastic, on the wishlist, and on blog articles. Content gets shared far more readily than product pages. Sidebar buttons get scrolled past and ignored.

Related modules and reading

If you'd rather not hand-edit templates, our Social Share Buttons module places the plain-URL buttons through standard product-page hooks and fires the GA4 share event for you (disclosure: this is our own PrestaShop module). For the wider social presence around them, feeds, follow links and on-store social activity, see Social Revolution; if visual discovery is your game, Pinterest Feed Integration turns the Pinterest share into a proper catalogue feed; and to publish share-worthy articles with visible share links, Blog Revolution.

The bottom line

People absolutely still share products, they've simply moved from public broadcast to private message, where the old Facebook-and-X buttons can't follow. On PrestaShop that means three practical moves: don't assume the platform hands you product share buttons by default (ps_socialfollow points the wrong way, and ps_sharebuttons isn't always installed), build the buttons you do add as plain URL links so they cost no page speed, and put them where sharing naturally happens, by the price, after the order, on the wishlist, on your blog. Add WhatsApp and Copy link for everyone, Pinterest if your products are visual, Email if your purchases are considered, and tag every shared link with UTMs so the dark-social traffic finally shows up in your reports. Small lever, but a free one, and free customer advocacy is worth claiming properly.