Testing & Preview
Test your scheduled content across devices, schedules, and interactions using the Visual Editor's built-in preview tools.
These tools preview scheduled content inside the VEE. To verify scheduled content on your actual website, set up the Next.js Integration and check the production page.
Device Preview
Use the ribbon controls to toggle Preview and switch between Desktop, Tablet, and Mobile views.
What to Check
- Desktop: Full-width layouts, hover interactions, image quality, text readability
- Tablet: Breakpoint behavior, touch-friendly elements, portrait/landscape
- Mobile: Touch targets and swipe gestures, content fit, loading performance
Verify consistent branding and content hierarchy across sizes, and test with simulated slow connections for mobile.
Scheduled Content Templates
When using Scheduled Content Templates, variables update in real time across all device views. Test how design changes affect each breakpoint (Desktop 1024px+, Tablet 768–1023px, Mobile below 768px).
Date and Time Simulation
Use the Date and Time Picker in the toolbar to preview scheduled content at any time—past, present, or future.
What to Test
- Campaign start/end times — when scheduled content goes live and deactivates
- Schedule transitions — switching between scheduled content items
- Overlapping schedules — conflicts in the same slot
- Edge cases — midnight, timezone changes, daylight saving, month/year boundaries
Links, Interactions & Performance
- Links & buttons: Confirm URLs, forms, and tracking work in preview
- Hover, animations, touch gestures: Validate in each device view
- Accessibility: Test keyboard navigation and alt text
- Loading: Check load times, progressive loading for large images, and caching
Quick Checklist
| Area | Checks |
|---|---|
| Visual | Content accuracy, image quality, text readability, brand colors |
| Functional | Links, buttons, interactive elements, animations |
| Devices | Display and behavior across Desktop, Tablet, Mobile |
| Schedule | Start/end times, transitions, no overlaps |
Advanced Testing
- A/B testing: Create multiple versions, use scheduling to compare, monitor metrics
- Cross-browser: Test in Chrome, Firefox, Safari, Edge; check fallbacks for unsupported features
- Load testing: Verify performance under high traffic and during peak usage
Common Issues
| Problem | Things to Check |
|---|---|
| Scheduled content not showing | Scheduling, slot IDs, device targeting |
| Wrong size/position | Slot configuration, responsive settings |
| Links not working | URLs, link configuration |
| Slow loading | Image optimization, server performance |
| Wrong timing | Timezone, date configuration |
| Not activating | Schedule dates, publication status |
Best Practices
- Test early and often with real content and actual devices when possible
- Document results and maintain checklists for consistent QA
- Involve stakeholders for approval before publishing
- Monitor performance and gather feedback after launch
Next Steps
- Review Best Practices for ongoing optimization
- Learn about Troubleshooting for issue resolution