How do I embed scheduling instructions in a bulk upload file?

Custom Recur Codes In Bulk Upload Files

You can include a code on an update that tells us the update must automatically recur (automatically publish at a specified frequency).

Here are a few samples:

#R5D means publish the update once every 5 days.

#r10i means publish the update once every 10 minutes.

#R3M means publish the update once every three months.

The code must be at the end of the update text.

The code can be uppercase or lower case or a combination.

Character #1: must always be one space (between the last character of the update text and the code itself)
Character #2: #
Character #3: R
Character #4-: a numeric value (must start with 1 to 9, must not be a 0)
Last Character: one of the following:
i (minutes)
h (hours)
d (days)
w (weeks)
m (months)
y (years)

The custom recur code can be combined with custom scheduling codes (see below) and they can appear on updates without custom scheduling codes.

Here is a sample including the update text.

Read all about our limited-time special offer! http://example.com/offer #R4H

The #R4H instructs us to publish the update once every four hours. The #R4H code does not appear in the update text when it is published.

Here is a sample with spinnable (rotating) update text.

{Read {all |}about our {limited-time|awesome|very} special offer!|Click to {find out|learn} more {about|regarding} our {limited-time|awesome|very} special offer!} {http://example.com/offer|http://bit.ly/ourspecialoffer} #R4H

Custom Bulk Upload Scheduling Codes

When you upload a file, you have two options. You can provide us with the text of the updates and tell us on the upload form how you want the updates to be scheduled. Or, you can include custom scheduling codes on each update in the file to specify exactly when each update must be scheduled. Meaning, with custom scheduling codes you embed the schedule in the file itself. (Read on, it's easier than it sounds.)

If you include custom scheduling codes in a file then every update in the file must have a custom code. You cannot include some updates that don't have a code.

Custom scheduling codes apply only to uploads into a social accounts where each individual update is scheduled during the upload. They do not apply to uploads into queue reservoirs where the updates are simply added to the update reservoir. If you upload a file that contains custom codes into a queue reservoir then the codes are simply removed from the update text before it is stored in the queue reservoir. In other words, it's okay to upload a file with custom scheduling codes into a queue reservoir. It's treated as a normal upload file and the scheduling codes are removed before storage of the updates.

These custom codes also have no effect if you include them on an update that you create with the online New Update form. They only apply to bulk uploads.

On multi-line updates the custom scheduling code must be inside the <update></update> tags.

The custom scheduling code is not stored with the update text. It's used during the upload process and then stripped from the text. Hence, they also do not count toward the length of the update text.

Combining Custom Scheduling Codes And Self-Destruct Codes

It is perfectly fine to add both a custom scheduling code and a self-destruct code to an update. Both must be at the end of the actual update text, and the order of the two codes is not important.

Absolute Custom Scheduling Code

An absolute custom scheduling code specifies the exact date and time that the update must be published.

Example: #S"2015/03/15 08:00 AM" means publish the update at 8:00 AM on March 15th, 2015.

The date stamp is in the time zone that's in effect on your SocialOomph account.

The code must be at the end of the update text. The code can be uppercase or lower case or a combination.

Character #1: must always be one space (between the last character of the update text and the code itself)
Character #2: #
Character #3: S
Character #4: "
Character #5-: date in the format YYYY/MM/DD HH:MM AM/PM If you leave out the AM/PM then the HH:MM must be in 24-hour format.
Last character: "

Here is a sample including the update text.

Read all about our limited-time special offer! http://example.com/offer #t5d #s"2014/01/01 9:00 AM"

You will notice the example also includes a self-destruct code. It's not required, it's just an illustration that you can add both to an update.

Relative Custom Scheduling Code

A relative custom scheduling code specifies the time gap (number of minutes, hours, days, weeks, months, or years) between the update and the one preceding it in the bulk upload file.

Here are a few samples:

#S5D means publish the update 5 days after the one preceding it in the file.

#s10i means publish the update 10 minutes after the one preceding it in the file.

#S3M means publish the update 3 months after the one preceding it in the file.

The code must be at the end of the update text.

The code can be uppercase or lower case or a combination.

Character #1: must always be one space (between the last character of the update text and the code itself)
Character #2: #
Character #3: S
Character #4-: a numeric value (must start with 1 to 9, must not be a 0)
Last Character: one of the following:
i (minutes)
h (hours)
d (days)
w (weeks)
m (months)
y (years)

Here are a few more examples.

#s90d - 90 days
#s5w - 5 weeks
#s20d - 20 days
#s2y - 2 years
#s600i - 600 minutes

Here is a sample including the update text.

Read all about our limited-time special offer! http://example.com/offer #s45i

The update will be published 45 minutes after the update that preceded it in the upload file.

Combining Absolute And Relative Custom Scheduling Codes In One File

You can include both absolute and relative codes in the same file. However, a specific update cannot have both, it must have either the one or the other.

When you include an absolute code on an update and the updates following it in the file have relative codes, then that absolute date becomes the reference (departure) point for the remaining updates.

For example, if an update specifies a date of 2014/10/10 9:00 AM and the next update has a relative code of #s2h then that next one will publish at 2014/10/10 11:00 AM.

You can have as many absolute codes in the file as you want. Each one becomes the reference point for subsequent relative codes up to the next absolute code or the end of the file.

Interaction Of Custom Codes And The Options You Choose On The Upload Form

Absolute codes completely ignore the scheduling options you choose on the form. The update is scheduled for the date and time specified in the absolute code.

Relative codes take the form's start date and time as reference point until an absolute code is encountered.

The form's frequency, weekday constraints and hour constraints are completely ignored for both absolute and relative codes. Meaning, if you include custom scheduling codes in the file then the only form scheduling data that is taken into account during the upload process is the form's start date and time, if your very first update in the file does not have an absolute code.

Your choices on the form regarding link shortening, update randomization, and treatment of long updates are respected.

Sample File

Stop spending time with the wrong people. #s"2013/12/01 8:00 AM"
Stop running from your problems. #s1d
Stop lying to yourself. #s3d
Stop putting your own needs on the back burner. #s90i
Stop trying to be someone you're not. #"2013/12/10 13:00"
Stop trying to hold onto the past. #s1w
Stop being scared to make a mistake. #s1d
Stop berating yourself for old mistakes. #s2d
Stop trying to buy happiness. #s8h


Self-Help Index

Can't find the answer to your question? Create a support ticket for personalized support by our staff.