When using an ad cloaker, one question always comes up: how do conversion events get reported back to the ad platform? Without proper postback, your campaign optimization goes blind. WUXIANG SHIELD explains the complete pixel postback workflow for cloaking setups.

Why Postback Is Complex with Cloaking

Normally, a tracking pixel on your page reports events to the ad platform. But with cloaking, bots see your safe page — which shouldn't have your marketing pixel. And you don't want bot visits generating fake conversion events. You need server-side postback that only reports real user conversions.

WUXIANG SHIELD's Postback Workflow

  1. User clicks ad → URL contains platform click ID (fbclid, ttclid, gclid)
  2. WUXIANG SHIELD identifies the visitor as a real user
  3. System captures and stores the click ID
  4. User browses the marketing page normally
  5. On conversion, WUXIANG SHIELD sends the event + click ID to the ad platform via CAPI/Events API

Facebook CAPI Configuration

You need: your Pixel ID, a server-side Access Token (from Events Manager), and the event names you want to report. Enter these in WUXIANG SHIELD's dashboard — the system handles everything else automatically.

TikTok Events API Configuration

You need: your TikTok Pixel Code, an API Access Token, and event types. Same simple dashboard configuration.

Event Deduplication

If you run both browser-side pixel and server-side CAPI simultaneously, the same conversion could be counted twice. WUXIANG SHIELD uses event_id deduplication — the ad platform automatically ignores duplicate events with the same ID.

FAQ

Does postback data reveal that I'm using a cloaker? No. CAPI/Events API data is identical in format to normal pixel postback. The ad platform cannot distinguish the source.

Is there latency? WUXIANG SHIELD's postback is near real-time — typically within seconds of the conversion event.

Proper postback setup is what separates amateur cloaking from professional campaign management. WUXIANG SHIELD handles it out of the box.