Guides

Cafe24 Meta Pixel and Conversions API: Browser + Server Setup

Imagefactory · Published 2026-09-18

The Meta pixel on a Cafe24 store needs no code. Connect the pixel through the Facebook channel app under Sales channels, then save the connection method as Browser + server in the channel settings' Pixel / Conversions API event settings. Seven browser events and four server events, from page view to purchase, fire on their own. Verify them in the Test events tab of Meta Events Manager.

A browser-only pixel loses purchases behind ad blockers and in-app webviews, and Naver Pay orders only arrive as server events. That is why the connection method is browser + server.

Check whether it is already installed

Open the page source of your storefront (Ctrl+U on Windows, Cmd+Option+U on Mac) and search for these strings.

Install the Chrome extension Meta Ads Data Advisor (formerly Meta Pixel Helper) and open the store. The icon badge shows the number of pixel events. No badge means no pixel, and two pixel IDs mean duplicates. Installation and usage are in Meta's help article.

1) Remove any hand-pasted pixel code

1. Go to Store settings → Basic settings → Store info → Search engine optimization (SEO) → Advanced settings → Direct code input and delete any script starting with fbq. Check both the PC and mobile tabs.
2. Delete pixel code placed in skin files under Design → Design editor as well.

Cafe24 says to remove existing pixels before connecting the channel app. Only the script is removed; the pixel and its data on Meta's side remain.

2) Connect the Facebook channel app

1. In the Cafe24 admin go to Sales channels → Facebook → Facebook channel. If the menu is missing, install the Facebook channel app from the Cafe24 Store. It is free and Chrome is recommended.
2. On Home press Log in with Facebook, sign in and press Continue as ○○○.
3. Press Start setup and choose Facebook ads as the category. Add Facebook Shop or Instagram Shopping if you use them.
4. Choose the Business Manager (business portfolio) and press Continue. Create one with Create new if you have none.
5. Choose the Facebook Page, the ad account and the pixel in turn, pressing Continue each time. The pixel list shows only pixels assigned to that ad account. Create one with Create new if none appears.
6. Review the summary, set every app permission to Yes, then press Next → Done.

The procedure follows Cafe24's Facebook channel guide.

3) Verify the domain

1. Under Channel settings → Domain verification press Verify next to the primary domain. It uses the meta-tag method and completes automatically.
2. If it fails, press the gear icon next to Basic settings and complete the popup again.

The procedure follows Cafe24's domain verification guide.

4) Save the pixel / Conversions API settings as browser + server

1. On the Channel settings screen select Pixel / Conversions API event settings.
2. Under Connection method choose Browser + server and press Save.
3. On the same screen turn on personal data for the begin-checkout and purchase events. Hashed email and phone are sent, which raises event match quality.

The event list and steps are in Cafe24's pixel guide and the pixel / Conversions API settings guide. If Channel settings shows only Connect and Change settings buttons, you are on the old version and need to update first.

5) Confirm Naver Pay order sync

1. Under Sales channels → Naver → Naver Pay settings → Application info check that Order sync is On.
2. When it is on, Naver Pay orders arrive as InitiateCheckout in the browser when the buy button is clicked, and as InitiateCheckout plus Purchase on the server when payment completes.

6) Verify in Events Manager

1. In Meta Events Manager click Data sources on the left and choose the connected pixel. The pixel ID is on the Settings tab.
2. On the Test events tab enter the store URL in the website events box and press Open website. In the opened tab go from a product page to the cart, checkout and a bank-transfer order completion.
3. Watch PageView, ViewContent, AddToCart, InitiateCheckout and Purchase appear in order. Press Clear activity when done.
4. After 20 to 30 minutes, check the table under the Overview tab: the connection method should read Browser · Server, which means server events are arriving.
5. Click Purchase in the table, open View details → Event deduplication and confirm a deduplication key is shown.

The steps follow Meta's test events tool, deduplication and server event details articles.

Checklist

Six common blockers

My pixel is not in the list. Only pixels assigned to the ad account appear. Assign the pixel (dataset) to that ad account as an asset in Meta Business settings, then connect again.

Server events fell back to browser. Changing the Facebook password or permissions expires the token. Disconnect in the Cafe24 channel settings and connect again, per the Cafe24 FAQ.

Two pixel IDs show up. A tag is left in Direct code input or a design skin. Go back to 1) and remove it.

Naver Pay purchases are missing. Order sync in the Naver Pay settings is not on. Check 5).

Diagnostics says "the same event ID was received for multiple event instances". That is not an error. The browser and server send the same event_id and duplicates are being removed. Press Mark as resolved.

Channel settings only shows a Connect button. That is the old FBE version. Follow the update guide and the Pixel / Conversions API event settings item appears.

An agency needs a Cafe24 sub-operator account and Meta business partner access to do this for you. Why both the pixel and the Conversions API are needed is covered in Meta pixel and CAPI tracking, and checking all four channels at once is in One test order to verify conversion tracking.