SocialEasy · By Sophie Calder · Updated 13 Nov 2026 · 18 min read

SocialEasy: Magento 2 Social Proof Notifications

Add Magento 2 social proof purchase notifications and promotional hellobars that build buyer confidence and lift conversions.



Overview

SocialEasy adds social proof to your Magento storefront by showing recent purchase pop-ups and promotional hellobars to shoppers as they browse. When a customer places an order, SocialEasy sends anonymized purchase data to the SocialEasy service, which then surfaces that activity to other visitors in the form of a small notification - the product name, buyer's first name, and location - appearing in the corner of the page. The result is a live signal of store activity that reassures hesitant buyers that others are purchasing right now.

SocialEasy configuration overview

This module helps you:

  • Show real-time purchase slide-up notifications to build buyer confidence
  • Display hellobars with promotional messages or announcements sitewide
  • Track notification engagement with UTM-tagged links back to product pages
  • Automatically sync new orders and customer registrations to the SocialEasy service
  • Manage the content and appearance of your notifications from the SocialEasy dashboard

When to use this

Use SocialEasy when you want to:

  • Reduce hesitation on product pages by showing that other shoppers are buying
  • Run promotional announcements (sales, free shipping thresholds, limited-time offers) via a hellobar without touching your theme
  • Attribute traffic from social proof notifications back to specific Google Analytics campaigns using UTM parameters
  • Launch a new product and quickly build perceived demand by surfacing your first real orders to subsequent visitors
  • Complement a retargeting or email campaign with on-site FOMO messaging

Key capabilities

  • Purchase notifications - real-time slide-ups showing anonymized recent order details to increase buyer confidence
  • Hellobars - sitewide announcement strips managed from the SocialEasy dashboard, no theme changes required
  • Analytics tagging - UTM source, medium, and campaign parameters added to every notification link so engagement shows up in your analytics tool
  • Conversion window - configurable look-back period (in days) for attributing conversions that started from a notification click
  • Auto pixel - automatic pixel loading after a visitor allowance check, or a managed Google Tag Manager request
  • Visitor usage - track unique browser visitors over the last 30 days and automatically pause SocialEasy when your plan allowance is exceeded
  • Batch order sync - when you first connect your API key, your last 30 orders are sent to seed the notification feed immediately

Installation

Bought on Adobe Commerce Marketplace? Your purchase comes with a Moogento account: set your password from the activation email, then follow the steps below with the Composer keys and licence key in My Plugins. If the email has not arrived, contact Moogento support.

SocialEasy installs via Composer, then activates with a license key from your Moogento.com account. The whole flow takes about 5 minutes.

Prefer a hands-off setup? Our team can install and configure the extension for you - see the paid install service.

Step 1: Get your Composer keys from Moogento.com

  1. Sign in at https://www.moogento.com and open My Plugins in your account menu.
  2. Find SocialEasy in the list of plugins you own.
  3. Generate (or reveal) the Composer access keys for that plugin - a public key and a private key.
  4. Add your install domain to the key. Each Composer key is tied to a specific domain - if you're installing on yourstore.com, add yourstore.com to the key's allowed domains. The Composer download will be rejected on any other domain.

If you run staging and production on different domains, add both - separate keys per environment are fine too.

Step 2: Install the module with Composer

From your Magento 2 root directory:

composer require moogento/m2-socialeasy

When Composer asks for credentials, paste the public key as the username and the private key as the password. They'll be cached in ~/.composer/auth.json for future runs.

Step 3: Enable the module in Magento

php bin/magento setup:upgrade
php bin/magento setup:di:compile
php bin/magento cache:clean

If you run php bin/magento module:status Moogento_Socialeasy you should see it listed as enabled.

Step 4: Add your license key in the Moogento admin

  1. For a direct purchase, copy the SocialEasy license key from My Plugins at moogento.com. For a Marketplace purchase, check your Moogento account for an issued key and contact Moogento support if it is missing.
  2. Open Stores > Configuration > Moogento > License in Magento Admin. Add the Installation Domain shown on this page to the key in your Moogento account.
  3. Paste the key into the key field and click Add key.
  4. Under Registered Keys for this Installation, confirm that SocialEasy appears with the correct plan.

The license validates within a few seconds. You should see the module's status flip to active. If it stays inactive, double-check the domain on the license matches where you've installed - domain mismatch is the most common cause.


Setup overview

Most setup happens in:

Stores > Configuration > Moogento > SocialEasy

You'll mainly work with:

  • General - enable the module, connect your API key, and choose how the pixel script is loaded
  • Setup: Google Analytics - configure UTM parameters and the conversion tracking window

Common setups

Connect your SocialEasy account and activate notifications

Before notifications appear on your storefront, you need to link your Magento store to your SocialEasy dashboard with an API key.

How to set it up

  1. Log in to your SocialEasy dashboard at https://socialeasy.moogento.io and copy your API key from the account settings.

  2. In your Magento admin, go to: Stores > Configuration > Moogento > SocialEasy > General

  3. Set:

    • Enable = Yes
    • API Key = (paste the key from your SocialEasy dashboard - this is separate from your Moogento license key)
  4. Click Save Config.

    On save, the module validates the key against the SocialEasy service and sends your last 30 orders to seed the notification feed. After choosing automatic loading or the managed GTM setup below, recent purchase notifications can appear on the storefront within a few minutes.

  5. Choose how the SocialEasy pixel script loads: set Auto-Add Pixel Script to Yes, or configure the managed GTM snippet.

SocialEasy General settings - API key and enable toggle

Notes

  • The API key is stored encrypted in the database and masked in the admin field after saving.
  • If you see a validation message that the key is not accepted, verify it was copied without trailing spaces and that your server can reach socialeasy.moogento.io over HTTPS.
  • To manage what the notifications say and look like, use the Manage notifications link in this group - it opens the SocialEasy dashboard directly.

Set up Google Analytics tracking for notification clicks

Tag every notification link with UTM parameters so you can measure traffic and conversions from social proof notifications in your analytics tool.

How to set it up

  1. Go to: Stores > Configuration > Moogento > SocialEasy > Setup: Google Analytics

  2. Set:

    • Conversion: Window = number of days you want to count as a conversion after a click (default: 1)
    • utm_source = the source label for your analytics tool (default: socialeasy)
    • utm_medium = the medium label (default: cta)
    • Purchase notification: utm_campaign = the campaign name (default: SO product)
  3. Click Save Config.

SocialEasy Google Analytics settings - UTM fields and conversion window

Notes

  • UTM parameters are appended to the product URL included in each purchase notification. Shoppers who click through will land on the product page with those parameters in the URL.
  • The conversion window controls how long the module tracks whether a visitor converts after seeing a notification - it does not affect your Google Analytics attribution model directly.
  • Keep utm_source consistent with any other SocialEasy traffic sources you already have in your analytics account to avoid fragmented data.

Choose how the SocialEasy pixel script loads

Set Auto-Add Pixel Script to Yes for the simplest setup (the default is No). The module checks visitor usage before loading the SocialEasy pixel and reuses that browser tab's decision for up to one hour.

If Google Tag Manager controls consent or loading timing, set Auto-Add to No and use the managed loader. Automatic loading follows Magento's native cookie restriction settings; it does not read a separate consent platform's GTM conditions. Replace any direct SocialEasy pixel tag (the script from your SocialEasy dashboard):

  1. Open Stores > Configuration > Moogento > SocialEasy > General.
  2. Set Auto-Add Pixel Script to No and save. The module still loads its visitor counter and managed loader.
  3. Remove or pause any direct SocialEasy pixel tag in GTM.
  4. Create a Custom HTML tag with a DOM Ready trigger and your required consent conditions:
<script>
window.mooSocialeasyPixelRequested = true;
if (window.mooSocialeasy) {
    window.mooSocialeasy.load();
}
</script>
  1. Publish the reviewed GTM container changes and verify that notifications appear while your plan is active.

The snippet queues the request if the module loader has not started yet, or calls it immediately if it has. The loader uses the Magento allowance gate, with a decision cached in that browser tab's session storage for up to one hour. A new tab without a cached decision checks again; repeat navigation in the same tab can reuse the decision. If the earlier check counted the visit without requesting a pixel, the GTM request makes one new check to obtain the pixel URL. Connection failures are retried instead of cached. With Magento native cookie restriction mode enabled, withdrawing cookie consent clears the cached authorization. Do not copy a Magento form key into the tag; the loader reads the browser's current cookie when making the request.

A direct SocialEasy pixel tag bypasses this gate and must be replaced. The Magento gate does not change service-side limits or retract notifications already running in an open tab.


Features reference

Social proof purchase notifications

Displays a small slide-up in a corner of the storefront showing the first name, city, country, and purchased product of a recent buyer. Data is sent to the SocialEasy service automatically each time an order is placed.

  • What it does: informs browsing shoppers that real people are buying, creating urgency
  • When to use it: always-on once configured; no per-product setup needed
  • Config path: moogento_socialeasy/general/enable

A direct link in the admin config to the SocialEasy dashboard login page, where you control notification text, display rules, hellobar content, and appearance.

  • What it does: opens https://socialeasy.moogento.io/login/ in a new tab
  • When to use it: to edit notification copy, pause campaigns, or configure hellobars
  • Location: Stores > Configuration > Moogento > SocialEasy > General

Hellobars

Sitewide announcement strips configured entirely from the SocialEasy dashboard. No Magento theme changes or deployments are required to add, edit, or remove them.

  • What it does: renders a configurable banner at the top or bottom of every storefront page
  • When to use it: for time-sensitive promotions, shipping threshold messages, or event announcements
  • Managed from: your SocialEasy dashboard at https://socialeasy.moogento.io

Order-view source card

On an order that has an attributed SocialEasy popup click, the admin order view shows a "How SocialEasy probably helped" card alongside cards from any other Moogento modules that also contributed to that sale.

  • What it does: shows that a shopper clicked a SocialEasy popup before this order was placed, plus the click time when one was recorded
  • When to use it: reviewing why an order came in, alongside ProfitEasy's other source-attribution cards
  • Requires: ProfitEasy installed, enabled and on a Pro licence (only Pro shows the Sale Source panel the card appears in), plus SocialEasy enabled and licensed
  • Config path: moogento_socialeasy/general/enable

Advanced configuration

UTM parameter customization

What it does

By default, every notification link includes utm_source=socialeasy, utm_medium=cta, and utm_campaign=SO product. You can change these values in Magento's global Default scope, but not separately for individual websites or store views.

Setup

  1. Go to Stores > Configuration > Moogento > SocialEasy > Setup: Google Analytics.
  2. Adjust utm_source, utm_medium, and Purchase notification: utm_campaign to match your campaign naming conventions.
  3. Save Config.

Notes

  • These settings are default-scope only (store-view and website scopes are not available for the analytics group). If you run multiple stores, all will share the same UTM values unless you duplicate the API connection under separate SocialEasy accounts.
  • Changes take effect immediately on the next order - existing notifications already sent to the service are not retroactively updated.

Pixel script via Google Tag Manager

Use the managed GTM setup above when GTM needs to request the pixel. Keep Auto-Add Pixel Script set to No and replace any direct SocialEasy pixel tag with that managed snippet. It queues an early request until the module loader is ready, including on cached storefront pages, and keeps the visitor allowance check in place.

Clear Magento's full-page cache (php bin/magento cache:clean) after changing Auto-Add or removing a direct pixel embedded in Magento. A GTM-only tag change needs the reviewed container changes published. Check that the managed tag fires on DOM Ready with your required consent conditions.


Tips & best practices

  • Seed the feed before launch. Place a few test orders on staging before going live so the notification feed has real data when the first real shopper arrives.
  • Choose the managed loading method. Set Auto-Add to Yes for the simplest setup, or use the managed GTM snippet when GTM controls consent or loading timing. Replace direct SocialEasy pixel tags so visitor limits still apply.
  • Match UTM naming to your analytics conventions. If your team uses source=email for email campaigns, don't use source=socialeasy for this - pick a value that fits your existing taxonomy so reports stay clean.
  • Check the SocialEasy dashboard after saving the API key. The batch sync of 30 recent orders happens on save - verify the dashboard shows those orders before going live.
  • Use a 1-day conversion window for high-frequency stores. A longer window inflates the conversion count from notification clicks for stores where customers return to buy different items within days.
  • Disable on staging if you share a database with production. The module sends real order data to the SocialEasy service on every order event. If staging and production share a database or the same API key, staging orders will appear in your production notification feed.

Troubleshooting

Notifications are not appearing on the storefront

No purchase slide-ups are visible to shoppers after configuration.

  • Cause: The module is disabled, the API key is missing or not yet validated, Auto-Add is No without a working managed GTM tag, the visitor allowance is exceeded, or cookie consent has not been granted.
  • Check: Go to Stores > Configuration > Moogento > SocialEasy > General and confirm Enable = Yes and the API Key field contains a value. Open your browser's developer console on the storefront and verify the SocialEasy script has loaded (no 403/404 errors). Review the visitor usage card and confirm the selected loading method and required consent are active.
  • Resolution: Save the configuration again to re-trigger API key validation and the initial order sync. If the pixel is set to auto-add, flush the full-page cache (php bin/magento cache:clean) so the updated config reaches the frontend.

The API key is not accepted on save

A message appears in the admin indicating the SocialEasy API key is not valid.

  • Cause: The key was copied incorrectly, the server cannot reach socialeasy.moogento.io, or a Content Security Policy rule is blocking the outbound request.
  • Check: Verify you copied the API key from the SocialEasy dashboard (not the Moogento license key). Test outbound HTTPS from the server: curl -I https://socialeasy.moogento.io/api/verifyAPI.
  • Resolution: Re-paste the key from your SocialEasy dashboard and save again. If connectivity is the problem, work with your hosting provider to allow outbound HTTPS to *.moogento.io.

Product images are not appearing in notifications

Notifications show text but no product image.

  • Cause: The product image file does not exist at the expected path, or the image has not been resized and cached yet.
  • Check: Confirm the product has an image assigned in the Magento catalog, and that the file exists under pub/media/catalog/product/. Check that the media directory is readable by the web server.
  • Resolution: Re-save the product to trigger image processing, or run php bin/magento catalog:images:resize to rebuild the image cache.

Clicking a notification link takes the shopper to the product page without UTM tags.

  • Cause: The analytics settings have not been saved, or the conversion window is set to 0.
  • Check: Go to Stores > Configuration > Moogento > SocialEasy > Setup: Google Analytics and verify all four fields have values (Conversion Window, utm_source, utm_medium, utm_campaign).
  • Resolution: Fill in any blank fields and click Save Config. UTM parameters will be included in all notifications generated after the save.

Malware scanner flags Helper/Moo.php

  • Cause: Your host's malware scanner (often Imunify360 on cPanel hosting) heuristically flags the encoded license-check files that ship inside every paid Moogento extension. The files are genuine and unchanged - the encoding protects the license check from tampering.
  • Resolution: Add the files to the scanner's ignore list so the warnings stop, and restore any file the scanner already quarantined. Both steps, plus how to verify the files are byte-for-byte what we shipped, are covered in the license file protection guide.

FAQs

How do I add Magento 2 social proof purchase notifications to my store?

Install SocialEasy, then go to Stores > Configuration > Moogento > SocialEasy > General, paste your API key from the SocialEasy dashboard, and set Enable to Yes. The module immediately syncs your last 30 orders. Choose Auto-Add Yes or the managed GTM setup so notifications can load for shoppers while your plan allowance and required consent permit.

Why is my SocialEasy API key not working?

The API key for SocialEasy comes from your account at socialeasy.moogento.io - it is not the same as your Moogento license key. If the key still fails after re-pasting, check that your server can reach socialeasy.moogento.io over HTTPS, as some hosting environments block outbound requests by default.

Do the purchase notifications show real customer names?

Notifications display only the buyer's first name along with their city and country - no email address, last name, or order total is shown. The email is stored as a hash and is never exposed on the storefront.

How do I change what the notifications say or look like?

Notification content and appearance are controlled from the SocialEasy dashboard at https://socialeasy.moogento.io. Use the Manage notifications link in Stores > Configuration > Moogento > SocialEasy > General to open it directly.

Does SocialEasy work with Hyvä, Luma, and Porto themes?

Yes. The SocialEasy pixel script and notification widgets are injected by the external SocialEasy service and are theme-agnostic. The Magento module provides the visitor gate, managed pixel loader, admin configuration and backend data sync. No frontend theme template overrides are required.

What happens if I disable SocialEasy?

Setting Enable to No stops new orders from being sent to the SocialEasy service and prevents new pixel loads through automatic loading or the managed GTM snippet. Clear Magento's full-page cache after changing this setting. Existing notification data in your SocialEasy dashboard is unaffected, and notifications already running in an open tab cannot be retracted. Any leftover direct SocialEasy pixel tag operates outside the module and must be removed separately.

Which SocialEasy plan do I need?

Choose a plan for your monthly visitor volume:

Plan Monthly visitor allowance
Seed 10,000
Growth 30,000
Pro 100,000

Larger plans retain their existing allowances: Pro A 200,000, Pro B 400,000, and Pro C 800,000 visitors.

Notification content and appearance are managed in your SocialEasy dashboard. Contact Moogento support if your store needs more than 100,000 monthly visitors.

How is visitor usage counted?

The allowance covers unique browser visitors during the rolling last 30 days, across all store views in your Magento installation. Repeat visits from the same browser count once while that browser remains in the window. This counts browsers, rather than customer accounts or page views.

SocialEasy uses an anonymous first-party browser identifier and stores only a protected hash and its last-seen time on your server. A different device or browser, cleared browser storage, and consent settings can affect the count. Counting begins when you install the release with visitor limits; earlier visits cannot be reconstructed. Pulse is not required.

What happens when I reach my visitor allowance?

SocialEasy remains active at the allowance and stops when the visitor count exceeds it. An allowance decision is cached for up to one hour in each browser tab, so stop, upgrade and resumption changes can take up to one hour to reach existing tabs. Notifications already running in an open tab cannot be retracted. It resumes automatically when older visitors leave the rolling 30-day window or you upgrade to a plan with enough capacity. This controls the Magento integration and managed pixel loader, without changing limits in the external service.

Displayed counts and backend order or registration checks can lag by up to one minute. An unavailable service or a temporary new-visitor restriction is retried instead of being cached for an hour. If a valid plan cannot be recognized, usage is shown as unavailable.

Open Stores > Configuration > Moogento > SocialEasy to review the visitor usage card beneath the page header. It shows your current count, counting window, active plan and allowance, all three plan limits, and whether SocialEasy is active, stopped, or usage is unavailable. Use the upgrade link to review a larger plan.

Should I use Auto-Add Pixel Script or Google Tag Manager?

Set Auto-Add Pixel Script to Yes for the simplest setup (the default is No). If you need GTM to control when the pixel is requested, set it to No and use the managed loader snippet in the Common setups section. Replace any direct SocialEasy pixel tag so visitor limits still apply.

How do I track which conversions came from SocialEasy notifications?

Go to Stores > Configuration > Moogento > SocialEasy > Setup: Google Analytics and configure the UTM source, medium, and campaign values. Every notification link will include those parameters so you can filter the traffic in Google Analytics. The Conversion Window field controls how many days the module considers a click as an attributed event.

Can I run SocialEasy on a staging environment?

You can, but be aware that placing orders on staging will send that data to the SocialEasy service using the same API key. If staging and production share an API key, staging orders will appear in your live notification feed. Use a separate SocialEasy account and API key for staging, or disable the module on staging environments.


  • Analyticseasy - enhanced Google Analytics tracking for Magento events; complements the UTM tagging that SocialEasy adds to notification links
  • Profiteasy - profit and margin reporting; useful alongside SocialEasy when you want to see whether social proof notifications are driving orders on high-margin products

Need help?

  • moo@moogento.com
  • Include:
    • Magento version
    • Module name
    • What you're trying to do