WhoKnew Views™ | Exporting & Importing Presets

Skip to main content
Table of Contents
Print

💾 Backup, Share, and Restore Your Configurations in Seconds

The Import/Export system allows you to backup all your WhoKnew Views™ configurations to a single JSON file, then restore them later or transfer them to another site. This is a Pro-exclusive feature that gives you complete control over your data.

📦 What is Import/Export?

💡 Think of it like this: Export creates a snapshot of your entire plugin configuration—all your custom presets, styling tweaks, and algorithm settings—packed into one downloadable file. Import lets you restore that exact configuration with just a few clicks.

🎯 Why Export Your Settings?

  • 🔒 License Renewal Safety Net: If your Pro license expires, you won’t lose your meticulously crafted configurations. Simply export before expiration, then re-import after renewal.
  • 🚀 Rapid Multi-Site Deployment: Configured the perfect setup? Export once, import to 10 other stores in minutes.
  • 🧪 Safe Experimentation: Export your current working configuration before testing new presets or settings. If something breaks, import your backup and you’re back to normal instantly.
  • 💼 Client Handoffs: Agencies can create optimized configurations and deliver them to clients as ready-to-import files.
  • 📅 Seasonal Rollbacks: After a holiday sale with aggressive padding, export your post-sale settings, then import your pre-sale baseline to reset everything at once.

🗂️ Where to Find Import/Export

The Import/Export interface lives on the General tab, making it easy to access your backup tools alongside core plugin settings.

📍 Navigation Path

  1. Go to WooCommerce → WhoKnew Views
  2. You’ll land on the General tab by default
  3. Scroll to the bottom of the page
  4. Look for the “Import/Export Settings” section (elegant gradient background, hard to miss)

⚠️ Pro Users Only: If you’re on the free version, you’ll see a message prompting you to upgrade. Import/Export requires WhoKnew Views™ Pro ($79/year).

📤 How to Export Your Settings

Exporting is a one-click process that captures everything you’ve configured in WhoKnew Views™ Pro. The exported file is comprehensive—you always get a full backup, every time.

🔧 What Gets Exported?

When you click “Export Settings,” the plugin creates a JSON file containing:

CategoryWhat’s Included
🎨 Styling SettingsIcons, fonts, colors, backgrounds, borders, animations, positioning, mobile overrides, custom CSS—every visual setting
🎛️ Custom PresetsAll your user-created presets with their complete configurations
⚙️ Algorithm SettingsCurrently active preset, base padding ranges, variation ranges, soft caps, display limits, drift settings, Smart Visibility Mode configurations
🪟 General SettingsView window duration, display text, placeholders, multilingual text, visibility rules, category exclusions
🔔 Email NotificationsMilestone alerts, rapid growth alerts, unified capacity management settings
📊 Advanced FeaturesPeak Traffic Boost windows, Living Baseline settings, Smart Preset Optimization, custom growth thresholds
🛡️ Admin ToolsIP Whitelist, Bot Filter configurations

💡 Key Insight: Export always creates a complete backup. You can’t pick and choose what to export—but you can choose what to import from that file (more on that in a moment).

🎬 Step-by-Step Export Process

  1. Navigate to the General tab: WooCommerce → WhoKnew Views → General
  2. Scroll to the bottom: Find the “Import/Export Settings” section
  3. Click “Export Settings”: The green button in the Export section
  4. Wait for the download: Your browser will automatically download a file named whoknew-views-settings.json
  5. Store it safely: Save this file to a secure location (cloud storage, password manager, version control)

⏱️ How long does it take? Typically 1-2 seconds, even with dozens of custom presets. The file size is usually under 100KB—JSON is extremely efficient.

📝 Understanding the JSON File

The exported file is human-readable JSON, structured like this:

{
  "settings": { /* All general & algorithm settings */ },
  "customPresets": [ /* Array of your custom presets */ ],
  "stylingSettings": { /* Only non-default styling values */ },
  "activePreset": "flash-sale-2024",
  "smartPreset1": { /* Smart Visibility Mode slot 1 */ },
  "smartPreset2": { /* Smart Visibility Mode slot 2 */ },
  "smartPreset3": { /* Smart Visibility Mode slot 3 */ },
  "ipWhitelist": [ /* Admin IP addresses */ ],
  "botFilter": [ /* Bot user agent patterns */ ]
}

🔍 Pro Tip: Advanced users can manually edit this JSON file to batch-update settings across multiple presets before importing. Just be careful with syntax—one misplaced comma will break the entire import.

📥 How to Import Your Settings

Importing is where the magic happens. Unlike export (which always grabs everything), import gives you three strategic options for what to restore from your backup file.

🎯 The Three Import Modes

When you import, you choose one of three radio button options to control what gets restored:

1️⃣ Import All Settings (Nuclear Option)

What it does: Replaces every single setting in WhoKnew Views™ with the values from your backup file. This is a complete restoration—your current configuration is entirely overwritten.

Use this when:

  • ✅ You’re restoring after a license renewal
  • ✅ You’re migrating to a brand-new site and want an exact replica
  • ✅ Something broke and you want to roll back to a known-good state
  • ✅ You’re a developer deploying a standard configuration to multiple client sites

⚠️ Warning: This obliterates your current settings. Export your current config first if you might want to revert!

2️⃣ Import Custom Presets Only (Preset Sync)

What it does: Imports only the custom presets from the file, plus the following algorithm-related settings:

  • Currently active preset (activePreset)
  • Smart Visibility Mode preset configurations (smartPreset1, smartPreset2, smartPreset3)

What it preserves: All your styling tab settings, general settings, display text, email notifications, IP whitelist, and bot filter remain completely untouched.

Use this when:

  • ✅ You’ve built presets on Site A and want to use them on Site B, but keep Site B’s styling
  • ✅ A colleague shares their expert presets and you want to add them to your collection
  • ✅ You’re experimenting with presets and want to restore your old ones without affecting visual styling
  • ✅ You’re rotating seasonal presets in/out without disturbing your core configuration

💡 Key Insight: This mode is additive for presets—if the imported file has a custom preset named “Flash Sale 2024” and you already have one with that name, the imported version will overwrite your existing one.

3️⃣ Import Styling Settings Only (Visual Sync)

What it does: Imports only the styling settings from the file—icons, fonts, colors, backgrounds, borders, animations, positioning, mobile overrides, and custom CSS.

What it preserves: All your presets (built-in and custom), algorithm settings, display text, view window, email notifications, and admin tools remain completely untouched.

Use this when:

  • ✅ You’ve perfected a visual design on a staging site and want to apply it to production without changing number padding logic
  • ✅ You’re a designer delivering a branded counter style to a client who has already configured their presets
  • ✅ You want to A/B test different visual styles without resetting your algorithm tuning
  • ✅ You’re migrating from one theme to another and need to adjust counter positioning/styling but preserve all padding configurations

🎨 Design Tip: This is the safest import mode for creative experimentation. You can try radical visual changes without risking your carefully tuned number padding strategy.

🎬 Step-by-Step Import Process

  1. Navigate to the General tab: WooCommerce → WhoKnew Views → General
  2. Scroll to the Import/Export section: Same location as the Export button
  3. Choose your import strategy: Select one of the three radio buttons (Import All Settings is checked by default)
  4. Click “Choose File”: Browse to your whoknew-views-settings.json backup
  5. Select your JSON file: Only .json files are accepted (browser validates this automatically)
  6. Click “Import Settings”: The green button in the Import section
  7. Wait for confirmation: You’ll see a JavaScript alert: “Import successful! Reloading page…”
  8. Page auto-refreshes: Your imported settings are now active

⏱️ How long does it take? 2-5 seconds for the import to process, then 1-2 seconds for the page to reload. Total downtime: under 10 seconds.

🔍 What Happens During Import?

Behind the scenes, the import system performs several intelligent operations:

  • 🧹 Legacy Cleanup: Old/deprecated settings from previous plugin versions are automatically removed
  • 🔄 Format Migration: If your backup uses an older data structure (e.g., single growth thresholds), it’s converted to the new array format
  • ✅ Validation: The system checks that required fields exist and are properly formatted
  • 🗑️ Selective Preservation: Depending on your chosen import mode, certain settings are intentionally left alone
  • 📝 Timestamp Logging: The import time is saved to wkv_last_import for troubleshooting

🧪 Advanced Import/Export Strategies

🔁 The “Configuration Swap” Workflow

Need to quickly switch between two completely different setups? Use this technique:

  1. Export your current config: Save it as config-A.json
  2. Import your alternative config: Choose “Import All Settings” and load config-B.json
  3. Swap back anytime: Import config-A.json to revert instantly

🎯 Use case: Switch between “Aggressive Black Friday” and “Conservative Post-Holiday” configurations seasonally without manually adjusting 50+ settings each time.

🏢 Multi-Site Deployment with Per-Site Customization

Managing multiple stores? Use this layered approach:

  1. Create your base config: Set up presets and algorithm logic on your primary site
  2. Export it: Save as base-config.json
  3. Import to Site 2, 3, 4, etc.: Use “Import Custom Presets Only”
  4. Customize styling per-site: Each site keeps its own visual branding while sharing the same number padding strategy

💼 Agency Tip: This is perfect for white-label deployments. Your clients get your expert algorithm tuning, but you can customize the counter appearance to match each brand.

📅 Seasonal Preset Libraries

Build a collection of event-specific backups:

  • black-friday-2024.json → Aggressive padding, extended view window, flash sale messaging
  • post-holiday-reset.json → Conservative baseline, shorter window, credibility-focused
  • summer-sale-casual.json → Moderate padding, relaxed drift, seasonal display text
  • launch-week-hype.json → Maximum variation, rapid growth alerts, energetic styling

When each event arrives, import the relevant file with “Import All Settings” for instant, zero-configuration activation.

🔬 Safe Testing Environment

Before making risky changes:

  1. Export current config: This is your safety net
  2. Make experimental changes: Try new presets, adjust soft caps, modify drift settings
  3. If it breaks: Import your backup with “Import All Settings” to instantly undo everything

🛡️ Best Practice: Always export before major changes. Storage is cheap; rebuilding a complex configuration from memory is expensive.

⚠️ Common Import/Export Pitfalls

🚫 Issue: “Error: Invalid JSON file”

Cause: The JSON file is corrupted or manually edited incorrectly (missing comma, extra bracket, etc.).

Fix:

  • If you manually edited the file, validate it with JSONLint.com
  • If you didn’t edit it, the download may have been interrupted—export a fresh copy
  • Make sure you’re uploading a .json file, not a .txt or .zip

🚫 Issue: Import Succeeds, But Settings Don’t Change

Cause: You imported styling settings, but your current values already match the file (no changes detected).

Fix:

  • Check if you selected the correct import mode (All Settings vs. Presets Only vs. Styling Only)
  • Open the JSON file and verify it contains the settings you expect
  • If importing presets, check the Presets tab to confirm they were added

🚫 Issue: “No valid custom presets found in the imported file”

Cause: You selected “Import Custom Presets Only,” but the JSON file’s customPresets array is empty.

Fix:

  • Verify the file was exported from a site with custom presets (built-in presets aren’t exported)
  • If you want to import built-in presets, you need to clone them as custom presets first, then export
  • Switch to “Import All Settings” if you need to restore general/styling settings instead

🚫 Issue: Import Overwrites Product-Specific Settings

Cause: Import/Export does not include product-specific overrides. Those are stored separately in product meta, not global settings.

Workaround:

  • Product-specific settings survive imports—they won’t be overwritten
  • If you need to migrate product settings, you’ll need to manually recreate them or use a WordPress migration plugin that copies post meta

🎓 Best Practices

  • 📆 Export regularly: After every major configuration change, export and save the file with a descriptive name (config-2024-11-26.json)
  • 🗂️ Organize by date: Keep a folder of timestamped exports so you can roll back to any point in history
  • ☁️ Use cloud storage: Store exports in Dropbox/Google Drive/OneDrive so they’re accessible from anywhere
  • 🔐 Include exports in backups: Add your WhoKnew Views exports to your regular site backup routine
  • 📝 Name meaningfully: black-friday-2024.json is better than whoknew-views-settings-copy-3.json
  • ⚡ Test imports on staging: Before importing to production, test the file on a staging site to verify it works
  • 🧹 Clean old exports: Every 6 months, delete outdated exports to keep your backup library manageable

Share