Skro
Ad tracking and conversion attribution for media buyers
vsGood for
- Buyers running paid Meta (Facebook) traffic who need CAPI postbacks
- Affiliates, ecommerce and search arbitrage teams who want to start on a free plan
Not for
- Teams that want to self-host and keep tracking on their own servers
- Teams that need several users but only want the free plan
How you pay
Free plan (no credit card); paid individual and business tiers are prepaid monthly and priced by events, with overage billed at month-end.
What it is
Skro is a hosted ad tracker that puts spend, clicks, conversions and revenue from different traffic sources into one dashboard, with no server to run. Pricing is by monthly events and there is a free plan; Meta Conversions API and the Ads Manager come with every plan, while Meta automation rules need a paid plan.
Quick facts
- Type
- Hosted, so there is no tracking server to run; spend, conversions and revenue from all sources in one dashboard.
- Pricing model
- Priced by monthly events (visits, clicks, conversions); overage is billed at the plan's rate and tracking keeps running.
- Free plan
- €0: 250,000 events a month, 3 months of reports, 1 user, 1 integration, 20 campaign and tracking entries; no credit card.
- Paid plans
- Monthly, from Starter at €39 (2.5M events) to Enterprise at €449 (30M events).
- Postbacks
- S2S postbacks; the clickId parameter is required, with optional payout, status, transactionId and more.
- Meta CAPI
- Conversions API on every plan, sending conversion events and revenue to a Meta pixel.
- Ads Manager
- Every plan can pause ads and change bids and daily budgets in Skro; Meta automation rules are paid-only.
- Team
- Workspaces with per-member access; multiple users start on Team (5 users), and Enterprise has 10.
Sources: Skro website. Checked against official Skro pages on 2026.11.01. Rules change, so check the official site.
FAQ
Does tracking stop after the monthly event limit?
No. Events are still tracked and the overage is billed at the plan's rate, for example €0.03 per 1,000 events on Starter.
How does Skro send conversions to Facebook?
Connect the Meta Ads integration, enable Conversion API in that step, then add the event name (such as Lead), the pixel ID and an access token generated in Meta.
How does Skro connect to Zeydoo?
Pick the Zeydoo template, set the postback URL Skro generates as the global postback in Zeydoo, and add ymid={clickId} to the offer link.
My take
In my ProPush Constructor-to-Facebook postback chain, Skro receives the postback and passes it on to Facebook. If you are starting Facebook × Zeydoo and don't want to add cost, it is relatively better value, and it matches the setup in the tutorial.
How I run it
- I merge Constructor's small postbacks by clickId and, once they reach $0.25, send one postback to Skro, which passes it on to Facebook; each GEO has its own threshold.
Watch out for
- ProPush sends clickid while Skro expects clickId; when the case doesn't match, Skro silently ignores it with no error.
- One Constructor Claim can fire 7–9 postbacks; pass them all to Facebook and CAPI sees several Leads on one click, which throws off optimization.
New articles and quick notes from Peter.
Related articles 4
Mentioned in 4
The Skro name and logo belong to their owner and are used here only to identify the product. To correct or remove this page, email support [at] affnomy.com.