WEBVTT

00:00:00.328 --> 00:00:03.580
Your popup is published, but nothing appears.

00:00:03.700 --> 00:00:07.860
Let’s find the reason in WConvert, fix one mistaken rule, and

00:00:07.860 --> 00:00:10.380
prove the popup works on the real page.

00:00:10.600 --> 00:00:14.120
Start on the exact page where you expect the popup.

00:00:14.120 --> 00:00:18.120
Our invitation should appear after five seconds, but this computer

00:00:18.120 --> 00:00:19.440
gets nothing.

00:00:19.560 --> 00:00:22.680
Waiting longer will not solve the audience rule we are about

00:00:22.680 --> 00:00:23.520
to find.

00:00:23.733 --> 00:00:27.093
Find the right campaign and confirm it is published.

00:00:27.173 --> 00:00:29.453
A saved draft is not live.

00:00:29.813 --> 00:00:32.053
Open the campaign to check its rules.

00:00:32.133 --> 00:00:34.773
We will use the preview to describe the visit that is

00:00:34.773 --> 00:00:35.533
failing.

00:00:35.733 --> 00:00:38.493
Open Preview, then Who sees it.

00:00:38.853 --> 00:00:43.013
The selected article, a computer, and a first-time visitor match

00:00:43.013 --> 00:00:43.933
our test.

00:00:44.053 --> 00:00:47.933
Read the explanation: this campaign is for phones only.

00:00:47.973 --> 00:00:50.013
The audience rule is stopping it.

00:00:50.233 --> 00:00:52.513
Choose Fix in Display rules.

00:00:52.633 --> 00:00:56.793
Our newsletter is intended for readers on every device, so change

00:00:56.793 --> 00:00:58.673
Phones only to Everyone.

00:00:58.953 --> 00:01:02.353
Keep an intentional restriction if your campaign really is for

00:01:02.353 --> 00:01:03.713
a smaller audience.

00:01:03.933 --> 00:01:06.693
Return to Preview and Who sees it.

00:01:07.053 --> 00:01:10.413
The same computer visit now passes, and the popup is set

00:01:10.413 --> 00:01:12.693
to open after five seconds.

00:01:12.693 --> 00:01:14.213
This checks the draft.

00:01:14.213 --> 00:01:17.733
The live page still uses the published version until we update

00:01:17.733 --> 00:01:18.133
it.

00:01:18.333 --> 00:01:20.213
There is another common reason.

00:01:20.573 --> 00:01:24.613
Set Before this visit to Saw it earlier this visit.

00:01:24.893 --> 00:01:28.173
Our once-per-visit limit now stops the popup.

00:01:28.253 --> 00:01:29.573
That is expected.

00:01:29.693 --> 00:01:32.973
Reset the visitor for a clean test instead of removing a

00:01:32.973 --> 00:01:34.133
useful limit.

00:01:34.333 --> 00:01:38.453
Close Preview, save, then review and publish the update.

00:01:38.867 --> 00:01:42.907
Confirm everyone can qualify on our selected page, with the five-second

00:01:43.027 --> 00:01:44.907
delay and once-per-visit limit.

00:01:45.187 --> 00:01:48.987
Publishing makes the corrected rule available to real visitors.

00:01:49.200 --> 00:01:52.040
Open the article in a fresh visitor session.

00:01:52.160 --> 00:01:53.960
Wait for the five-second delay.

00:01:54.400 --> 00:01:57.800
Now the popup appears on the computer, just as intended.

00:01:58.080 --> 00:02:01.920
A fresh session keeps earlier views or submissions from confusing

00:02:01.920 --> 00:02:02.760
the result.

00:02:03.127 --> 00:02:06.727
Check the published version, describe the visitor, and read what

00:02:06.727 --> 00:02:08.167
stops the popup.

00:02:08.167 --> 00:02:11.180
Fix the cause, publish, and test again.

00:02:11.180 --> 00:02:14.687
If it still stays hidden, use the written guide for live-page

00:02:14.727 --> 00:02:15.887
checks and caching.