WConvertMy changes are not visible or the campaign conflicts with my site
Separate unpublished draft changes, display history, cached pages and layout conflicts with a controlled test.
On this page
Before you start
These checks apply to Free and Pro. Note the page, campaign name, device size and the exact difference between the editor and the live result. If you manage several sites, verify which site’s editor you have open.
Make one change at a time. Use a test page or staging copy for theme, plugin or optimization experiments.
First check draft versus published content
- Open the intended campaign and check the changed wording in its draft.
- If you only selected Save draft, open Review & publish.
- Review any blockers and warnings, then use the offered publish action.
- Wait for publication to finish, reload the actual page and trigger the campaign again.
If an inline location changed, update the page or template containing the block or shortcode as well.
Identify the kind of mismatch
| Setting | What it means |
|---|---|
| Old wording still appears | Confirm publication and that you are looking at the same campaign, then check page/server/CDN caching. Clear the relevant cache using its normal controls. |
| No campaign appears | Check targeting, dates, conversion history and frequency in a fresh private window. Use the display inspector before changing the design. |
| One element ignores a shared color or font | Inspect that element’s Style overrides as well as Look. Check the selected screen and mobile view. |
| A bar or reminder overlaps another control | Review format position, distance and mobile settings. Test alongside the site’s real header, chat and consent controls. |
| The editor works but the live form does not | Record the actual message. Check publication, loaded scripts and any optimization that delays or changes them on a staging copy. |
| Only a custom page layout fails | Compare a plain test page. For inline forms, check the content area or use an explicit block/shortcode location. |
Isolate a repeatable conflict
- Reproduce the problem on a test page and record the steps and viewport size.
- Compare a fresh browser session with the original one to separate history from layout.
- On staging, change one relevant optimization, theme setting or plugin at a time and retest.
- Restore the setting after each comparison unless it is the confirmed, intended fix.
Do not label a theme or plugin incompatible just because it is installed. A useful report identifies the smallest change that reliably makes the symptom appear or disappear.
Confirm the fix and report what remains
Check the live desktop and mobile result, then run one normal form or link action. If contact details are submitted, verify the saved record; if sending is expected, verify the receiving service separately.
For unresolved problems, send support the affected URL, campaign, exact steps, visible error and relevant theme/plugin versions. Include a focused screenshot with private details removed. Say whether the problem happens in Preview, on the published page, or both.
Related guides: preview and publish, inline placement and form rejection.
Include your WConvert version, the page you tested and any error message.