Who is this guide for?
If your organization has multiple teams creating Wisepops campaigns, whether across countries, brands, or departments, you likely need a way to ensure that campaigns are reviewed and approved before going live. This guide walks you through how to set up a governance workflow using the features available in Wisepops today.
This is especially relevant if you have a central/global marketing team that needs to maintain brand consistency and strategic coherence, while local or regional teams handle day-to-day campaign creation.
The Challenge
In large organizations, multiple people create campaigns. Without guardrails, you risk publishing campaigns that haven't been reviewed for brand compliance, legal requirements, or strategic alignment. You need a process that answers:
- Who can create campaigns?
- Who can publish them to production?
- How does a campaign move from "draft" to "live"?
Recommended Wisepops Setup: The Staging/Production Model
The most robust approach uses two separate Wisepops websites to separate campaign creation from campaign publishing.
Step 1 - Create Two Websites in Wisepops
Staging (e.g. `staging.yoursite.com` or a hidden section of your production site) -where Campaigns are created and reviewed. Local/regional editors + Global admins have access.
Production (e.g. `www.yoursite.com`) - is where campaigns are published. Only Global admins have access
If you have multiple locales and one website per locale - you can either create one staging website per locale or have a single staging website for all locale, and use folders to differentiate between locales. We recommend the latter option.
The key principle: editors create on staging, admins publish to production. Local teams never have direct access to the production website in Wisepops, which means they cannot accidentally (or prematurely) push a campaign live.
Step 2 - Use Folders to Signal Approval Status
Within the staging website, create a folder structure that makes the approval status of every campaign immediately visible:
📁 Drafts / Work in Progress
📁 Ready for Review
📁 Approved — Ready to Publish
📁 Published (archived from staging)
When a local editor finishes a campaign, they move it from "Drafts" into the "Ready for Review" folder. This signals to the global team that the campaign needs attention.
Step 4 - Admins Duplicate to Production
When a global admin reviews and approves a campaign in the staging website, they duplicate it to the production website using the Wisepops campaign copy feature. Then they can publish the campaign. This is the moment the campaign goes live.
Only admins have access to the production website, so this step acts as the final gate.
The Approval Process — Step by Step
Here is the full workflow in practice:
1. LOCAL EDITOR creates a campaign on the Staging website
↓
2. Editor moves the campaign to the "Ready for Review" folder
↓
3. GLOBAL ADMIN checks the "Ready for Review" folder
↓
4. Admin reviews the campaign on the Staging website
↓
5. Admin approves → Admin DUPLICATES the campaign to the Production website
↓
7. Admin published the campaign -> Campaign is live.
Tips for International Teams
Wisepops has several features that make it well-suited for multi-country operations:
- Language-based audience targeting: Show campaigns only to visitors whose browser language matches a specific locale (e.g. show the French version only to French-speaking visitors).
- Geolocation targeting: Target campaigns to visitors in specific countries or regions.
- URL-based targeting: If your international sites use different URL paths (e.g. `/en/`, `/de/`, `/fr/`), you can target campaigns to specific paths.
- Campaign duplication: Easily duplicate a campaign and adapt it for another market. Change the language, the targeting rules, or the offer while keeping the design.
These features allow local teams to build hyper-relevant campaigns for their market while staying within the governance framework.
Need help setting this up? Contact your Wisepops account manager or reach out to support@wisepops.com.