AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Algo Ad Bidding

skill-asgard-ai-platform-skills-algo-ad-bidding · by asgard-ai-platform

Implement and select ad bidding strategies from manual CPC to automated target-CPA and target-ROAS. Use this skill when the user needs to choose a bidding strategy, set up automated bidding, or optimize bid parameters — even if they say 'what bidding strategy should I use', 'target CPA setup', or 'smart bidding configuration'.

No reviews yet
0 installs
20 views
0.0% view→install

Install

$ agentstack add skill-asgard-ai-platform-skills-algo-ad-bidding

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-asgard-ai-platform-skills-algo-ad-bidding)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
2mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Algo Ad Bidding? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Ad Bidding Strategies

Overview

Bidding strategies determine how much an advertiser pays per auction. Range from manual CPC (full control) to automated strategies (Target CPA, Target ROAS, Maximize Conversions) that use ML to optimize bids in real-time based on contextual signals.

When to Use

Trigger conditions:

  • Choosing between manual and automated bidding strategies
  • Setting up or troubleshooting Target CPA / Target ROAS campaigns
  • Analyzing bid strategy performance and making adjustments

When NOT to use:

  • When designing the auction mechanism itself (use GSP/VCG)
  • When building a CTR prediction model (use CTR prediction skill)

Algorithm

IRON LAW: Automated Bidding Requires SUFFICIENT Conversion Data
Below ~30 conversions/month, the algorithm lacks signal and performs
WORSE than manual bidding. Strategy selection depends on data volume:
- < 30 conv/month: Manual CPC or Maximize Clicks
- 30-50 conv/month: Maximize Conversions
- 50+ conv/month: Target CPA
- 50+ conv/month + revenue data: Target ROAS

Phase 1: Input Validation

Assess: monthly conversion volume, conversion tracking accuracy, campaign budget, business goal (volume vs efficiency vs revenue). Gate: Conversion tracking verified, sufficient data for chosen strategy.

Phase 2: Core Algorithm

Manual CPC: Set bid per keyword. Adjust based on: device, time, location, audience performance data.

Target CPA: 1. Set target cost-per-acquisition. 2. Algorithm predicts conversion probability per auction using contextual signals. 3. Bids up for high-probability conversions, down for low. 4. Aims to average at target CPA over time.

Target ROAS: Same as CPA but optimizes for return on ad spend = conversion_value / cost.

Phase 3: Verification

Monitor: actual CPA vs target, conversion volume stability, impression share changes, budget utilization. Gate: Actual CPA within 20% of target after learning period (2-4 weeks).

Phase 4: Output

Return strategy recommendation with expected performance ranges.

Output Format

{
  "recommendation": {"strategy": "target_cpa", "target": 500, "currency": "TWD", "confidence": "high"},
  "expected_performance": {"cpa_range": [400, 600], "volume_change": "-10% to +15%"},
  "metadata": {"monthly_conversions": 85, "current_cpa": 550, "learning_period_days": 14}
}

Examples

Sample I/O

Input: E-commerce campaign, 120 conversions/month, current CPA=NT$450, goal: maintain CPA, increase volume Expected: Target CPA at NT$450. Expected: volume +10-20% as algorithm finds efficient auctions.

Edge Cases

| Input | Expected | Why | |-------|----------|-----| | 10 conversions/month | Manual CPC | Insufficient data for automation | | Target CPA too aggressive | Volume drops to near zero | Algorithm can't find profitable auctions | | Conversion tracking broken | All strategies fail | Garbage data → garbage optimization |

Gotchas

  • Learning period volatility: First 2 weeks after switching strategies show unstable performance. Don't change targets during this period.
  • Conversion delay: If conversions take days to attribute (e.g., B2B), the algorithm optimizes on stale data. Use conversion modeling or extend the attribution window.
  • Budget as a constraint: Target CPA won't spend if it can't hit the target. Setting an aggressive CPA with a large budget doesn't increase spend — it just saves money.
  • Micro-conversions: If training on a proxy conversion (add to cart) instead of final purchase, the algorithm optimizes for the proxy. Ensure the tracked conversion aligns with business value.
  • Seasonality shocks: Automated bidding learns from recent data. Black Friday, holidays, or competitive events can throw it off. Use seasonality adjustments.

References

  • For bid strategy migration playbook, see references/migration-playbook.md
  • For learning period best practices, see references/learning-period.md

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.