Subscribe and Send One-Off Message


The Subscribe and Send One-Off Message command allows you to subscribe an email address and send a single transactional style message to the subscriber.  These messages are individually created and sent, but can be tracked together as a sticky campaign to collect data as a single campaign.


The Subscribe and Send command requires the following arguments: Command, List, Template, Format, and Data.


The command is ‘subandsend’, the list properties are defined in list with ID ‘5’, the content to send is in template with ID '42', a subscription will be created and the message sent to the email address ''.

The Subscribe and Send command expects at least one field in the Data argument.  The email address of the subscriber is always required to subscribe and send a message.  If the subscriber does not exist, or is not subscribed to the list, a Subscription and Subscriber record will be created.  If the subscriber does exist, the record will be updated with any defined data.

The Subscribe and Send command support the following arguments:








Defines the command to use.




Name of the realm to run the command.  This is optional and only necessary when submitting files to a parent realm in order to manipulate a child realm.




Identifier of the list properties to use. If you are using one file to perform the same command for several lists, group the command lines in your file by Command and List.  This will improve processing efficiency. 

Alternately, define the list in the header instead of per command.  This must refer to a valid list with From and Reply-to.




Identifier of the template content to send.  In the template, both Plain Text and HTML must be defined in order to send MIME.




Subject line of the message to send. This overrides the default Subject defined in the Template.  Character limit is 48.




To specify the format of the email message, set Format to the corresponding value:

1= send Plain Text only

2 = send HTML only

99 = send Multipart MIME


Campaign Name


To track one-off message events, such as opens and click-throughs, the List properties must be set to Sticky Campaigns.  If you then define a campaign name, you can view the results as a single campaign.

A single list can have multiple campaigns by using a different Campaign Name. 




The Email data field is always required.  Additional fields are optional.





Using many commands and arguments (please note the command is wrapped for display purposes only):


A new Subscriber record will be created for the email address ‘’ in the realm ‘myrealm’, a child of the Realm defined in the header.  The Subscriber record will contain the First Name, Last Name, and Age of the subscriber.  Once created, a subscription will also be created for List ‘5’.  A message will then be sent to the subscriber using the List Properties from List ‘5’ and the HTML content in Template ‘42’.

If Sticky Campaigns is enabled for the list, and a campaign does not already exist, a new campaign called 'my campaign' will be created and all tracking data will be reported through it.  If a campaign already exists, all tracking data will be added to the existing campaign.

Customer Key Example

Some systems have the ability to define a unique Customer Key per subscriber.  If your realm has Customer Key enabled, then you must include the customer_key in the data argument along with email.  For example:


If the Customer Key is not included, the command will fail.


A Subscribe and Send command will fail if an Opt out record exists for the specified email address.  It will also fail if an invalid list or template is specified, or if no content is defined for the specified email format.

Additional Considerations

The Subscribe and Send command supports several special arguments.

Subscription vs. No Subscription

The email address for the subscriber is always required, however the email address does not need to correspond to an existing subscriber.  If an email address does not exist as a Subscriber or is not subscribed to the list, the message will be sent.  If the subscriber does not exist, or is not subscribed to the list, a Subscription and Subscriber record will be created.

Tracking as Campaigns

By default the Subscribe and Send command sends a single message and does not track the resulting Subscriber initiated events.  To track one-off messages as a campaign, you must enable the Sticky Campaigns option in your List properties.  Do this through the web interface by logging in and then going to LISTS > VIEW LISTS.  Select the list and then click the Advanced tab.  Scroll to the bottom of the page and select the option under Sticky Campaigns labeled ‘Publish using the same (initial) campaign,’ and then click SAVE to save the settings.

Define the Campaign Name in the header to associate all Subscribe and Send commands in the Data file to the same campaign.  Define the Campaign Name in the specific Subscribe and Send command to override the header definition.

When you submit the Data File for processing, it will check to see if a campaign already exists with the list_id and campaign_name.  If so, tracking for this one-off message will be associated to that campaign.  If not, a new campaign will be created and tracked. 

You can view the Campaign Details by going to REPORTS > VIEW CAMPAIGNS and selecting the List with the defined Campaign Name as the Alias.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request


Powered by Zendesk