Pixels
Connect Facebook, TikTok, and Google Ads, map events, and deliver server-side conversions.
Pixels send events and conversions to your ad account. Facebook, TikTok, and Google Ads are supported. Manage them in Pixels.
Connect a pixel
Create a pixel and provide:
- an optional internal name;
- optional tags for search and grouping;
- platform — Facebook, TikTok, or Google Ads;
- Pixel ID;
- Access Token for Facebook/TikTok;
- active state (a switch available while editing).
For a pixel to fire on a stream, select it as the default pixel in the stream editor's General section. Individual rules can override the pixel.
Name, tags, and search
The name is only used inside darkcore and does not change anything in the ad account. It can contain up to 200 characters. Without a name, the list shows Unnamed, while pixel selectors still show the technical Pixel ID.
A pixel can have up to 20 tags, each up to 50 characters. Search checks the name, Pixel ID, and tags. Names and tags also appear in pixel selectors for streams and event replay.
Google Ads
For Google Ads, enter the tag ID in the AW-… format and select a delivery mode:
- Browser Tag — a real Google tag on the page, only for page-view events;
- Server Tag — a server request to your sGTM container URL;
- OAuth — connect with Connect Google through the Google Data Manager API;
- Hybrid — Browser Tag for the page view plus OAuth for server-side conversions.
For OAuth or Hybrid, save the integration, select Connect Google, complete authorization, and provide the Google Ads customer ID. In Google mapping, set the Conversion Action ID for the required system events and conversion types.
A deposit, registration, or any event received through a postback is delivered only through the server path — sGTM or Google Data Manager API. darkcore does not imitate a browser event for it.
Map event names
Each pixel has an Event name settings section where every darkcore event is mapped to the platform event name. This includes system events (install, landing-page view, PWA launch) and every active workspace conversion type.
Typical default mappings:
| darkcore event | TikTok | |
|---|---|---|
| Registration | CompleteRegistration | CompleteRegistration |
| Deposit | Purchase | CompletePayment |
For each event, you can enable or disable sending and set a custom name if events in your ad account use another naming convention.
For Google Ads, map the Conversion Action ID instead of an event name. An optional browser conversion label is used only for a real landing-page view.
Which URL to put in the ad
If the stream has a default pixel selected, you do not need an extra parameter:
https://your-domain.com/If no pixel is selected or you need to override it for a campaign, pass the pixel integration ID in darkcore:
https://your-domain.com/?pixel_id=PIXEL_INTEGRATION_IDAdd subs for reporting or routing only when necessary:
https://your-domain.com/?pixel_id=PIXEL_INTEGRATION_ID&sub1=CAMPAIGN_IDCheck delivery
Open Tracker logs and select Pixel logs. You can find an event by click ID and check its status and platform response. When needed, filtered events can be replayed to another active pixel on the same platform.