OcBox AI Remarketing & Advanced Analytics

OcBox AI Remarketing & Advanced Analytics — every OpenCart analytics and remarketing tool rolled into one module

Ads and analytics · OcBox team Ads eating your budget with too few orders? Our paid-ads specialist Kristina will set up and fine-tune your Google Ads and Meta campaigns and wire up GA4 so every dollar you spend comes back as orders. Hundreds of e-commerce projects behind her, real numbers instead of guesswork. Talk to Kristina →

Thanks to everyone who helped with development and testing

This module grew on the live stores of our alpha testers: your bug reports, screenshots from ad managers and feedback in the support topic over the past months are what turned it into what it is now. Everyone who really helped (tested, reported what did not work, showed conflicts with other modules, suggested needed features) — gets a lifetime free license for this module. Just send a private message to OcBox, remind us who you are and how you helped, and we issue a license for your domain, no questions asked. Thank you!

Every ad pixel, server-side conversion API, GDPR consent layer, Google product feed, UTM reports, Telegram notifications and AI helpers — in one module, from one admin tab. Fill in the IDs and tokens once, and every store event (product view, cart, checkout, purchase, search, sign-up) fires into your ad platforms automatically, with client+server deduplication, proper currency and complete product data. One payment, no monthly subscriptions, no lock-in to third-party services.

What you get — in detail

This is not a marketing blurb but a working checklist of everything the module actually does. Each part is turned on separately, so you decide which pixels and features to enable.

Google Analytics 4 — client-side gtag plus server-side sending

✓ GA4 through two paths at once, with proper e-commerce events
Enter a Measurement ID (G-XXXXXXXXXX) and, optionally, an API Secret — the module drops gtag.js on every page and simultaneously sends the same events over Measurement Protocol straight from your server. All standard store events (view_item, view_item_list, add_to_cart, view_cart, begin_checkout, add_shipping_info, add_payment_info, purchase, search, sign_up) are built in the exact GA4 shape, with ecommerce.items, correct currency, brand and positions. Every item in an event carries the full set GA4 expects: id, name, brand, up to five category levels, the chosen variant (colour, size), the price after discount, the discount itself in money, the applied coupon code, quantity and the store domain. Empty fields are not sent, so the reports stay clean. A "Send test event" button verifies the wiring in a second, results show up in DebugView. Events are now enabled by default right after install, no need to open settings first.
⚠ Without this: ad blockers strip up to half of client events, GA4 conversions dip, reports lie, Google Ads campaign optimiser works on incomplete data.

Google Ads — conversions plus remarketing with no template edits

✓ Conversion ID, conversion labels and remarketing audience collection
Enter a Conversion ID (AW-XXXXXXXXX) and conversion labels in the format purchase=LABEL, flip the remarketing switch on — and the module sends every completed purchase to Google Ads with the right amount and order currency, and builds a remarketing audience from product page visits. Events are deduplicated by event_id, so Smart Bidding gets a clean signal.
⚠ Without this: Google Ads does not see real conversions, Smart Bidding cannot learn, CPA climbs and ROAS drops.

Meta Pixel — Facebook and Instagram, with Conversions API

✓ Client pixel + server CAPI with deduplication
Drop Pixel ID + Access Token into the "Meta" tab — the client fbq and the server Conversions API both fire the same events with one shared event_id. Meta collapses the duplicates automatically, so the Ads Manager report counts every purchase exactly once even when the shopper is on an ad blocker. Test Event Code for live checks is supported too. Access Token is stored encrypted with the store key, decrypted only at the moment the API is called.
⚠ Without this: after iOS 14/ATT and modern ad blockers Facebook misses 30–50% of conversions, and purchase-optimised campaigns stall on "insufficient data".

TikTok — pixel plus Events API

✓ Pixel + server token pair for every store event
Paste a Pixel ID + Access Token from TikTok Events Manager — the module fires ViewContent, AddToCart, InitiateCheckout, PlaceAnOrder, CompletePayment and the rest from client and server. The "Test event" button verifies the link and shows the event in TikTok Test Events.
⚠ Without this: TikTok ads burn budget blind, the purchase optimiser has no signal and keeps serving cold audiences.

Pinterest, X (Twitter), Snapchat, Microsoft UET (Bing), Criteo — every pixel in one place

✓ Five client-side pixels on a single "Other pixels" tab
Enter your IDs (Pinterest Tag ID, X Pixel, Snapchat Pixel, Microsoft UET, Criteo Partner ID + Account ID) — each one gets injected on the site with the correct standard events. Every ID format is validated, and the field is highlighted if you paste the wrong thing. Criteo correctly sends viewHome, viewList, viewItem, viewBasket, trackTransaction — exactly under the names OneTag expects.
⚠ Without this: your Pinterest/Snapchat/Bing/Criteo remarketing starts from scratch, audiences take months instead of weeks to build.

Hotjar and Microsoft Clarity — heatmaps and session recording

✓ Hotjar Site ID and Clarity Project ID — heatmaps and recordings straight away
Enter the IDs — the module adds Hotjar and Clarity scripts to every page. In a few hours you can already see where people click, where they drop carts, which buttons no one notices. Microsoft Clarity is fully free and shows sessions almost immediately.
⚠ Without this: you optimise the store blind and argue with your designer about "I think this will be better" instead of just watching the recording.

Google Consent Mode v2 + cookie banner — GDPR without a separate plugin

✓ Consent Mode v2, cookie banner and server-side consent gate
Turn "Consent mode" on — before the visitor consents, ad storage stays in "denied", ad events do not fire, GA4 runs in anonymous mode. The banner sits at the bottom / top / centre with "Accept all" and "Only necessary" buttons. Consent categories (necessary, analytics, marketing, functional) are exposed separately, and every provider is pinned to its category. Server-side sending also checks consent — with no consent, the event simply does not go out. The "Accept all" button now works even on stores where another module breaks JS: the handlers are self-contained, the cookie is written, consent update is sent, the banner closes — regardless of foreign scripts. A "Cookie settings" trigger is always visible in the page corner so the shopper can change their choice at any time. There is a separate "Strict opt-in" mode for jurisdictions that do not accept Consent Mode v2 and require full opt-in-first.
⚠ Without this: complaints, GDPR fines, and since March 2024 Google discards a slice of data in European reports without Consent Mode v2.

"Data Layer only" mode — running through Google Tag Manager

✓ Clean dataLayer for GTM, no tag duplication
If the store already has Google Tag Manager and you want it to manage the tags itself (GA4, Google Ads, Facebook, TikTok), flip the "Data Layer only" switch on the "Data Layer" tab — the module stops loading gtag.js on its own, stops duplicating pixel config in head, and stops sending its own server-side events to GA4. The dataLayer keeps being populated cleanly and in order (every entry carries an event_source: "ocbox" tag for quick diagnostics), GTM reads it and decides what goes where. No GTM — leave the switch off and the module keeps working as before.
⚠ Without this: the module and GTM start duplicating the same tags, phantom x2 events in reports, Tag Assistant warnings about double firing.

UTM attribution — see which ad brought every order

✓ UTM capture + first and last source + landing page
The module remembers utm_source, utm_medium, utm_campaign, utm_term, utm_content, first referrer, last referrer and landing page for every visitor, and attaches them to the completed order. You see exactly which campaign, which ad, which Instagram post or email blast delivered each order — not just "came from Google". The traffic source is frozen at the moment of order placement, so manually completing a status in the admin never overwrites it with Direct.
⚠ Without this: you only see the top-level source (google/direct) and cannot tell which campaign actually made money and which burned budget.

Reports + CSV export + Conversion Paths — live statistics inside the admin

✓ Period report: products, categories, orders, sources, with filters
The "Dashboard" tab: individual period buttons ("Today", "Yesterday", "Last 7 days", "Last 30 days", "This month", "Last month", "Custom range" with two "From / To" fields), tiles for "Total orders", "Total sum", "Average order value", a "Traffic sources with sales" table, a separate "Conversion paths" block with per-order paginated view (customer name, product name, sum, source chain up to purchase), navigation "First / Last / Page NNN → Go", and a "CSV Export" button. Everything opens in Excel, with the same filters. No separate BI tool needed.
⚠ Without this: stock OpenCart has no source reports, and every month you hand-merge Google/Meta/TikTok in Excel.

Built-in tracking self-check — proves everything works

✓ Walk from category to a test order — the module shows every event
The "AI Assistant" tab has a "Tracking self-check" panel. Hit "Start check", walk the store: category → product → add to cart → checkout → test order. Come back to the module — a table shows a row per stage (category list view, product view, add to cart, begin checkout, add shipping, add payment, purchase): was the event captured, did it fire exactly once (green "OK"), doubled up (yellow "Duplicate"), does it carry valid data (currency, sum, item count, order id). It also shows where the event came from — dataLayer, client pixel, or server-side send. If there is a problem — the module tells you exactly at which stage. Capture auto-turns-off after 30 minutes, no shopper PII is written.
⚠ Without this: you set everything up, and whether GA4/Meta actually receive the right events with the right data is left to faith.

Conflict detector — warns when another module fires the same events

✓ If another tracker on the page doubles view_item/add_to_cart/purchase — the module sees it
The module watches the client-side dataLayer and if it sees, alongside our events, view_item, add_to_cart, view_cart, begin_checkout, purchase and other e-commerce events sent by someone other than OcBox (for example, another remarketing / analytics module running in parallel), it records this and shows a yellow warning on the "AI Assistant" tab with the list of events and a suggestion: enable "Data Layer only" or turn those same events off in the other module. When there are no conflicts — a green "no conflicts detected" tick.
⚠ Without this: two modules fire the same purchases into GA4 and Facebook in parallel, reports show x2 conversions, and your ROAS optimiser drifts off reality.

AI setup assistant + AI insights in reports

✓ One button — and the model checks your config and reports
Hit "AI assistant" — the module sends OpenAI an anonymised snapshot of your config (which providers are on, whether server tokens are set, which events are active) and returns a plain-language read-out: what already works, what is missing, what to do next. A second button "AI insights" on the Dashboard compares the chosen period to the previous equal-length one, spots anomalies (sales spikes/dips, changes in top products, weird behaviour from a source) and produces a short takeaway with recommendations. The OpenAI key can be entered right in the module on the "AI Assistant" tab, or the shared store-wide key is picked up (from other OcBox modules like AI Chat or Product Editor). The key is stored encrypted. No customer data is sent — only numbers and flags.
⚠ Without this: you drop in a pixel, forget the Access Token, do not notice the server side is dead, and burn ad budget on blind tracking for months.

Google Merchant product feed — dynamic remarketing out of the box

✓ Feed with g:-fields, CRON build, static delivery on tens of thousands of products
A separate "Google Merchant Feed" extension serves a ready XML with every Merchant Center field: id, title, description, images (up to 10 additional), price/sale_price with proper tax handling, availability (in_stock / preorder / backorder / out_of_stock), brand, GTIN, MPN, product_type, google_product_category, shipping with shipping_weight in the right units, custom labels, multipack. The feed is built on a schedule by a separate CRON job, written atomically to a temp file and swapped in as the current one in a single move — Google never sees a broken XML. The public feed URL responds instantly (milliseconds) even on 30-50k catalogues, a "Build now" button runs a background rebuild, the ready CRON command is shown right on the settings page, and a "Feed build status" block shows when the last build was, product count, file size, and the last build message. This is the foundation for Performance Max, Shopping campaigns and Google Ads dynamic remarketing.
⚠ Without this: no feed means no Shopping ads and no dynamic remarketing, Google Ads only runs text.

Google Customer Reviews — post-purchase survey and rating badge

✓ Opt-in survey after checkout + trust badge with rating
Enter your Merchant ID, set an expected delivery window — and on the "Thank you for your order" page Google surveys the customer, while in the site footer you show a badge with the average "Google Customer Reviews" rating. That is the real Google five-star icon, not some third-party "bought a badge".
⚠ Without this: no Google merchant reviews, no yellow stars next to your listing in the SERP, lower CTR than competitors.

Telegram notifications — new order and status change straight to chat (with group topic support)

✓ Telegram bot, chat-ID auto-detection, templates with macros, group topics
Create a bot with @BotFather, drop in the Bot Token, auto-detect the Chat ID with a click (several are fine, comma-separated — your own, managers, a support group) — and every new order lands in Telegram instantly, while status changes come through filtered by the statuses you chose. If your team works in a Telegram group split into forum topics, in the Chat ID field you can specify the group ID, a colon and the topic ID: -1001234567890:42 — and the message will land in the "Orders" topic, not the general chat. Formats can be mixed with commas. Templates support macros like {order_id}, {customer_name}, {total}, {products} and more.
⚠ Without this: the order arrives at night, you see it in the morning, and the customer has already left for a competitor.

Custom scripts — drop in third-party tags with no template edits

✓ Custom tags in head / body-start / body-end, with page filter, consent, and edit-in-place
Need to add a Google domain verification tag, a competitor chat widget, another counter or a pixel for a really niche network — the "Custom scripts" tab lets you add it, pick a position (head, body-start, body-end), filter which pages to inject on, and decide whether GDPR consent is required and under which category. Scripts can not only be added and deleted, but also edited — the pencil icon next to the trash opens the same form with fields pre-filled.
⚠ Without this: every theme update wipes your hand-inserted scripts, or they collide with the new template.

Client + server with dedup — accurate conversions in spite of ad blockers

✓ One event_id across client and server, dedup on the network side + purchase double-count guard
Every store event gets a single event_id that is sent to the client pixel and to the server API. The network figures out it is the same event and counts it exactly once. On top of that purchase has an extra safeguard: a service table remembers every already-sent order so a purchase can never be double-counted. One shopper action = exactly one event: if the theme duplicates "Add to cart" through both jQuery and modern fetch, the module de-duplicates the noise in a short window. Product data in every event is always complete (name, brand, price with sale and tax in shopper currency, quantity) — no zero prices, no empty brands. The module also converts amounts into the order currency so ROAS math is correct.
⚠ Without this: either half your events disappear behind ad blockers (client only), or they double up (client + server without a shared event_id), or they come in with zero prices, or every purchase fires x2 — either way, the reports are chaos.

Custom checkout — Chameleon, quickcheckout and the like

✓ begin_checkout, add_shipping_info, add_payment_info work on every checkout theme
Historically many trackers listened only to the stock OpenCart checkout, and on custom themes (Chameleon, custom ocStore checkouts, quickcheckout themes) the middle funnel steps simply vanished. Now the module recognises any checkout page by the presence of the word checkout in the URL and automatically listens for shipping and payment method changes both through classic forms (form-urlencoded) and through AJAX with JSON body; the shipping_tier/payment_type field always carries the human-readable method name (e.g. "Nova Poshta") rather than the internal code. One method change = exactly one event, even if the theme repaints the form several times.
⚠ Without this: the GA4 "Cart → Checkout → Shipping → Payment → Purchase" funnel shows empty middle steps, and conversion counts are wrong.

Secrets encryption — Access Tokens and API Secrets no one reads from the database

✓ Secrets encrypted with the store key, decrypted only at send-time
Meta Access Token, TikTok Access Token, GA4 API Secret and other sensitive fields are stored in the DB not in plain text but encrypted with OpenCart's built-in Encryption class using the store key. Decryption only happens the moment the API is called. A dumped database without the encryption key does not hand an attacker your ad account tokens. Flood protection uses the real visitor IP even behind Cloudflare and similar CDNs, so the limit does not cut off genuine traffic.
⚠ Without this: a leaked DB backup = every one of your ad accounts leaked and someone else running ads on your dollar.

Universality — works via OpenCart events, on any theme, OpenCart 2.3 and 3.x

✓ No template edits, no "paste this into footer.tpl"
Every pixel and script is injected via the module's own OCMOD, automatically on any theme (LuxShop, CyberStore, Chameleon, Prime, stock Default, whatever). Store event data flows through OpenCart's built-in events — no controller rewrites or template hacks. Update the theme, the module keeps working. The module installs both on OpenCart 3.x (.twig files) and OpenCart 2.3 (.tpl files) — two separate builds, take the one for your branch. On OpenCart 2.3 the dataLayer, consent banner and events for product view, add-to-cart, checkout and payment fully render, not only the server-side purchase logging.
⚠ Without this: the classic "paste GA4 into header.tpl" guides break every time you update the theme or swap the template.

Setup wizard — 15 minutes from zero to working tracking

✓ Step-by-step helper with links "where to find each ID"
The "Setup wizard" button at the top of the module page walks you through the minimum useful set of steps: connect GA4, add Meta Pixel + CAPI, TikTok, consent banner, Telegram, test event and tracking check. Once completed, the flag is remembered and the wizard does not pop up on its own; the button label changes to "Run the wizard again" so you can rerun it any time (for example, after a module update or when adding a new store to the same admin).
⚠ Without this: the first-time setup drags on for days while you read Meta / TikTok / Google docs.

What this means in plain terms

Previously, to wire all of your marketing into an OpenCart store, you had to: paste GA4 into the theme, then Meta Pixel separately, then TikTok separately, then Google Ads, then figure out server-side (usually you didn't), install a separate Google Merchant feed module, install a separate Telegram module, wrestle with the GDPR banner on its own, merge UTMs into Excel by hand, and pay freelancers for the setup. OcBox AI Remarketing rolls all of that into a single admin tab. Fill in your IDs once, tick the boxes you want, walk the wizard, watch the self-check go green — and your store stops being blind to your ads.

Why OcBox over a typical analytics setup

A short side-by-side, without naming any specific competing developer or module. The left column is what OcBox AI Remarketing does out of the box; the middle column is the typical scenario where the same jobs are covered by separate modules from different authors (one per system); the right column is what stock OpenCart gives you with no add-ons at all.

The wording "usually a separate module", "partial" and "none" refers to typical scenarios in the niche, not to a specific product from a specific author. Your particular module may cover one or another of these features to some degree; the point of the table is not to bash anyone, but to show how many different jobs a single OcBox module closes instead of a stack of separate ones.

Who this module is for

For any OpenCart or ocStore shop that has ever paid for Google Ads, Meta or TikTok advertising and noticed that the ad platform reports never match the real orders. Especially — for stores without a dedicated marketer, where the owner does everything and has no time to dig into the theme or fight Consent Mode. And especially for OpenCart 2.3 stores where other trackers often only run in half-mode.

Compatibility

The module runs on OpenCart 3.0 and ocStore 3.0, and equally on OpenCart 2.3 and ocStore 2.3: two separate builds, we compile the one you need for your branch. PHP 7.x to 8.x, MySQL 5.7+, any theme (stock Default, Cyberstore, Prime, Chameleon, LuxShop and any other). The ionCube compilation for your domain is done automatically after payment.

License renewal for updates

The module price includes one year of support from the OcBox Team. After 12 months from the purchase date the module keeps working; to keep receiving new versions you renew at $40/year. The annual fee covers new module versions. Recompilation for a new domain, on-server install, consultations and personal support are not included and are ordered separately.

How to buy and receive the module

There is no downloadable file on this listing page, it is a showcase for the module. The flow is simple: click "Buy" on this page and complete the purchase through the forum, or send a private message to OcBox. Once payment lands we confirm your working domain (and, optionally, a test one), generate a licensed ionCube build locked to your domain for one year, and give you download access to the module together with install instructions in three languages. For those who prefer not to install it themselves there is the "Installation and setup" service for $40 available as an option next to the module (we install it on your server via FTP/SSH, wire up GA4/Meta/TikTok from your IDs, enable the consent banner, and walk you through usage). One year of updates is included in the price.

Recommended paid OcBox modules

Smart Related $30 — related products	SEO FAQ AI $30 — AI FAQ + Schema.org	AI Product Editor $50 — bulk product editing
Image Pro $15 — WebP, watermark	Filter $30 — smart filter + SEO	Category Manager $15 — visual category manager
AI Smart Search $200 — AI search with synonyms	AI Chat $100 — AI assistant 24/7	AI Photo Studio $50 — AI photo processing

We recommend templates by 29aleksey

Works best with fast templates. 29aleksey makes top-tier OpenCart 2.3/3.0 templates focused on speed and out-of-the-box optimisation:

Prime	UpStore	CyberStore
Chameleon	LuxShop	NewStore