One Test Order to Verify Conversion Tracking: Checklist
Imagefactory · Published 2026-09-18
Before turning ads on, place one test order and confirm the same order in four places: Naver conversion tracking, the Google Ads conversion summary, GA4 DebugView and Meta Events Manager. If all four show it, conversion tracking is done. If any of them does not, go back to that channel's setup guide.
Why check four places separately?
Each channel receives conversions from Cafe24 through a different path. Naver uses the common key, Google Ads and Meta use the tags from Cafe24's channel apps, and GA4 uses the event you built in GTM. One channel recording the order says nothing about the others.
| Channel | How Cafe24 sends it | Where to check | Delay | Setup guide |
|---|---|---|---|---|
| Naver Search Ads | Purchase logs fire automatically once the common key is registered | Tools → Conversion tracking status, ad report conversions | Status after review, reports the next day | Naver conversion tracking |
| Google Ads | The Google & YouTube app tag sends browser and server events | Goals → Conversions → Summary status and count | Up to 24 to 48 hours | Google Ads conversion tag |
| GA4 | The purchase event you built in GTM | Admin → DebugView, Reports → Realtime | Immediate, standard reports 24 to 48 hours | GA4 on Cafe24 |
| Meta | The Facebook channel app's pixel and Conversions API | Events Manager Test events, Overview | Test events are immediate | Meta pixel and Conversions API |
The delays follow Google's conversion tracking data article and GA4 data freshness.
Step 1. Confirm the tags fire
This check needs no ads. You only confirm that the tags fire on the order-complete page.
- Open the store in an incognito window without ad-blocking extensions.
- Turn on the checking tools first. GA4 uses GTM
PreviewandDebugView, Meta theTest eventstab in Events Manager, Naver the Chrome extensionNaver Conversion Script Assistant, and Google Ads Tag Assistant. - Go from product page to cart to checkout to order complete and pay by bank transfer. Bank transfer reaches the order-complete page without a payment. Naver Pay and Kakao Pay skip that page, so do not use them for the test.
- Check each tool for the purchase event. GA4 should show
purchasewith a transaction ID and value, MetaPurchasefrom both browser and server, Naver apurchaselog, and Google Ads a fired conversion event. - Cancel the order in the admin when you are done.
Step 2. Confirm the ad click links to the order
Even when tags fire, the Naver and Google ad reports only count a conversion when the click parameter reaches the landing page. That is NaPm for Naver and gclid for Google. Meta also matches logged-in users in addition to the fbclid click parameter, but the same check applies. Do this once on the first day your ads run.
- Turn the ads on, search, and click your own ad once. One click is charged.
- Check that the landing page URL still carries a parameter such as
NaPm=orgclid=. If it is gone, the landing URL redirects or passes through a short link. - In the same window place a bank-transfer order as in Step 1.
- The next day, check for one conversion in the Naver ad report
Conversions, Google AdsConversionsand the Meta Ads ManagerResultscolumn.
Checklist
| Channel | Screen | Pass condition | If missing |
|---|---|---|---|
| Naver Search Ads | Tools → Conversion tracking | Status In use, one conversion in the next day's report | Check the common key and review status in Naver conversion tracking |
| Google Ads | Goals → Conversions → Summary | Purchase action status Recording conversions | Check the app toggle and event method in Google Ads conversion tag |
| GA4 | Admin → DebugView | purchase carries transaction_id and value | Check GTM publishing and the trigger in GA4 on Cafe24 |
| Meta | Events Manager → Test events | Purchase arrives from both browser and server | Check the connection method in Meta pixel and Conversions API |
What to check when it is missing, in order
Payment method first. Naver Pay and Kakao Pay orders skip the Cafe24 order-complete page. GA4 and browser pixels never see them, and Google Ads and Meta only receive the Naver Pay orders Cafe24 sends as server events. Test with bank transfer.
Then the browser. Ad blockers, declined cookie consent and in-app webviews block browser tags. Try again in an incognito window.
Then where the tag lives. A common miss is pasting the GA4 Direct code input into the PC store tab only. If the order was placed on mobile, check the mobile tab.
Then the channel-side status. Naver Not in use means no purchase log has ever arrived, and Google Ads Unverified means no conversion has been recorded yet. Repeat Step 1.
Then the click parameter. If it disappeared in Step 2, remove the redirect or short link on the landing URL. For Naver, NaPm must survive to the final landing page for the report to count it.
Where Imagefactory helps
Imagefactory builds AI marketing tools and runs ad operations for clients. When you hand over operations, we fill in this checklist for you in the first week. We check that every channel's tag is on the page, confirm the four places with a test order, and only then turn the ads on. The first week's job is to make sure no ad spend goes out while conversions are not being recorded.