Tracking
A Mumara ONE pixel tracks what people do on your site after they click — page views, add-to-cart, checkouts, purchases. Because a tracking id rides along on the link, those actions tie back to the exact recipient who clicked, so you can attribute revenue and retarget on behaviour.
Before </head>
<script src='…/mcevents.js'></script>
<script> psr("pixel_id","PageView",false); </script>
Events firing
What a pixel does
A pixel turns anonymous on-site activity into named, attributed signal. Three jobs, one snippet.
Fire an event whenever a visitor does something that matters — viewing a page, adding to cart, starting checkout, buying. Use the preset events or name your own, and the pixel posts each one to your Mumara ONE account as it happens.
When a recipient clicks a link in your campaign, a unique tracking id rides along on the destination URL. The pixel reads that id and ties every subsequent event to the exact person who clicked — so activity isn't anonymous, it's attributed.
Conversion events carry item, value, and currency, so a purchase isn't just a flag — it's revenue tied to the campaign and contact that drove it. That closes the loop from a send to the dollars it produced.
Two ways to send data
Create a pixel in a click (Setup → Pixels → Add New, name it, save), then choose how it receives data. Most people drop the JavaScript snippet on their site; the postback URL is there for when you'd rather send events server-to-server.
Install the pixel code
JSPaste the snippet before your closing </head> tag. It fires PageView on every load, and you call psr() for any other action.
psr("pixel_id", "AddToCart", true);
Three arguments: your pixel id, the event name, and a true/false flag — false tracks only recipients referred by your emails, true tracks everyone.
Send a postback URL
SERVERWhen a platform or affiliate can call back to a URL on conversion, point it at your pixel's postback endpoint with the event in the query string.
…/callbacks/pixel/pixel_id/?event=PageView
Pass tid to attribute the event to a recipient, or fire it bare for general traffic. Multiple events in one call are supported.
Recipient vs everyone
Add tid=%%tid%% to the destination links in your broadcast content. At send time, %%tid%% becomes a unique id for that recipient. When they click through and the pixel sees that id on the URL, it knows precisely who's on the page — and every event they fire is attributed to them.
Don't want recipient matching? Set the pixel to track globally and it counts everyone's activity for general site analytics — while still attributing the recipients it can identify. Recipient-scoped or whole-audience: your call, per event.
How a click becomes attributed
Broadcast link
example.com/offer?var1=%%tid%%
Sent
%%tid%% → 124-17858-98-48
Recipient clicks
pixel reads tid on the URL
Event fires
Purchase · matched to recipient
Events & conversions
A set of ready-made event names covers the common funnel out of the box — and any action you can describe, you can name and fire yourself.
For Mumara to treat an event as revenue, fire one of Purchase, Sale, or Conversion with three details attached:
item_name
Football
item_value
45.75
item_currency
USD
That records a 45.75 USD sale of a Football — attributed to the recipient if a tracking id was present.
Pixel analytics
Open a pixel's statistics and the data is already shaped into the questions you'd ask: how events trend, which fire most, and what revenue they produced — down to the geography behind each one.
Compare up to three events over a date range, with per-event breakdowns and totals for the last hour and 24 hours.
The most-fired events at a glance, each with its share and count — so you see where attention is going.
Sales-conversion events over a period, in graphical reports.
A table of conversion events with the tracking data behind each — geography, item name, currency, and earnings.
Every event fired, with tracking data, geography, browser, operating system, and more.
And it folds into campaign reporting: embed a tracking id in a broadcast's links and that broadcast's statistics gain Events and Conversions tabs — so you read on-site behaviour and revenue right beside opens and clicks.
Go deeper
Name your own events beyond the presets and fire them on any action.
Record sales with item, value, and currency — and tie revenue to campaigns.
Match events to the exact recipient who clicked through, via the tracking id.
First-party, on your own domain — recipient-scoped or global, your choice.
Why it matters
You can see that someone opened and clicked. What you usually can't see is whether they browsed, added to cart, or bought — the part that actually decides whether the campaign worked.
A pixel closes that gap. Because the tracking id travels with the click, the events on your site aren't anonymous traffic — they're the named recipient continuing the journey the email started. You learn that Tuesday's campaign didn't just get a 30% open rate; it drove a specific set of people to specific purchases worth a specific amount.
That attribution feeds the rest of the platform. On-site behaviour becomes data you can segment on — 'viewed pricing, didn't buy' — and trigger from, so a pixel event can start a re-engagement drip. The pixel isn't a reporting dead end; it's a behavioural source the whole account can act on.
And you choose the scope. Track only the recipients your emails referred for clean campaign attribution, or track everyone for general site analytics. Either way it's first-party — running on your own domain, posting to your own Mumara account.
What it answers
Opens and clicks are proxies. A revenue event with item and value ties a purchase back to the campaign and recipient, so you measure email in money, not metaphors.
Without on-site events you can't tell. A pixel records the add-to-cart and the abandoned checkout, so the segment and the retargeting drip become possible.
Anonymous traffic can't be acted on. The tracking id matches the visitor to the exact person who clicked, turning footprints into attributed signal.
Scattered analytics tools mean stitching reports together. The pixel's own analytics views — plus Events and Conversions tabs on the campaign — keep it in one place.
Common questions
Go to Setup → Pixels, click Add New, give it a name, and save. Then either paste the JavaScript snippet before your site's </head> tag, or use the generated postback URL to send events server-to-server. The snippet fires a PageView automatically; you call psr() for any other event.
You add a tracking id to your campaign's destination links as tid=%%tid%%. At send time %%tid%% becomes a unique id for each recipient, so when they click through and the pixel sees that id on the URL, it attributes every event they fire to that exact person.
Preset events cover the common funnel — PageView, AddToCart, AddToWishList, Lead, Register, Contact, InitiateCheckout, Purchase, Subscribe — and you can name and fire your own for anything else. Events fire on page load, on a button click, or via a postback call.
Fire a Purchase, Sale, or Conversion event with three extra details — item_name, item_value, and item_currency. Mumara records it as revenue, attributed to the recipient if a tracking id was present, and surfaces it in the conversion reports.
Yes. The pixel can run recipient-scoped (only visitors your emails referred) or global (everyone), set per event via the true/false flag in the snippet. In global mode it still attributes the recipients it can identify.
Each pixel has its own analytics — a comparison graph, top events, conversion stats, a conversions log (with geography, item, currency, earnings), and an events log (with geography, browser, OS). When a campaign carries a tracking id, its statistics also gain Events and Conversions tabs.
Related
Turn pixel events into audiences — "viewed pricing, didn't buy" becomes a segment.
Read moreFire a re-engagement drip when a pixel event (or its absence) signals intent.
Read morePixel revenue rolls into campaign reporting, so sends are measured in dollars.
Read moreThe revenue side of pixels — record sales with item, value, and currency, attributed to campaigns.
Read moreMumara ONE · Pixels
One snippet turns on-site activity into attributed, revenue-aware signal — matched to the recipient who clicked, ready to segment, trigger, and report on.
