The Conversion Tracking plugin (plg_solidshop_conversions) sends each order to the
analytics and advertising tools your store uses, from nothing more than their IDs:
Google Analytics 4, Google Ads, Meta Pixel,
Microsoft Advertising, TikTok, Matomo,
Plausible, Umami and Fathom, plus a box for
your own code. Each order is sent once, from the order confirmation page, with its value and,
where the tool takes them, its currency and products, and with no personal data.
Solidshop itself can report each order to Google Tag Manager and to scripts of your own, with Publish orders to the data layer on the store’s Tracking tab — see Conversion tracking for what the order contains and which orders count. The plugin builds on that order and does not need the switch: it loads each tool’s script, sends the order in the shape that tool expects, and holds everything back until the shopper agrees in the cookie banner. See the Conversion Tracking extension page for the overview.
Requirements
- Joomla 6.x or later
- PHP 8.4 or later
- Solidshop 1.8.0 or later — the release that reports each order on the confirmation page, gives each store its Tracking tab and ships the cookie banner. The installer refuses an older core, so update Solidshop first.
Installation
Download plg_solidshop_conversions from the Downloads page
while your subscription is active. Updates arrive through the Joomla updater.
In System → Install → Extensions, drop the ZIP into the upload area. The plugin is enabled on install and does nothing until a store has a tool set up, so there is nothing to switch on in the Plugins screen.
Go to Solidshop → Configuration → Stores, open the store and choose the Tracking tab. Next to the store’s own General card you now find a card for consent, one per tool, and one for custom code. Every setting belongs to the store: on a site with several stores, each reports to its own accounts.
The dashboard’s Store setup checklist gains a Measure your sales step that links to this tab. It ticks once any tool, the custom code or the store’s data layer is on; a store that tracks nothing can mark it not needed.
Consent
Advertising and analytics tools set cookies, so in the EU and the UK, and in many other places, they may only run after the shopper agrees. Out of the box the plugin outputs every tool’s script blocked, and Solidshop’s own cookie banner runs it once the shopper accepts its category:
- Turn the banner on in Solidshop → Configuration → Settings, on the Cookie consent tab (how the banner works). The store screen warns you when a tool waits for the banner and the banner is off: nothing would ever run.
- Type the tool’s ID on the Tracking tab. While a tool waits for the banner, the banner asks the shopper while they browse the shop, not on the confirmation page where the tools load.
The ad platforms (Google Ads, Meta, Microsoft, TikTok) wait for Marketing consent and the analytics tools for Analytics; Google waits for Analytics while it only feeds GA4 and for Marketing as soon as it sends to Google Ads. Each tool’s card has a Consent category to change that.
| Consent card setting | Use it when |
|---|---|
| Blocked by my consent tool + Solidshop cookie banner | The default. Your site uses the banner that ships with Solidshop. |
| Blocked by my consent tool + another tool |
Your site runs CookieConsent v3 (as YOOtheme Pro ships it), Cookiebot, n3t Cookie Consent or
Klaro. The scripts are written in that tool’s markup. Custom attribute covers
a tool that is not listed but blocks scripts by a data- attribute. That tool does
the asking: keep the Solidshop banner off, so shoppers are not asked twice. Cookiebot reads
Analytics as its Statistics category. With Klaro the scripts are named after Klaro
services: create services called analytics and marketing, or type
your services’ names in Analytics category and Marketing
category. With Custom attribute, give the Attribute (for
example data-category) and, if your tool names its categories differently,
those two names.
|
| None | Your store needs no consent, or Google Tag Manager decides which tags may run. The scripts run as soon as the order is published. |
The plugin never sets Google Consent Mode itself: Solidshop’s banner sends it, and so does any other consent tool that supports it.
Which amount each tool gets
Every tool’s card has a Value sent setting with two choices (on the Google card, Value sent to GA4 and Value sent to Google Ads):
| Value | What it is | Default for |
|---|---|---|
| Revenue before tax | The goods after discounts, without tax or shipping: the figure the sales report shows. | GA4, Plausible, Umami, Fathom |
| Total the customer pays | The order total with tax, shipping and any payment fee. | Google Ads, Meta, Microsoft, TikTok, Matomo |
Google, Meta, Microsoft, TikTok and Matomo are sent the order’s products by the id your catalog feeds know them by — the SKU, or the product id when a product has none — so purchases join your Google Merchant Center and Meta catalog. Plausible and Umami get the number of items instead, and Fathom only the value.
Setting up each tool
The ID fields on the Google, Meta, Microsoft and TikTok cards accept several, one per line; Matomo, Umami and Fathom take one site each. An ID in the wrong format is refused when you save, with the entry named. Each card also has Load the script (Load the Google tag on the Google card), on by default: switch it off when your site already loads that tool another way (Google Tag Manager, a template setting), and the order is sent to the copy your site loads.
No tool is sent a page view: the plugin measures sales, not visits, and your visitor numbers keep coming from the analytics your site already runs. It never sends a name, e-mail address, phone number or address, so there are no Google Ads enhanced conversions and no Meta advanced matching.
Google Analytics 4 and Google Ads
-
GA4 Measurement IDs:
G-XXXXXXXXXX, from GA4’s Admin → Data streams. GA4 gets apurchasewith the order’s items, tax, shipping and coupon, and whether the customer is new or returning. -
Google Ads conversions: the conversion ID and label together,
AW-123456789/AbCdEfGhIjK, as the conversion action’s event snippet shows them insend_to. Each gets the order’s value, its number for deduplication, andnew_customerfor the new customer acquisition goal. - Dynamic remarketing, off by default, also sends each Google Ads account the products bought, under the retail vertical, for remarketing ads built from your Merchant Center feed. It needs a Google Ads conversion above.
If Google Tag Manager on the same site already sends the data layer purchase to the same GA4 property, use one or the other: both would count each order twice.
Meta Pixel
Pixel IDs from Events Manager → Data sources. Each pixel gets one
Purchase with the products, sent to that pixel only, and the order number as its
event ID — so the Meta Conversions API can be added later without counting orders twice.
Microsoft Advertising
UET tag IDs from Tools → UET tag. Each tag gets a
purchase with the order’s value (the total the customer pays unless you change
Value sent) and the products. The conversion goal’s event
action must be purchase.
TikTok
Pixel IDs from Events Manager → Web events. Each pixel gets one
Purchase (TikTok’s name for the event since May 2025) with the products,
deduplicated by the order number.
Matomo
Your Matomo URL, an https:// address
(https://example.matomo.cloud/ or your own server),
and the website’s Site ID. Matomo gets an ecommerce order with its lines,
tax, shipping and discount; Disable cookies (on by default) tracks it without
Matomo’s cookies. Ecommerce must be turned on for the website in Matomo.
Plausible, Umami and Fathom
Each gets one named event, Order unless you change Event name, with
the order’s value. Create a goal with that name in the tool to see orders as conversions.
-
Plausible: the site script address from your site’s installation
instructions (
https://plausible.io/js/pa-….js), with Domain left empty. Revenue is recorded against a revenue goal (Plausible’s Business plan); without one the event is still counted. On the older script (https://plausible.io/js/script.js) give the Domain too; the plugin then loads its manual variant, which records no page view. Self-hosted or proxied, give the manual variant yourself (…/js/script.manual.js): your copy may not serve the others. -
Umami: the tracker address (
https://cloud.umami.is/script.json Umami Cloud) and the Website ID from its tracking code. -
Fathom: the Site ID from its embed code. Fathom takes the
currency from the event’s settings; a store that takes several currencies can switch on
Add the currency to the event name and get
Order EUR,Order USDand so on.
Custom code
For a tool that is not listed — an affiliate network, Pinterest, a CRM — the
Custom code card runs your JavaScript once for each order on the confirmation
page. Write it without <script> tags, and use tokens for the order’s
values:
pintrk('track', 'checkout', {
value: {{order.total}},
currency: '{{order.currency}}',
order_id: '{{order.reference}}'
});
| Token | Prints |
|---|---|
{{order.reference}}, {{order.currency}} |
The order number and the currency code, without quotes: put them in your own. |
{{order.id}}, {{store.id}} |
The order’s and the store’s ids in Solidshop, as numbers. |
{{order.revenue}}, {{order.total}}, {{order.tax}},
{{order.shipping}}, {{order.discount}}
|
Amounts, with a dot and the currency’s decimals. |
{{store.name}}, {{order.coupon}} |
Text, printed as a complete quoted string: never put these in quotes. |
{{event_json}}, {{ga4_json}} |
The whole order, as the order event or as GA4’s ecommerce object. |
There is no token for the customer. A token the plugin does not know prints nothing, and saving
the store names it so a typo does not go unnoticed. The code runs inside a function, so its
variables stay local, and it waits for consent like the tools do (Marketing unless you choose
Analytics). A script of your own that takes the order over (preventDefault() on
solidshop:purchase, see Conversion
tracking) stops the tools and the custom code for that order too.
The code runs on your storefront, so only users who may change Solidshop’s Options can see or change it. Other users who edit the store see a note instead, and their saves keep the code as it is.
Testing
- Open the shop in a private window and accept the cookie banner. Use an e-mail address with no earlier orders to see a new customer reported.
- Place a test order with a test payment method, or with bank transfer.
- On the confirmation page, check each tool: GA4’s DebugView or the Tag Assistant, the Meta Pixel Helper or Test events in Events Manager, the UET Tag Helper, the TikTok Pixel Helper, or the browser’s network panel for Matomo, Plausible, Umami and Fathom.
- Reload the page: you land back on the checkout, and nothing is sent again, because each order is shown and reported once.
Troubleshooting
- Nothing arrives in any tool
- Check the warning on the store screen: with the scripts waiting for the Solidshop banner, the banner must be on, it must offer the category (Ask for analytics, Ask for marketing on its tab), and the shopper must have accepted it. With Count orders not yet paid off, a bank-transfer or cash-on-delivery order is not reported at all.
- Orders are counted twice
- Two things send to the same account: the plugin and Google Tag Manager, or the plugin and a pixel your template loads with its own purchase code. Keep one sender. If your site loads the tool’s script itself, you can also switch the card’s Load the script off; the plugin then sends to that copy.
- A
UA-ID is refused -
Universal Analytics stopped processing data in July 2023. Use the GA4 Measurement ID
(
G-…).