For Admins
Ads Manager (Admin)
Admin β Ads Manager scores paid-ads performance by cost per qualified outcome (CPQO) β spend divided by admin-verified results, against a target you set. It's a separate module from the SEO Campaign Manager. Since 2026-11-06, each employee's monthly average score also sets a flat salary bonus (see Leaderboard & locking below).
Setting up a campaign
- Create β pick the website (the responsible engineer is suggested automatically from the site-ownership email match), the platform (Meta / Google Search / YouTube / LinkedIn / X / ChatGPT), the monthly budget, the qualified outcome name ("Demo booked", "Course enquiry"β¦) and the target CPQO (βΉ you're willing to pay per outcome).
- Activate β this approves the campaign and locks the targets. Changing budget/target/outcome afterwards requires a written reason and is recorded in a visible audit trail on the campaign page.
One open campaign per website per platform β the form warns about collisions (β marks websites with open campaigns); completed/archived campaigns never block the next round.
Feeding it data (your weekly routine)
- CSV import β export the per-day report from the platform (Meta Ads Manager, Google Ads, LinkedIn Campaign Manager, X Adsβ¦) and upload it on the campaign page. The importer is header-mapped (Meta's Day / Amount spent (INR) / Impressions / Link clicks, Google's Day / Cost / Impr. / Clicks, LinkedIn's Start Date / Total Spent / Impressions / Clicks all work), skips bad lines with an itemised log, and re-importing corrected files overwrites rather than double-counts.
- Manual day entry β a stopgap for quick numbers; a CSV row for the same day outranks it (source precedence: API > CSV > manual β one source per day, never summed). Campaign owners can also log daily numbers from their Ads page into the same manual slot β your CSV import always overrides them, so employee-logged numbers can never bend a score.
- Verify conversions β the critical admin job. When a real outcome happens, record it: date, quantity, source, note. Only these records score; employees cannot self-verify, and platform-reported conversion counts are never used for scoring.
Scoring
Score = 100 Γ target CPQO Γ· actual CPQO (actual = spend Γ· verified outcomes)
Bands (admin-tunable at Ads β Scoring settings): Exceeds β₯ 120, On Target β₯ 100, Needs Improvement β₯ 80, Underperforming below. Honest guard states replace fake zeros: Not Started (no spend), In Progress / Insufficient Data (spend under the minimum gate, open/closed month), Pending Conversion Validation (spend but no verified outcomes, month still open). A closed month with spend and zero outcomes scores 0. Over-budget is an independent flag. Every evaluation stores its full explanation, line by line.
Leaderboard & locking
Ads β Leaderboard ranks engineers by spend-weighted average score, with data-reliability badges (unscored campaigns, over-budget flags), expandable per-campaign rows, and each employee's salary bonus for the month β a rate on their scoreable spend: average β₯ Exceeds threshold β βΉ500 per βΉ10,000 (5%), β₯ On Target β βΉ200 per βΉ10,000 (2%), below β βΉ0, capped at βΉ5,000/month (rates and cap tunable in Scoring settings; a 0 rate disables a tier, cap 0 = uncapped). The rates are industry-anchored: agencies charge 10β20% of spend just to manage ads, so paying 5% only when the efficiency target is beaten stays cheap for the value, and the 2.5Γ gap between tiers keeps excellence the clear prize. Splitting a budget across platforms changes nothing β only total well-managed spend pays. The bonus lands on the salary calculation as an "Ads performance bonus" item.
Month-end order matters: lock the ads month first, then lock salary. Salary computation refreshes each user's ad evaluations live β locking ads first means the bonus freezes on final numbers. At month end, Lock month freezes every evaluation permanently β the same immutability as salary locking.
Example campaigns
Three reference campaigns (flagged example, badged violet on your index) show engineers a completed month per platform β read-only for everyone, excluded from the leaderboard and from my/team lists. They display their final locked month, not the current one. Manage them like any campaign from the admin side if the sample data ever needs refreshing.
Boundaries worth knowing
- Sessions show "β" for now β that KPI arrives with GA4 integration (Stage 2); clicks are platform-reported, not sessions.
- Campaigns with recorded data can't be deleted β archive them; performance history must survive.