Key takeaways
- «Golden audience» in ClikBy is a working practice, not a separate DB entity or a «create golden» button.
- The point: people reach the ads pixel after filtering (confirmed), not a raw click/bot.
- Assemble: promo link → domain/Smart Traffic → pixel → confirm SDK → Ads account.
- In the Audience tab look at bot_server / bot_filter / confirmed and the average conversion_score.
What «golden» means
A marketing label for the segment: «clicked the offer + passed the quality check + landed in the pixel». This is a hot core for retargeting — more expensive and cleaner than «all site visitors».
- Interest is recorded by a click on a promo/offer (not a random visit).
- Bots and «empty» pending must not inflate the pixel audience.
- Next — look-alike / retarget in Meta, Google, VK, etc.
This is not a separate module
There is no golden / «golden audience» entity in the code. There are: smart links, pixels, Smart Traffic, visit statuses, conversion_score, the Audience tab, interests in the Selena UI (up to 3 pairs from XML — hints, not an auto-filter of clicks).
If someone promises «clicked a button — Selena exported golden to Ads» — that is not the current product. Building a segment = your scenario + a pixel.
Segment recipe
A separate link to the offer
Promo destination; UTM/tag «Promo hot».
Domain or Smart Traffic
Otherwise pixels will not work as needed.
Ads-account pixel(s)
Facebook / Google Ads / VK — where the retarget will go.
Smart filtering + delay/events
pending → confirm; bots and unconfirmed must not feed the pixel.
pixel_notification if needed
consent{link_id} consent before tracking.
Test and scale
Check Network/Test Events, then traffic on the promo button.
The Audience tab
In the account look at the visit split: bot_server (server block), pending (waiting for SDK), confirmed, bot_filter (pending older than ~1 hour without confirm). Average conversion_score on confirmed shows «how close the visit is to the ideal» from Selena settings.
For a client report: the confirmed vs bot_* share is more convincing than overall «clicks from Ads».
The role of conversion_score
After confirm the service computes a 0–100 score (events, frequency, time, scroll, behavior, fingerprint). A high score is a guide to a «quality» visit among already confirmed ones. It does not replace the pixel and does not create a Meta segment by itself.
Optionally the score may be refined by the ML command (ml:fetch-predictions) — this is a background contour, not a manual «gold» button.
Case and playbook
The scenario case «hot segment via a promo» is already described in the knowledge base. The technical end-to-end flow is in the retargeting playbook.