Omnikyo/Help Center
Guide

Tracking and conversions

The Meta Pixel and Conversions API let you send shoppers' actions and orders to Meta, so your ads can find people like your buyers and measure sales accurately.

বাংলায়: Meta Pixel এবং Conversions API ব্যবহার করে আপনার দোকানে ক্রেতারা যা করে (পণ্য দেখা, পেমেন্ট করা) তা Meta-এ পাঠান। এতে আপনার বিজ্ঞাপন আরও ভালো মানুষদের কাছে পৌঁছায় এবং বিক্রয় সঠিকভাবে মাপা যায়। ডেটা দুই পথে যায়: শপারের ব্রাউজার থেকে এবং Omnikyo-র সার্ভার থেকে। নিজের ওয়েবসাইট থাকলে সেখানেও tracking কাজ করে।

Where to find it: Sidebar › Settings › Marketing › Ads and tracking › Facebook and Instagram › Pixel tab. Who can do it: Anyone with Integrations or Storefront Settings permission.

What it is

The Meta Pixel is a tracker that collects actions on your store — a page viewed, a product added to the cart, an order placed — and sends them to Meta (Facebook). The Conversions API is a server-side channel: instead of relying only on the browser, Omnikyo's servers also send these actions to Meta. Together they give Meta a fuller picture of what works in your ads.

You set this up once in Settings, and it tracks your entire online store automatically. If you also connect your own website (a hand-built Laravel or PHP site), the same Pixel works there too.

How it works

Two types of tracking happen at the same time.

When a shopper lands on your store, Meta's pixel script loads in their browser. As they browse — viewing a product, adding to cart, checking out — the script sends those actions directly to Meta. This happens even if they block cookies or use ad-blocker software. This is browser tracking.

At the same time, Omnikyo's servers also send the same actions to Meta using the Conversions API. This is a second, reliable path: if an ad blocker stops the browser pixel, the server still sends the sale. This is server tracking.

Why both? The browser pixel is fast and immediate; the server path is stronger for matching customers to their ad click, because it includes data Meta can use to link the shopper back to the person who saw your ad.

The Pixel ID and access token

The Pixel ID is a number — your store's identifier with Meta. You find it in Facebook's Events Manager under your pixel's name.

The Access token is a password that lets Omnikyo send events to Meta. You generate it in Events Manager (Pixel → Settings → Conversions API → Generate access token) and paste it into Omnikyo.

Without both, nothing is sent. With only the Pixel ID (and the browser pixel enabled), you get the browser path only — the status shows Browser only. With both, the status is Tracking on.

Online store vs. your own website

If you have an Omnikyo online store, tracking is built in. A shopper's actions (views, cart, order) are tracked automatically.

If you also connect your own website — a Laravel or PHP site you had built — the same Pixel works there. You add a script tag to your site, and Omnikyo sends those events to Meta as well.

If you have only your own website (no Omnikyo store), the Pixel can still track it. See "Connect your website" for setup.

What Meta gets (and what it doesn't)

Omnikyo sends these events to Meta:

  • PageView: every page visited
  • ViewContent: a product page viewed
  • AddToCart: an item added to the cart
  • InitiateCheckout: checkout page opened
  • Purchase: an order placed or paid

With each event, Meta also gets some data about the shopper — their email (hashed), phone (hashed), city (hashed) — and the browser they used (IP address, user agent). The hashing is for privacy: Meta cannot see the real email or phone, but can link the order back to someone who saw your ad.

Omnikyo does not send customer location data, product details beyond the id and price, or full customer names and addresses (only first and last name, hashed, for Purchase orders).

What does not appear in the event data at all stays private in Omnikyo — the internal notes you write on an order, your shipping costs, your profit.

Status pills: what they mean

The pill at the top right of the Meta Pixel group shows your setup status:

  • Not set up (muted): No Pixel ID has been entered.
  • Test mode (warning): A test event code is saved. Orders are not counted in your ad results; they show only in Meta's Test events tab. Remove the code to count real sales again.
  • Tracking on (success): Pixel ID is set, Server events is on, and you have an access token. Both browser and server tracking are active.
  • Browser only (warning): Pixel ID is set, but either Server events is off or there is no access token. Only the browser pixel is working; server events are not sent.

Test mode: what it does

When you paste a test event code (from Events Manager → your pixel → Test events), Omnikyo saves it and uses it for all events — browser and server. While the code is set, Meta counts events you send only in the Test events tab, not in your regular ad results. This is for checking that tracking works without affecting your campaign numbers.

Once you confirm everything is working, clear the code from Settings and save. Tracking goes back to counting real sales.

Cookies and storage: what shoppers' browsers keep

When a shopper visits your store, their browser keeps a few small pieces of data:

  • _fbp (90 days): Meta's own ID for this visitor. Lets Meta recognize them if they come back or see an ad later.
  • _fbc (90 days): Meta's click ID, if they arrived from a Meta ad. Helps Meta link the sale back to that ad.
  • Local storage (per session): Which products they viewed, when they started browsing, where they came from (if a UTM tag or fbclid was in the URL).

None of these contain the shopper's name, address, or payment details. They are used only to count views, carts, and orders.

There is no built-in consent banner. Omnikyo's Terms of Service (section 7) require that you tell shoppers in your store's privacy notice that you use the Pixel and get any consent the law requires in your country or theirs.

Where tracking happens

Tracking is set once in Settings and applies to your entire store. If you publish a new theme, the Pixel works the same way. If you change the Pixel ID or token, it takes effect within about 15 minutes (the store caches these settings).

For your own website, you add a script tag to your pages. The same Pixel you set up in Omnikyo runs there automatically.

Questions people ask

Does server tracking slow down my checkout?

No. Server events are sent in the background after the order is saved. The shopper sees "Order placed" immediately; Meta gets the event a moment later.

Can a shopper block the Pixel?

The browser pixel can be blocked by ad blockers. That is why the server path is important: even if the shopper's ad blocker stops the browser script, Omnikyo's server still sends the sale to Meta, so you do not lose that data.

What if I only want browser tracking?

Leave the Server events switch off and save. The status will show Browser only. You do not need an access token. However, this is less reliable, especially on iPhone where app-tracking prevention (ATP) blocks cookies.

Do I need to set this up?

Not strictly — your store works without it. But tracking helps your ads perform better. Most sellers should set it up even if they just paste a Pixel ID (no access token). That gets you browser tracking, which is better than nothing.

Other ways people ask this

  • pixel কী
  • meta tracking setup করব কেন
  • conversions api on off korbo kivabe
  • server events on korbo na off
  • meta pixel kothay paibo
  • আমার দোকানে কত মানুষ এসেছে meta বলবে কি
  • tracking on state মানে কী
  • events manager এ events দেখব কোথায়
  • facebook login দিয়ে pixel set করব কীভাবে
  • test mode এ orders count হবে
  • cookie permission দিতে হবে কি
  • own website এ pixel কাজ করবে কি

Related pages

Related guides

Checked against the product on 2026-10-02.