Send the right event to the right ad platform
Pixels in DarkCore are not just a single script pasted into a page. They are an event delivery layer: system events, custom conversion statuses and per-platform event names are mapped from the same registry that powers analytics, push and CRM.
Ad platforms optimize only on the events they receive. If install, lead, approve, deposit, rejected and buyout are all flattened into one generic signal, the platform learns the wrong thing and the buyer loses control of optimization.
Facebook and TikTok event maps today
DarkCore maps fixed events such as install, page view and view content, plus each active conversion status, to platform-specific event names for Facebook/Meta and TikTok.
Designed for more providers
The event-name model is provider-keyed, so planned connectors such as Google, Bigo, Reddit, X, Kwai and other ad platforms can reuse the same conversion registry instead of adding new columns for every source.
Per-event enable and override
Each event can be enabled, disabled or renamed for a pixel. Reject can be suppressed, approve can fire Purchase, install can fire a platform-appropriate lead/download event.
Custom statuses become platform signals
If your workspace creates approve, buyout or redeposit, those statuses can have pixel event names too. The ad account sees the outcome your business actually cares about.
Health and diagnostics stay visible
Pixel rows track active state, broken state and last error codes, so teams can see when event delivery is not healthy instead of discovering it after optimization drifts.
- ✓ Map real funnel events to platform events instead of flattening everything into one signal.
- ✓ Use custom statuses as optimization signals for ad platforms.
- ✓ Prepare one conversion registry for current and planned pixel providers.
- ✓ Disable noisy events such as reject where they should not optimize spend.
The related DarkCore pages Google and readers should connect with this topic.