Facebook Autolaunch and Autofill: What Media Buyers Need to Know

Autolaunch — known in the CIS media buying community as автозалив (avtozaliv, literally "auto-pouring") — is the single most defining feature of the grey-hat Facebook advertising ecosystem. It is the reason these tools exist, the workflow that drives their adoption, and the capability that no official tool could replicate until recently.

Understanding facebook autolaunch autofill is understanding the operational core of grey-hat media buying. This guide covers the mechanics, the tools, the workflow variations, and how official API alternatives now address the same need.

What Autolaunch Actually Is

At its core, autolaunch is automated mass campaign creation across multiple Facebook ad accounts. But that definition understates the sophistication of what modern autolaunch tools do.

A complete autolaunch workflow includes:

1. Account selection — choosing which ad accounts to launch on (based on account health, spending limits, geographic targeting)
2. Template configuration — defining campaign structure (objective, budget, targeting, creative, placements)
3. Variation generation — creating variants across accounts (different creatives, different copy, different landing pages)
4. Payment binding — attaching payment methods to accounts before or during launch
5. Batch execution — launching across all selected accounts simultaneously
6. Status monitoring — tracking which campaigns passed review, which were rejected, which accounts were flagged
7. Replacement cycle — killing flagged accounts, sourcing replacements, relaunching

This is not "create a campaign and duplicate it." It is an industrial process optimized for throughput, resilience, and speed.

The Campaign Creation Flow

1Step 1: Template Design

Every autolaunch starts with a campaign template. The template defines every parameter:

Campaign Level:

• Objective (Conversions, Traffic, Engagement)
• Campaign budget optimization (CBO) settings
• Special ad categories
• Naming convention (often with dynamic variables: {account_id}_{geo}_{date}_{variant})

Ad Set Level:

• Targeting: age range, gender, interests, behaviors, custom audiences
• Geographic targeting (countries, regions, cities, radius)
• Placements (Facebook Feed, Instagram Feed, Stories, Reels, Audience Network)
• Budget (daily or lifetime)
• Schedule (start/end dates, dayparting)
• Optimization goal (conversions, landing page views, link clicks)
• Bid strategy (lowest cost, cost cap, bid cap)
• Attribution window

Ad Level:

• Creative type (single image, video, carousel)
• Media files (images or videos with file paths or URLs)
• Primary text (ad copy)
• Headline
• Description
• Call-to-action button (Learn More, Shop Now, Sign Up)
• Destination URL (with UTM parameters)
• Tracking pixel
• URL parameters

2Step 2: Variation Matrix

Sophisticated autolaunch setups create variation matrices. Instead of launching identical campaigns everywhere, the system generates combinations:

• 5 creatives x 3 copy variants = 15 ad variations
• Across 4 geos = 60 ad set configurations
• Across 20 accounts = 1,200 individual ads launched

Tools like Nooklz allow importing this entire matrix from a CSV/Excel file. Each row defines one unique combination, and the tool maps columns to campaign parameters.

Example CSV structure:

account_id,geo,creative_url,headline,body_text,landing_url,budget
acc_001,US,img_01.jpg,"Headline A","Body text 1",https://lp1.com,50
acc_001,UK,img_02.jpg,"Headline B","Body text 2",https://lp2.com,30
acc_002,US,img_01.jpg,"Headline A","Body text 1",https://lp1.com,50
acc_002,DE,img_03.jpg,"Headline C","Body text 3",https://lp3.com,40

3Step 3: Payment Method Binding

Before campaigns can spend, ad accounts need payment methods. Autolaunch tools handle this in three ways:

Method 1: Manual Card Binding

• Operator manually adds a credit/debit card to each ad account
• Most reliable but slowest
• Cards are often virtual cards from services like PST.net or Capitalist
• Common pattern: one virtual card per account to limit risk exposure

Method 2: Automated Card Binding via RPA

• Tool navigates to payment settings in each account
• Auto-fills card details (number, expiration, CVV, billing address)
• Card details stored in tool's database, mapped to accounts
• Faster but more detection risk (payment addition is heavily monitored by Meta)

Method 3: BIN Generator + Virtual Cards

• BIN (Bank Identification Number) generators create card numbers with specific bank prefixes
• Combined with virtual card services that issue real, spendable cards
• Some tools integrate directly with card providers via API
• Highest automation but highest risk — Meta monitors for virtual card patterns

Method 4: Pre-loaded Accounts

• Accounts purchased with payment methods already attached
• "Spend-ready" accounts cost more ($20-100+) but skip the payment binding step
• Common in high-volume operations where time is more valuable than per-unit cost

4Step 4: The Launch

With templates configured, variations defined, and payment methods bound, the actual launch happens in one of two ways:

Token-Based Launch (API):

The tool makes Marketing API calls using extracted EAAB tokens. For each account in the batch:

1. Verify token validity
2. Check account status (active, not restricted)
3. Create campaign object
4. Create ad set(s) with targeting
5. Upload creative assets
6. Create ad(s) linking creative to ad set
7. Set campaign status to ACTIVE
8. Log result (success/failure/error code)
9. Move to next account

Speed: 3-10 seconds per account. 50 accounts in 3-8 minutes.

RPA-Based Launch (Browser Automation):

The tool opens browser profiles one by one (or in parallel batches) and fills Ads Manager forms:

1. Open anti-detect browser profile
2. Navigate to facebook.com/adsmanager/creation
3. Select campaign objective (click)
4. Fill campaign name
5. Configure budget and schedule
6. Set targeting parameters (multiple clicks and selections)
7. Upload creative (file dialog interaction)
8. Enter ad copy, URL, CTA
9. Click Publish
10. Wait for confirmation
11. Close profile, open next

Speed: 60-180 seconds per account. 50 accounts in 50-150 minutes.

The speed difference explains why token-based tools dominate the autolaunch market.

5Step 5: Post-Launch Monitoring

Launching is only step one. Post-launch monitoring is where autolaunch tools differentiate:

Review Tracking: Campaigns enter Meta's ad review queue. Autolaunch tools monitor review status and flag rejections. In grey-hat verticals, 30-70% of campaigns may be rejected in initial review.

Performance Monitoring: Tools track spend, CPM, CPC, and conversion metrics across all accounts. High-performing accounts get increased budgets; underperformers get killed.

Account Health: Monitoring for warnings, restrictions, and bans across all accounts. Early detection of issues allows budget reallocation before an account is fully disabled.

Automated Responses: Some tools can automatically:

• Pause campaigns that exceed CPA thresholds
• Increase budgets on accounts that pass review
• Kill and replace accounts that get restricted
• Resubmit rejected ads with modified creatives

Tool-by-Tool Breakdown

Dolphin Cloud

Dolphin Cloud is the most comprehensive autolaunch platform in the grey-hat ecosystem.

Autolaunch Capabilities:

• Template-based campaign creation via tokens
• Multi-account simultaneous launch
• Creative library with media management
• Campaign duplication across accounts
• Integrated with Dolphin Anty (their anti-detect browser)
• API for custom automation scripts
• Team dashboards for monitoring launches

Unique Features:

• "Smart Launch" mode that stagger launches across accounts to reduce detection
• Built-in A/B testing across accounts (different creatives per account)
• Automatic account rotation when one gets flagged
• Integration with Keitaro tracker for postback attribution

Pricing: From $89/month. The autolaunch module is available on all paid plans but with account limits on lower tiers.

FBTool

FBTool is the speed-focused alternative. Russian-developed, with a strong presence on fb-killa.pro.

Autolaunch Capabilities:

• Token-based campaign creation
• Fastest launch speed in the market (reports of 100 accounts in under 10 minutes)
• Bulk editing (change budgets, bids, status across all accounts)
• Campaign cloning across accounts
• Direct proxy integration (assign proxy per account)

Unique Features:

• "Warm-up launch" mode that creates campaigns with low budgets first, then increases
• Account scoring system (rates account quality based on history)
• Built-in BIN checker for payment method validation

Pricing: From $59/month. Simple tier structure based on account count.

Nooklz

Nooklz differentiates through its data-driven approach to autolaunch.

Autolaunch Capabilities:

• CSV/Excel import for campaign configurations
• Spreadsheet-based campaign management
• Bulk operations through data files
• Template inheritance (parent templates that child campaigns modify)

Unique Features:

• Excel-native workflow (media buyers who work in spreadsheets can map directly)
• Column-to-parameter mapping that handles any campaign structure
• Version control for campaign templates
• Export functionality for campaign performance data back to spreadsheets

Pricing: From $49/month. Popular with media buyers who manage complex campaign matrices.

Saint.tools

Saint.tools is a newer CIS entrant with a unique angle on autolaunch.

Autolaunch Capabilities:

• Token and RPA hybrid launching
• Campaign templates with conditional logic (if geo = US, use budget X; if geo = EU, use budget Y)
• Multi-platform support (Facebook + TikTok autolaunch)

Unique Features:

• "Farming + Launch" integrated workflow (warm account → attach payment → launch)
• Built-in creative editor for quick variant generation
• Telegram bot integration for launch notifications
• Community templates shared by users

Pricing: From $39/month. Aggressive pricing to capture market share.

The One-Click Duplication Workflow

One of the most used autolaunch features is one-click duplication — taking a working campaign from one account and replicating it across many others.

The workflow:

1. Identify a campaign that passed review and is performing well
2. Select target accounts for duplication
3. Choose what to duplicate (exact copy, or with modifications)
4. Specify modifications per account (different creative, different geo, different budget)
5. Execute duplication
6. Monitor review status on duplicated campaigns

This is the "scale what works" workflow. Find a winning combination on one account, then replicate it across your entire account farm. The best affiliates can go from first test to full-scale deployment across 50+ accounts within hours of finding a winner.

Why Speed Matters: The Affiliate Marketing Time Window

To understand why autolaunch exists, you need to understand the affiliate marketing timeline:

Hour 0-4: A new offer appears on an affiliate network. Early testers begin running traffic.

Hour 4-12: Initial data comes in. Testers identify winning geos, creatives, and landing pages.

Hour 12-24: Successful affiliates begin scaling. This is where autolaunch becomes critical — the faster you scale, the more you capture before competition arrives.

Day 2-5: Competition increases. CPMs rise as more affiliates target the same audiences. Creative fatigue begins on early-mover assets.

Day 5-14: Market saturation. Only affiliates with superior creatives, better funnels, or lower costs survive. Many campaigns become unprofitable.

Day 14+: The offer is either mature (stable but lower margins) or dead (oversaturated, network caps reached).

In this timeline, the difference between launching on 50 accounts in 10 minutes (autolaunch) versus 50 accounts in 2 days (manual) is the difference between profit and loss. The first mover captures Day 1-5 traffic at low CPMs. The late mover enters a saturated market.

This time pressure is the fundamental economic driver behind autolaunch tools.

The Official API Alternative

The Meta Marketing API supports bulk campaign creation through official channels. Here is how it compares:

What the Official API Can Do

• Batch API calls: Create multiple campaigns, ad sets, and ads in a single API request (up to 50 objects per batch)
• Campaign templates: Define reusable structures and apply them programmatically
• Bulk editing: Modify budgets, bids, status, and targeting across campaigns via API
• Automated rules: Conditional logic that triggers actions based on performance metrics
• Cross-account management: Manage multiple ad accounts within a Business Manager through a single API integration

Tools like AdRow expose these capabilities through an intuitive interface:

• Campaign template system for reusable configurations
• Bulk duplication across ad accounts within your Business Manager
• Automated rules that scale budgets, pause underperformers, and alert you via Telegram
• AI-powered creative generation to accelerate variant production

Where the Official API Differs

The key differences are structural, not functional:

1. Authentication: Official API requires OAuth per Business Manager. You cannot launch across Business Managers you do not own and have not authorized
2. Rate limits: The API enforces rate limits (typically 200 calls per hour per ad account). Grey-hat tools have no such limits
3. Compliance: All campaigns must pass review. The official API does not support cloaking or policy evasion
4. Account model: Official tools assume persistent, valuable ad accounts. Not disposable, replaceable accounts

For advertisers running compliant campaigns, these differences are non-issues. The official API provides the same speed and scale for legitimate operations. For advertisers who depend on account rotation and policy evasion, the official API is structurally incompatible with their workflow.

The Migration Path

Some media buyers start with grey-hat tools and migrate to official platforms as their business matures. The typical migration path:

1. Grey-hat start: New affiliate marketer, testing verticals, limited budget, high risk tolerance
2. Partial migration: Keep grey-hat for testing, use official tools for proven, compliant campaigns
3. Full migration: Business grows, team expands, compliance becomes important, official API provides all needed functionality
4. Official-only: Established operation, brand reputation matters, risk tolerance decreases, grey-hat tools become liability

This migration is one-directional. Established advertisers rarely move from official tools to grey-hat — the risk calculus does not support it at scale.

Understanding autolaunch is understanding the operational heart of grey-hat media buying. Whether you use these tools, compete against them, or need to evaluate alternatives, knowing how they work gives you the context to make informed decisions about your own toolstack.

For the broader ecosystem context, see The Facebook Ads Automation Ecosystem Explained. For the technical mechanisms behind token and cookie access, see How Grey-Hat Facebook Tools Actually Work.