Key takeaways
- Antifraud and AI Selena run in the specific client’s account — data is not “shared across the agency”.
- Visit statuses (bot / pending / confirmed), Smart Traffic, and Selena are the basis for a quality conversation.
- Pixels without a domain or Smart Traffic will not fire — check the conditions before blaming the “placement”.
- A report with risk factors is more convincing than “we feel the clicks are bad”.
One account per client
Run antifraud monitoring in the account of the brand whose budget you are discussing. Mixing links from different clients in one account breaks both reporting and billing.
1 account = 1 client — the agency working model in the current product.
What to look at
- Visit statuses and the bot share.
- Repeat IP/device, VPN/proxy/datacenter — based on signals available in reports.
- Mismatch between campaign geo and clicks.
- AI Selena explanations of risks (in plain language for the client).
- The effect of Smart Traffic / “Smart filtering” and pixel delays.
Diagnosis “pixel is silent / domain”: troubleshooting.
How to explain it to the client
- Show the period and channel (UTM / tag).
- Separate “clicks in the Ads account” from confirmed visits in ClikBy.
- Cite 2–3 risk factors, not only the final %.
- Propose an action: pause the source, change the creative, Smart Traffic, change the domain.
Do not promise a “budget refund from Meta/Google” on behalf of ClikBy — the platform provides quality evidence, and the advertiser/agency runs the dispute in the Ads account.
Agency actions
- Enable Smart Traffic and/or AI Selena on key links.
- Check the custom domain for pixels.
- Export the report and attach it to the weekly client status.
- Record the baseline before optimization and after.