---
name: replicate
description: Rebuild an existing campaign from one ad platform onto another — read the live structure on the source platform, map it to the target platform, and ship a matching campaign. Use when a user wants to copy, port, clone, duplicate, mirror, or replicate a campaign across platforms (e.g. "build my Google campaign on Microsoft", "run this Meta campaign on TikTok too", "copy my Search campaign to Bing").
---

# Replicate a Campaign Across Platforms

Take a campaign that already runs on one platform and stand up a matching one on another. Read what exists, map it to the target platform's shape, show the plan, and ship on the user's word. This is a build path — every spend-creating step waits for explicit approval.

The common ask is Google → Microsoft (near 1:1), but the same loop works for any pair.

## 1. Read the source campaign — completely

Confirm the org and accounts first: `list_connected_accounts`. Both the source and target platforms must be connected. If the target isn't connected, run the **connect** skill first.

Find the source campaign: `list_campaigns(platform="<source>")`. Get its real ID.

Pull the full structure, not just top-line metrics:

- Read `list_campaigns`, `audit_account_structure`, and `pull_google_ads_performance` for a Google source. Ask for platform exports when budgets, geo criteria, keyword match types, negatives, or complete ad text are missing. Do not replicate unknown settings.
- **Other sources (Meta, LinkedIn, Reddit, Microsoft):** use `list_campaigns` and the matching performance tool (`pull_meta_ads_performance`, `pull_linkedin_ads_performance`, `pull_reddit_ads_performance`, or `pull_microsoft_ads_performance`) for performance; request platform exports for structure, audiences, and creative. TikTok and X sources require a platform export.

Write down the source structure explicitly before you build. If you cannot read a piece, say so — never invent a keyword list or a budget.

## 2. Map source → target

Platforms are not identical. State the mapping and where it is lossy.

**Google → Microsoft (the easy case — nearly a mirror):**
- Campaign, ad group, keyword (with match types), RSA, negative keyword, geo/location, ad schedule, and budget all map directly.
- Keep match types exactly. Keep negatives — they matter as much as the keywords.
- Watch the gaps: Microsoft's audience and network options differ (Search Partners, Microsoft Audience Network), some Google automated-bidding modes have no exact twin, and final-URL/tracking-template syntax can differ. Call these out rather than silently dropping them.
- Rebuild fresh through Synter's plan tools. Do not describe this as Microsoft's native "Import from Google" — that is a different, platform-side path.

**Cross-format pairs (e.g. Search → social, Google → Meta/TikTok):**
- Social campaigns require a new targeting interpretation. Use `research_campaign_opportunity` and existing `list_audiences` results to inform it; document how the proposed targeting differs from the source.

## 3. Build the target plan

`create_campaign_plan` to draft the target structure, then `upsert_plan_entity` to add each campaign → ad group / ad set → ad, carrying over the mapped keywords, negatives, geo, schedule, and budget. `forecast_campaign` for reach/CPC/CPA on the new platform — the source platform's numbers do not transfer.

Creative: reuse the source ad copy where the format allows; otherwise run the **ad-copy-generation** skills to regenerate for the target platform. Apply brand voice — see `../../context/brand-and-safety.md`.

## 4. Preflight — before anything goes live

Run the **campaign-preflight** checklist and report pass/fail:

- Geo/location criteria copied and correct (a "US" name with no location criteria is the classic miss).
- Negatives carried over — porting keywords without negatives burns budget fast.
- Check target-side evidence with `ga4_get_conversions` and `get_pixel_health`. Resolve missing tracking verification before launch.
- Budget and bid caps sane — guard against a fat-finger daily budget 10–100x intended.
- Match types preserved; final URLs resolve and match the ad's promise.

## 5. Ship on approval

Show the mapped plan beside the source, including changed structure, geography, audience, budget, and assets. Follow **launch** for `run_launch_preflight`, explicit user approval, `approve_campaign_plan`, and `execute_campaign_plan`. Verify with `get_plan_execution` and `list_campaigns`; enable only within the approved scope.

Confirm live: `list_campaigns(platform="<target>")` and report the real campaign ID created. "Created" and "live and spending" are different claims — verify before you say it is running.

## House rules

- Nothing that spends money ships without explicit approval. Recommend, then execute.
- Use the real account and campaign IDs the tools return — never invent them.
- Never run one org's campaign through another org's key.
- Microsoft (and most platforms): enabling a campaign does not serve its ad groups if those stay paused. After enabling, re-pull and confirm the children actually serve.
- Start the target conservative on budget; scale winners later with the **optimize** skill.