Save Bulk Launch rows as launch templates, share them with teammates, duplicate them, and move them between workspaces via a JSON export/import envelope.

Launch templates — share, export and import

Launch templates save a Bulk Launch campaign row so you can reuse it. Beyond saving and reusing, Wevion lets you share a template with teammates, duplicate a template into your own library, and export / import templates as a portable JSON envelope to move them between workspaces. Shared and exported templates are sanitized — account-bound fields are stripped so nothing account-specific leaks.

Launch templates vs campaign templates

Wevion has two template systems. This article covers launch templates (/api/v1/launch-templates), used from the Bulk Launch grid at /launch, which add sharing and export/import. For the Campaign Creator's campaign templates (/api/v1/campaign-templates), see cc-118.

Who is this for

Mediabuyers and agencies who reuse launch structures across teammates or across workspaces — and want to hand a proven setup to a colleague or migrate it to another workspace without rebuilding it.

Saving a launch template

From the Bulk Launch grid, save a row as a template. Wevion calls POST /api/v1/launch-templates with a name (unique per user) and the campaign row data. Limits:

• Template name must be unique per user (duplicate name → conflict)
• Template data max 500 KB (larger → rejected)

Your template list

GET /api/v1/launch-templates returns both templates you own and templates shared with you, each with a preview: objective, budget, ad-set count, ad count, and the first few countries. Owned templates show how many teammates they're shared with; you can only manage (rename, delete, set shares for) templates you own.

Sharing with teammates

You can share a launch template with specific teammates:

• List recipients (GET /api/v1/launch-templates/:id/shares) — owner only
• Set recipients (PUT /api/v1/launch-templates/:id/shares) — replaces the share list with team members you can access; passing an empty list revokes all shares (up to 500 recipients)

When a non-owner reads or copies a shared template, Wevion sanitizes it — account-bound fields (the specific ad account, pixel, page) are blanked, and the response reports which fields were cleared. This lets a colleague reuse the structure without inheriting your account bindings.

Duplicating

POST /api/v1/launch-templates/:id/duplicate copies a readable template (one you own, or one shared with you) into your own library. Shared templates are sanitized before duplication. Wevion auto-names the copy <name> (copia), then (copia 2), (copia 3), and so on to avoid collisions.

Export / import envelope

To move templates between workspaces, use the portable JSON envelope:

Export

POST /api/v1/launch-templates/export with a list of your template ids (max 250) returns:

{  "format": "wevion.launch-templates",  "version": 1,  "templates": [    { "name": "...", "template_data": { }, "resource_names": { "account": "...", "pixel": "...", "page": "..." } }  ]}

Export strips account-bound fields and adds readable resource names (account / pixel / page) when they can be resolved, so the receiving workspace can re-map them.

Import

POST /api/v1/launch-templates/import accepts an envelope with format: "wevion.launch-templates" and version: 1 (other versions are rejected). Wevion:

• Resolves the supplied resource names against assets you can access, re-binding account / pixel / page where a match exists
• Disambiguates names against your existing templates — a clash becomes <name> (importato), then (importato 2), etc.
• Skips any template whose data exceeds 500 KB

It returns counts: imported, renamed, and skipped.

Deleting

• Delete one — DELETE /api/v1/launch-templates/:id
• Bulk delete — DELETE /api/v1/launch-templates/bulk with up to 250 ids (only your own templates are deleted)

Common issues

• "A template with this name already exists": names are unique per user — pick a different name or rename the existing one.
• Template data too large: the row exceeds 500 KB; simplify it (fewer ad sets/ads) before saving.
• Can't share / rename a template: only the owner can manage a template. Duplicate it into your own library first.
• Shared template missing account/pixel/page: expected — account-bound fields are sanitized for non-owners. Re-select them at launch.
• Import "Unsupported export version": the envelope isn't version: 1. Re-export from a current Wevion workspace.
• Import renamed my templates: a name already existed in your library, so Wevion appended (importato) to avoid overwriting.

FAQ

What's the difference between launch templates and campaign templates?

Launch templates (/api/v1/launch-templates) come from the Bulk Launch grid and add sharing plus a JSON export/import envelope for moving templates between workspaces. Campaign templates (/api/v1/campaign-templates, see cc-118) are the Campaign Creator's reusable structures. They're separate systems, so a launch template and a campaign template are managed independently.

What happens to account-specific data when I share or export a template?

Wevion sanitizes account-bound fields. When a non-owner reads, duplicates, or you export a launch template, the specific ad account, pixel, and page are stripped, and Wevion reports which fields were cleared. Exports also add readable resource names so the receiving workspace can re-map account / pixel / page to its own assets during import.

How do I move a launch template to another workspace?

Export the templates you want with POST /api/v1/launch-templates/export (up to 250 ids) to get a wevion.launch-templates version 1 envelope. In the other workspace, import that envelope with POST /api/v1/launch-templates/import. Wevion re-binds account / pixel / page where a matching asset exists, disambiguates any name clashes, and returns how many were imported, renamed, and skipped.

Can I give a teammate a template without giving them my ad account?

Yes. Sharing a launch template exposes only its structure — account-bound fields are blanked for non-owners. Set recipients with PUT /api/v1/launch-templates/:id/shares (team members only; an empty list revokes all sharing). Your teammate reuses the objective, budget, audiences, and creatives layout, then selects their own account, pixel, and page at launch.

FAQ

What's the difference between launch templates and campaign templates?

Launch templates (/api/v1/launch-templates) come from the Bulk Launch grid and add sharing plus a JSON export/import envelope for moving templates between workspaces. Campaign templates (/api/v1/campaign-templates, see cc-118) are the Campaign Creator's reusable structures. They're separate systems, so a launch template and a campaign template are managed independently.

What happens to account-specific data when I share or export a template?

Wevion sanitizes account-bound fields. When a non-owner reads, duplicates, or you export a launch template, the specific ad account, pixel, and page are stripped, and Wevion reports which fields were cleared. Exports also add readable resource names so the receiving workspace can re-map account / pixel / page to its own assets during import.

How do I move a launch template to another workspace?

Export the templates you want with POST /api/v1/launch-templates/export (up to 250 ids) to get a wevion.launch-templates version 1 envelope. In the other workspace, import that envelope with POST /api/v1/launch-templates/import. Wevion re-binds account / pixel / page where a matching asset exists, disambiguates any name clashes, and returns how many were imported, renamed, and skipped.

Can I give a teammate a template without giving them my ad account?

Yes. Sharing a launch template exposes only its structure — account-bound fields are blanked for non-owners. Set recipients with PUT /api/v1/launch-templates/:id/shares (team members only; an empty list revokes all sharing). Your teammate reuses the objective, budget, audiences, and creatives layout, then selects their own account, pixel, and page at launch.

Last updated: 2026-07-02

Related articles

• Campaign templates — save and reuse
• Bulk Launch overview — grid interface
• Bulk Launch across multiple ad accounts