-
Notifications
You must be signed in to change notification settings - Fork 6
/
ch037_scheduling.xhtml
55 lines (55 loc) · 3.74 KB
/
ch037_scheduling.xhtml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
"http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><title/></head><body><h1>Scheduling
</h1>
<p>In the campaign workflow you will find the scheduling tab.
</p>
<p> If you want to send a campaign straight away, and there is no need to stop sending before a specific time, then you can leave these details unchanged and your campaign will simply send.
</p>
<p>If your needs are more complex, read on.
</p>
<p><strong>Important information </strong>
</p>
<p> Scheduling settings interact with your sending method. If you are only able to process your queue from within the browser because you have no cron or command-line access, then the embargo time feature will not work for you. To send a campaign from the browser you must <em>always</em> open your browser to process the queue and keep it open until you have finished, even if you have used an embargo time.
</p>
<h2>Scheduling tab
</h2>
<p>Below is an image of the scheduling tab. We we will work though it from top to bottom:
</p>
<h2><img src="/phplist/_edit/static/main.png" alt=""/></h2>
<h2>Server time 
</h2>
<p>The server time may not be the same as your local time. All of the times in the scheduling page are relative to server time. Changing this time is an advanced feature. 
</p>
<h2>Embargoed until
</h2>
<p>The campaign will not be sent until this time has passed. If you have a campaign which you wish to send at a later date, perhaps when you out of the office or away from your desk, then this is the feature you should use.
</p>
<p>Embargo time is initially set to the nearest hour <em>before</em> you started your new campaign: this effectively switches off the embargo feature by default. To use the feature you must set the time in the future. Simply set the date and time to the time you want to send, relative to your server time which is stated above. Then place the campaign in the queue as normal. If you are using a cron job then the campaign will automatically start sending at the desired time.
</p>
<p><img src="static/change_embargo_time.png" alt=""/> 
</p>
<h2>Stop Sending After
</h2>
<p>This feature is used when the topic of a campaign is time sensitive, for example, a special offer with an expiration date or an event with a specific time. If the campaign would become irrelevant to anyone who received it after a particular time, then this is the feature you should use. 
</p>
<p>The primary use of this feature is when your list size exceeds your sending capacity within the timeframe you need to send your campaign in. For example, if you have a list of 10,000 subscribers and can send 1000 emails in an hour but the campaign becomes irrelevant in 8 hours time, you need to stop sending before everyone on your list has received a copy of the mail.  
</p>
<p> 
</p>
<p><span>Re-Queue</span>
</p>
<p>The re-queue setting is used to send a campaign to subscribers who join a list <em>after</em> the campaign is sent. Remember, a campaign will never be sent to the same subscriber twice.
</p>
<p><img src="/phplist/_edit/static/re-queue.png" alt=""/></p>
<p> 
</p>
<p>
</p>
<p>As an example, you create a monthly newsletter on the first of January, and send it to a list. Over the month you expect another 50 people to sign up, or be added to your list manually, and you would also like them to automatically receive a copy of the campaign. You would set up your campaign to <strong>re-queue every</strong> day and to <strong>re-queue until</strong> 31st of January.
</p>
<h2>Feedback
</h2>
<p>Discuss this chapter <a href="https://discuss.phplist.org/t/scheduling-manual-chapter-feedback-and-discussion/227">here</a>.
</p></body></html>