Omnikyo/Help Center
How-to

Set up the Meta Pixel and Conversions API

Paste your Meta Pixel ID and access token once. Test that both browser and server tracking work, and your store sends events to Meta automatically.

বাংলায়: Settings-এ আপনার Meta Pixel ID এবং access token পেস্ট করুন। Server events চালু করুন যাতে অর্ডার Meta-এ সার্ভার থেকেও পৌঁছায়। তারপর test mode এ একটি dummy অর্ডার করে দেখুন tracking কাজ করছে কিনা। সেটা আপনার বিজ্ঞাপনকে আরও ভালো করবে।

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

The store picks up the settings within 15 minutes.

Before you start

You need a Meta Pixel in Facebook Events Manager. If you do not have one yet, create it in Events Manager first, then come back here.

You are setting up one Pixel for your entire store. All orders and customer actions are sent to the same place. If you later choose a different Pixel, it overrides this one.

Set up your Pixel ID

  1. Open Settings › Marketing › Ads and tracking › Facebook and Instagram › Pixel tab.
  2. In the Meta Pixel group, you will see the Pixel ID row (unless you have connected Facebook login; if you have, follow "Choose your dataset with Facebook login" below).
  3. In Events Manager, open your pixel, find its name and the ID number below it. Copy the number.
  4. In the Pixel ID field, paste the number. Whitespace is stripped automatically. The field shows "1234567890123456" as a placeholder.
  5. If this is the first time you are setting a Pixel ID, Omnikyo stamps a "Pixel connected at" time and includes it with your tracking data.

The Pixel ID appears in the status bar at the top right. You will see it move from Not set up towards Browser only or Tracking on as you add other fields.

Good to know: The store caches the Pixel ID for 15 minutes. If you change it here, your store's pages will use the new ID within about 15 minutes. Publishing the store speeds this up.

Turn on server events

  1. In the same Meta Pixel group, find the Server events switch. It is off by default.
  2. Turn it on.
  3. If you have not connected Facebook login, a new row appears: Access token. You must paste a token here. If you have connected Facebook login, the login's token is used automatically; no separate field appears.

The switch controls whether Omnikyo's servers send events to Meta using the Conversions API. With it on, Meta gets sales data even if the shopper's browser has an ad blocker. Without it, only the browser sends events (status shows Browser only).

Paste the access token (if not using Facebook login)

If you are using Facebook login for your pixel, skip this section — your login's token is used automatically. If you are not using Facebook login, follow these steps.

  1. Open Facebook Events Manager in another tab.
  2. Navigate to your Pixel → Settings → Conversions API → Generate access token (or "Create new access token" if one exists).
  3. Copy the token. It is a long alphanumeric string starting with key_.
  4. Return to the Omnikyo Pixel tab.
  5. In the Access token field (below Server events), paste the token.
  6. The field shows it as a masked value (dots). Omnikyo stores it encrypted.

With a token saved, the status moves to Tracking on if a Pixel ID is also set. Without a token, the status stays Browser only.

Careful: The token has no expiry date shown in this field. If you rotate the token in Events Manager without updating it here, Omnikyo stops sending server events silently.

Choose your dataset (pixel) with Facebook login

If you have connected Facebook login to Omnikyo (for Ads, inbox, or catalog), you can choose which Pixel (dataset) to use through that login, and Omnikyo will use the login's access token automatically. No separate token paste needed.

  1. In the Pixel tab, go to the Account tab (same page).
  2. Look for "Facebook, Instagram & WhatsApp". If it shows "No login yet", click Continue with Facebook first, then come back.
  3. Find the Dataset (Pixel) row. It shows a list of available pixels (datasets) from your Facebook business accounts and ad accounts.
  4. Select the one you want to use. The field shows Don't use (no pixel) by default.
  5. Omnikyo writes the dataset's ID as your Pixel ID automatically.
  6. Click Save accounts. A toast confirms "Saved" or "Omnikyo now works with these accounts."

Now when you go back to the Pixel tab, the Pixel row shows the dataset's name and ID in read-only format (you cannot change it here, only in the Account tab). The access token is also locked in — it comes from your Facebook login.

If you disconnect Facebook or choose Don't use (no dataset), the Pixel ID is cleared. To use a different Pixel, either choose another dataset in Facebook login, or switch back to pasting a Pixel ID by hand.

Save your changes

After entering the Pixel ID and (if needed) the access token, look for the Save button at the bottom of the page. Click it.

A toast at the top says "Pixel settings saved" or "Couldn't save" with an error.

Test your pixel and server events

Once the Pixel ID and access token are saved, test that both paths work.

1. Check in Events Manager

  1. Open Facebook Events Manager → your Pixel → Test events.
  2. Place a test order in your store as a customer would. Add an item to the cart, check out, and place the order.
  3. Watch Events Manager. Within a few seconds to a minute, you should see events arrive:
    • PageView — every page load
    • ViewContent — the product page
    • AddToCart — when you added to cart
    • InitiateCheckout — when checkout opened
    • Purchase — the order placed

If you see these events, both browser and server tracking are working. The status in Omnikyo is Tracking on.

2. Use the test mode in Settings (optional)

  1. Back in the Pixel tab, find the Check it works group.
  2. In the Test event code field, paste a code from Events Manager → your pixel → Test events → copy the code at the top.
  3. The field shows "TEST12345" as a placeholder.
  4. Save the settings. A warning appears: "Test mode is on. Server events and orders aren't counted in your ad results until you clear the code."
  5. The status changes to Test mode (warning).

While a test code is set:

  • Your store's events still arrive, but Meta counts them only in the Test events tab, not in your campaign results.
  • Your ads' ROAS and conversion numbers are not affected.
  • The code works for both browser and server events.

3. Clear the test code

Once you confirm tracking is working:

  1. In the Check it works group, the Test event code field shows a Clear code button (or you can just empty the field).
  2. Click Clear code or delete the text.
  3. Save. The status returns to Tracking on or Browser only (depending on whether the access token is set).
  4. Now events count toward your real ad results.

4. Send test events from this page (optional)

Below the test code field is a Send test events section. If your Pixel ID is saved, you can test the pixel from this Settings page itself.

  1. Click Start the pixel here. A button appears once the Meta script loads.
  2. You will see four buttons: Page view, Product view, Add to cart, Checkout started. Each button is labeled "Send", then "Sent", then "Sent ×2" if you press it again.
  3. Click them in any order. They fire sample events from your browser on this page only.
  4. Within a few minutes, these events appear in Events Manager under your pixel (in the Test events tab if a test code is set).

Good to know: The test bench fires events from your own browser on the Settings page. It does not use your store's script or the test event code (unless you pasted one, the code reaches the store, not this bench). These test events are useful for checking that your Pixel ID is valid and the Meta script loads, but they are not a full test of your store's tracking. For that, place a real test order in your store.

What happens to old orders

If tracking was off and you turn it on later, past orders are not sent. Only orders placed after you save the settings are tracked. The order total is calculated the same way — this change only affects whether Meta is told about it.

If server events do not arrive

If you see the browser events (PageView, AddToCart, etc.) but no Purchase in Events Manager, or if the Events Manager Test events tab shows some events but not others:

  1. Check that Server events is on (the switch is turned on, not off).
  2. Check that an Access token is pasted and saved (not a blank field).
  3. Confirm the Pixel ID is correct. A wrong ID means events go to the wrong pixel in Meta.
  4. If you just saved the access token, wait a few minutes for Meta to register it.
  5. Check in Events Manager → your pixel → Settings → Conversions API → look for "Assigned active conversion events" — at least "Purchase" should be listed.

If you still see no server events after 5 minutes, read the troubleshooting page (see Related pages).

Other ways people ask this

  • pixel id paste korbo na na
  • access token paste korbo কেন
  • server events কী
  • test event code কোথায় পাব
  • test mode off korbo কেন
  • events manager এ events আসছে না কেন
  • facebook login দিয়ে pixel setup এর সুবিধা কী
  • pixel change korbo কিভাবে
  • test order দিয়ে tracking check করব কিভাবে
  • events manager এ purchase দেখছি না কেন
  • clear code button নেই কেন
  • pixel settings save হয় নি

Related pages

Related guides

Checked against the product on 2026-10-02.