Коротко
- Pulse → Advertising section (/advertising): Google Ads, Yandex Direct, and Facebook Ads (Meta) are connected.
- The point of the integration is to export antifraud data into the accounts, not to pull spend and clicks from there into ClikBy.
- Google and Yandex: IP block lists for selected campaigns. Meta: negative signals on bot fbclid (Conversions API); IP block is unavailable.
- You need smart links with real bot traffic in the data — otherwise there is nothing to sync. The platform administrator configures the OAuth app.
Where it is in the account
Open the Pulse → Advertising menu. There is a list of ad accounts: create, edit, connect via OAuth, start sync.
Google / Yandex / Meta app keys are set by the ClikBy administrator in platform settings. You do not need to paste an App Secret into the account card — only your ads Account ID and (for Meta) Pixel ID.
The account must be verified. If the Connect button says platform credentials are not configured — write to ClikBy support.
What connecting gives you — and what it does not
Делает
- Google Ads — adds fraud IPs to campaign negative criteria (up to 500 IPs per campaign); the list rotates by threat score.
- Yandex Direct — blocks IPs/subnets in campaigns (up to 25 slots per campaign; with ≥3 bots from one /24 the whole subnet may be blocked).
- Meta / Facebook Ads — sends negative signals via Conversions API (FraudDetected event with fbclid from bot visits). IPs are not blocked in Meta by this section — the platform has a different mechanism.
Does not
- Does not import spend, CPC, ROAS, or a «pretty account Dashboard» into ClikBy.
- Does not connect TikTok or LinkedIn as an ad account in this section (pixels on links are a separate story).
- Does not replace the pixel on a smart link and does not cancel the Smart Traffic setup.
The data source for sync is bot decisions and visits on your links (blocked / bot_server / bot_filter). Smart Filter safe mode writes would_block and does not enter this export.
Common steps
Create an account
Advertising → New: name, platform, Account ID.
Connect OAuth
On the edit page, click Connect (for Yandex — a separate flow with a code).
Set up sync
Fraud-data collection period 7/14/30 days, autosync every 6 hours if you want.
Select campaigns (Google / Yandex)
Load campaigns → mark campaigns for IP blocking → save.
For Meta, specify Pixel ID
And enable sending negative signals via Conversions API.
Sync now
Check the sync log. After that, scheduled autosync can run.
Google Ads
In Account ID, enter a Customer ID of the form XXX-XXX-XXXX (Google Ads → account settings). If the account is under MCC — fill in Manager Customer ID (MCC) when the API needs it.
- Create a Google Ads-type record and save.
- Click Connect — Google OAuth opens with access to Google Ads.
- After the Connected status, load campaigns and choose where to write IP exclusions.
- Turn on autosync or click Sync now.
- On the ClikBy side the administrator must have Client ID/Secret and a Google Ads API Developer Token — without a developer token the connection is not considered complete.
- Limit: up to 500 IPs per campaign; the list updates, and old IPs may be removed during rotation.
Without selected campaign_ids, IP sync to Google will not run — first Load campaigns and save the selection.
Yandex Direct
In Account ID — the account login or Client ID (as in the agency interface). In the API this is sent as Client-Login.
- Create a Yandex Direct-type record.
- Click get authorization code — oauth.yandex.ru opens (verification code).
- Copy the code and paste it into the «Connect by code» form.
- Load campaigns, select the ones you need, save, sync.
- Up to 25 BlockedIps records per campaign.
- Smart aggregation: if ≥3 bot IPs come from one /24 subnet, the system may block the whole subnet (one slot ≈ 256 addresses).
If validation fails after the code — check that the OAuth user has access to this Yandex Direct login.
Meta (Facebook Ads)
In the interface the platform is called Facebook Ads. Enter Ad Account ID (act_… or a number). The Facebook user you log in with for OAuth must have access to this ad account.
- Create a record → Connect → Meta authorization with the needed permissions (ads, business, and related scopes).
- Enter Facebook Pixel / Dataset ID — without it, negative signals will not go out.
- Turn on the option to send negative signals via Conversions API.
- Sync now or autosync every 6 hours.
How it works: ClikBy takes fbclid from bot visits on your links and sends a FraudDetected event to the pixel (in batches). This helps Meta optimization — do not confuse it with an IP-blacklist, which Facebook does not have in this integration.
For fbclid to appear, people must click Meta ads via ClikBy links (the URL usually contains fbclid). Without bot visits with fbclid, there is nothing to send.
Synchronization
| Setup | What it does |
|---|---|
| Autosync every 6 hours | The ad:sync-fraud command for accounts with auto_sync and an active token |
| Fraud-data collection period | 7 / 14 / 30 days — the window from which bot IPs and fbclid are taken |
| Sync now | Manual score recalculation + export of IP or fbclid signals |
| Sync log | Logs oauth_connect, ip_exclusion, fbclid_exclusion, token_refresh |
Tokens refresh in the background (if they expire in the coming days). Account statuses: Connected / Disconnected / Error.
Typical problems
- «Platform credentials are not configured» — the admin has not yet entered App ID/Secret (and Developer Token for Google).
- Google Connected, but sync is empty — no campaigns selected or no bot IPs in the period.
- Yandex: code accepted, access not confirmed — wrong Client-Login or no permissions.
- Meta: error without pixel_id — specify Pixel/Dataset ID and enable negative signals.
- Smart Filter safe mode — would_block decisions do not enter the fraud-IP collector for sync.
- No smart links / no bots in the data — connecting an account by itself does not fix the «silence».
First make sure detection on links works: detection guide. A plain-language explanation of fraud — здесь.