Blog posts by Philipp Gaska

Sending automated order confirmations via Optimizely Campaign

Wed, 29 Sep 2021 11:17:15 GMT

In this blog post, I want to give you a basic example on how to automatically send an order confirmation via Optimizely Campaign. A transactional mail serves as template for the order confirmation which you can create either via the Optimizely Campaign user interface or the REST API.

Processing order data

When a customer registers in your web shop and completes a purchase order, you collect the data (including information such as product item and price) and store it in JSON format: {"item":"Boots","price":"49.99"}.

You transmit this data together with other recipient data into a dedicated field of the transactional mail's recipient list. You can also store the whole HTML content and different language versions in the transaction recipient list to use only one transactional mail as template instead of creating multiple versions.

Creating field functions

To access the individual variables within the JSON object and directly insert them into the mailing text, create a field function that refers to the dedicated recipient list field.

The following sample velocity field function replaces the whole mailing content of the transactional mail and refers to the "order" recipient list field which contains the order data:

#set ($jsonContent = $json.readFromString($!{user.data.order}))
Dear customer,
<br/>
Thank you for your purchase! You successfully completed the order of <b>${jsonContent.item}</b> and already paid the full amount of <b>${jsonContent.price} Euro</b>. You will receive another confirmation email as soon as your order has been shipped.
<br/>
Best regards,
<br/>
Your web shop team
<br/>

Converting prices

If you store prices in cent amounts and want to convert them to decimal amounts (e.g., 4999 cents to 49.99 euros), you can use the following function:

#macro(priceConverter $value)$!{null}#set($int=0)$!{null}#set($netto=$int.parseInt($value))$!{null}#set($netto=$StringHelper.percentage(10000, $netto, 2, $Common.locale("de", "", "")))$!{null}$netto$!{null}#end

Displaying JSON objects as HTML text

If you have a JSON array with multiple items and prices, for example, "order":[{"item":"Boots","price":4999},{"item":"Books","price":1299}], and want to display each of them as HTML text, you can use the following function:

#foreach($data in $jsonContent.order)
<h2>$data.item</h2></br>
Price: #priceConverter($data.price) &Euro;</br></br>
#end

Tip: For more information about field functions, see the Optimizely User Guide.

Sending the order confirmation

To transmit the order data and send the order confirmation, use the POST/{clientId}/transactionalmail/{transactionalMailId}/send operation.

You need the following information:

Client ID. The ID of the client the REST API is set up for. You can find the client ID in Optimizely Campaign under Administration > API Overview > REST API.
Transactional mail ID. The ID of the transactional mail that serves as template for the order confirmation. You can find the transactional mail ID in Optimizely Campaign under Campaigns > Transactional Mails.
Recipient list ID. The ID of the transaction recipient list. You can find the recipient list ID in Optimizely Campaign under Administration > API Overview > Recipient Lists.
Recipient ID. The customer’s email address.
Data. The order data to be displayed in the order confirmation.

The request in curl looks as follows:

curl -X POST "https://api.campaign.episerver.net/rest/123456789/transactionalmail/987654321/send" 
-H "Authorization: BASIC k783r3fjn989dhnfjjdr83dgds1383NDfv=" 
-d "data.order=%7B%22item%22%3A%22Boots%22%2C%22price%22%3A%2249.99%22%7D&recipientListId=238312130812&recipientId=customer%40example.com"

The transactional mail contains only the field function and looks as follows when the order confirmation is sent:

Dear customer,

Thank you for your purchase! You successfully completed the order of Boots and already paid the full amount of 49.99 Euro. You will receive another confirmation email as soon as your order has been shipped.

Best regards,

Your web shop team

Working with the Optimizely Campaign webhooks

Mon, 23 Aug 2021 11:00:50 GMT

Using webhooks, you can get real-time event data on sent mailings, opens, clicks, bounces, and unsubscribes. For example, instead of retrieving the data on a regular basis by using the response data export job, our REST API based webhooks provide you with the data within seconds.

You can immediately process the data and create, for example, in-app notifications or monitoring dashboards in third-party systems such as CRM software. So, you don´t have to open Optimizely Campaign to check which mailings were successfully delivered to the recipient.

Tip: Regularly check our Release Notes for updates. We continuously improve and extend the webhook functionalities and will provide more event types in future.

Early adopter: METRO.digital

METRO.digital, the company behind the digital solutions for the METRO global wholesale business, is one of the first implementers of our webhooks. METRO.digital uses the API client Postman and our Swagger documentation to test the webhooks and build new solutions for processing customer data:

Updating customer master data
Keeping the customer's subscription status up to date by using the bounce and unsubscribe events.
Real-time monitoring and analyses
Analyzing the mailing dispatch (uptime/downtime, queueing/delays) based on the sent event to provide a backup plan in case of delayed transactional mails.
Reporting and scoring
Enriching the data warehouse with internal campaign information and analyzing the customer's channel affinity, scoring and campaign performance for detailed campaign reports.

Creating a webhook for the bounce event

In the following example, I want to show you how to create a webhook for the bounce event using the Optimizely Campaign REST API.

A bounce occurs when a message could not be delivered. There are two types of bounces:

Soft bounce. Possible reason: The mailbox is full, but the recipient may receive mailings again later.
Hard bounce. Possible reason: The email address no longer exists.

Note: To enable the webhook feature, contact customer support. See also: Webhooks in the Optimizely user guide.

To create the webhook, use the POST/{clientId}/webhooks operation. You need the following information:

Client ID. The ID of the client the REST API is set up for. You can find the client ID in Optimizely Campaign under Administration > API Overview > REST API.
Format. Data format in which the event data is to be sent. Currently available: JSON.
Type. Event type "bounce".
Target URL. URL to which the event data is to be sent.

Note: Make sure that the URL is accessible and able to receive data via HTTP POST requests from the IP address 193.169.180.1 at any time. Use the latest HTTPS version and standard port 443 for HTTPS connections.

The request in curl looks as follows:

curl -X POST "https://api.campaign.episerver.net/rest/123456789/webhooks" 
-H "Authorization: BASIC k783r3fjn989dhnfjjdr83dgds1383NDfv="
-d "format=json&type=bounce&targetUrl=https%3A%2F%2Fwww.example.com"

After creating the webhook, you can verify the webhook whether it is ready to use and can send event data to the specified target URL by using the GET/{clientId}/webhooks/{webhookId}/verify operation.

Activating the webhook und retrieving real-time event data

To activate the created webhook, use the POST/{clientId}/webhooks/{webhookId}/activate operation.

Specify the client ID and the webhook ID which you get as response when creating the webhook.

Tip: You can also use the GET/{clientId}/webhooks operation to retrieve the IDs of all created webhooks.

The request in curl looks as follows:

curl -X POST "https://api.campaign.episerver.net/rest/123456789/webhooks/987654321/activate" 
-H "Authorization: BASIC k783r3fjn989dhnfjjdr83dgds1383NDfv="

After activating, the event data is sent to the specified target URL whenever a bounce occurs. The payload consists of the following data, among other:

Bounce category - "softbounce" or "hardbounce"
Bounce reason - "spam-related" or "other"
Media type of the bounced message, e.g., "EMAIL"
Mailing ID
Recipient ID

Sample payload in JSON format:

{ 
    "type":"bounce", 
    "id":"0a673102-178d27b2c8c-178d2cac0e4-c7420699923845e", 
    "recipientId":"john.smith@example.com", 
    "userListId":10180860004, 
    "clientId":10180860001, 
    "created":1617108575391, 
    "subscriptionId":10227900201, 
    "mailId":"4P6W8B4-4P6W0LI-BSLXEC", 
    "mailingId":10230355206, 
    "mediaTypesToAddresses": { 
      "EMAIL":"john.smith@example.com" 
    }, 
    "category":"softbounce", 
    "mediaType":"EMAIL", 
    "reason":"other", 
    "thresholdExceeded":false 
}

Tip: To update the webhook without deactivating it or creating a new one, for example, to change the target URL, you can use the PUT/{clientId}/webhooks/{webhookId} operation.

Right to be forgotten: Deleting recipient data

Thu, 08 Jul 2021 09:18:42 GMT

Data security and protecting the privacy of your customers and newsletter recipients is vital important. With the introduction of the General Data Protection Regulation (GDPR) at the latest, you must provide the possibility of deleting personal data upon request. This is embodied in Article 17 of the GDPR – the so-called "Right to be forgotten".

To irrevocably delete all recipient data from Episerver Campaign (except blocklist entries which is anonymized data), you can use the recipient history in the Episerver Campaign user interface.

A more flexible way is using the Episerver Campaign REST API. This lets you delete recipient data remotely – without logging in to Episerver Campaign. You can, for example, use the Swagger Try it out feature, enter the curl request in the Windows command prompt, or implement a deletion option right into your system, such as a CRM software.

To delete recipient data via REST API, use the DELETE /{clientId}/recipients operation.

You need the following information:

Client ID. The ID of the client the REST API is set up for. You can find the client ID in Episerver Campaign under Administration > API Overview > REST API.
Reason. Reason for data deletion.
Recipient key. Recipient ID, usually the email address.

The request in curl looks as follows:

curl -X DELETE "https://api.campaign.episerver.net/rest/123456789/recipients?reason=customerrequest&recipientKey=recipient%40example.com" -H "Authorization: BASIC k783r3fjn989dhnfjjdr83dgds1383NDfv="

The following example shows the request as PHP code.

Note: The PHP code is a basic example and is not ready to use in your live system. Use it only as a template for testing and adapt the code to your company's internal requirements.

<?php
$user = 'user@example.com'; // API user name, usually your email address 
$password = 'password'; // password of your API user
$clientId = 123456789; // ID of the client the REST API is set up for
$recipientId = 'recipient@example.com'; // ID of the recipient whose data is to be deleted
$reason = 'customerrequest'; // reason for data deletion (without blanks)
$URL = 'https://api.campaign.episerver.net/rest/'.$clientId.'/recipients?recipientKey='.$recipientId.'&reason='.$reason;

$curl = curl_init();
curl_setopt($curl, CURLOPT_URL,$URL);
curl_setopt($curl, CURLOPT_CUSTOMREQUEST, "DELETE");
curl_setopt($curl, CURLOPT_SSL_VERIFYPEER, false);
curl_setopt($curl, CURLOPT_TIMEOUT, 30); //timeout after 30 seconds
curl_setopt($curl, CURLOPT_RETURNTRANSFER,1);
curl_setopt($curl, CURLOPT_HTTPAUTH, CURLAUTH_BASIC);
curl_setopt($curl, CURLOPT_USERPWD, "$user:$password");

$result = curl_exec ($curl);
$result = json_decode($result, true);
     
echo '<pre>';
var_dump ($result);
echo '</pre><br>';

curl_close ($curl);       

?>

Tip: To delete the recipient's blocklist entry, you can use the DELETE/{clientId}/blacklistentries/{entry} operation.

Updating mailing content via REST API

Mon, 21 Jun 2021 09:19:24 GMT

In a previous blog post, I gave an example on how to use the Episerver Campaign REST API to create a Smart Campaign and mailing. To update the created mailing with plain text, you can use the POST/{clientId}/smartcampaigns/{campaignId}/messages/{mailingId} operation.

I recommend using a more convenient operation for updating mailing content. The POST/{clientId}/smartcampaigns/{campaignId}/messages/{mailingId}/content operation lets you update the mailing with plain text, HTML content, or multipart content that consists of HTML and plain text.

Note: You can only update mailings created via REST API.

You need the following information:

Client ID. The ID of the client the REST API is set up for. You can find the client ID in Episerver Campaign under Administration > API overview > REST API.
Campaign ID. ID of the created Smart Campaign. To get the campaign ID, you can use the GET/{clientId}/smartcampaigns operation. You can also find the campaign ID in Episerver Campaign under Campaigns > Smart Campaigns.
Mailing ID. ID of the mailing whose content you want to update. To get the mailing ID, you can use the GET/{clientId}/smartcampaigns operation. You can also find the mailing ID in Episerver Campaign under Campaigns > Smart Campaigns.

Plain text

To transmit plain text, set the content type to "text/plain" in the request header and transmit the content within the request body. The request in curl looks as follows:

curl -X POST "https://api.campaign.episerver.net/rest/123456789/smartcampaigns/987654321/messages/123454321/content" -H "Authorization: BASIC k783r3fjn989dhnfjjdr83dgds1383NDfv=" -H "Content-Type: text/plain" -d "This is plain text."

HTML content

To transmit HTML content, set the content type to "text/html" in the request header and transmit the content within the request body. The request in curl looks as follows:

curl -X POST "https://api.campaign.episerver.net/rest/123456789/smartcampaigns/987654321/messages/123454321/content" -H "Authorization: BASIC k783r3fjn989dhnfjjdr83dgds1383NDfv=" -H "Content-Type: text/html" -d "This is <b>HTML</b> content."

Multipart content

Multipart content consists of plain text and HTML text. This is useful if, for example, a web browser is unable to display the HTML content correctly. Instead of displaying the text along with HTML tags, the plain text is displayed.

To transmit multipart content, transmit the different content parts within the request body as form data without specifying the content type in the request header. The request in curl looks as follows:

curl -X POST "https://api.campaign.episerver.net/rest/123456789/smartcampaigns/987654321/messages/123454321/content" -H "Authorization: BASIC k783r3fjn989dhnfjjdr83dgds1383NDfv=" -F "content1=This is plain text.;type=text/plain" -F "content2=This is <b>HTML</b> content.;type=text/html"

By default, the ISO-8859-1 charset is used. This charset represents only a limited number of languages. You can also specify a different charset within the request, for example, UTF-8:

curl -X POST "https://api.campaign.episerver.net/rest/123456789/smartcampaigns/987654321/messages/123454321/content" -H "Authorization: BASIC k783r3fjn989dhnfjjdr83dgds1383NDfv=" -H "charset=utf-8" -F "content1=This is plain text.;type=text/plain" -F "content2=This is <b>HTML</b> content.;type=text/html;charset=utf-8"

Working with newsletter unsubscribes

Tue, 23 Feb 2021 14:11:37 GMT

In the blog post Setting up a newsletter subscription via REST API, I described how to use a double opt-in process to acquire new recipients in a legally secure way. Even if you do not want to lose the recipients you have acquired, it is essential to include an unsubscribe option in the newsletter and on your website. This is a basic requirement for serious email marketing because you should send your information only to those who are interested in it.

Including an unsubscribe link in your newsletter

In Episerver Campaign, you can easily implement the newsletter unsubscription via an unsubscribe link. Add the {Unsubscribe Link} field function in the newsletter footer after the greeting and contact information.

When the recipients click on the link, they are added to Episerver Campaign's system-internal unsubscribe list. The recipients are not removed from the recipient list but are matched against the unsubscribe list in the future and skipped when the newsletter is sent.

Also, the unsubscribe link redirects to a default confirmation page. If you want to use your own confirmation page, you can change it in Episerver Campaign.

Setting up an unsubscribe form on your website

In addition to the unsubscribe link in the newsletter, you should also provide an unsubscribe form on your website. Like the newsletter subscription, you can do this by using the Episerver Campaign REST API. Create a form and set up the API request using the POST/{clientId}/unsubscribes operation.

Note: Set up the REST API in your client first, see Client setup.

One advantage of an unsubscribe form is that you can ask for the unsubscribe reason and offer an opt-down. Since you do not want to lose your newsletter recipients completely, you can offer to receive an alternative newsletter with a lower sending frequency - for example, monthly instead of weekly. This way you create an unsubscribe form including a new subscription option and keep your unsubscribe rates low.

For further information and tips on how to create subscription and unsubscribe forms, see the Episerver User Guide.

Managing unsubscribes

Monitor your newsletter unsubscribes and make sure that the unsubscribe process is working properly.

Are all newsletter unsubscribes processed by the unsubscribe link in your database as scheduled?
Do you also fulfill individual unsubscribe requests that reach you through reply emails?

Therefore, regularly check the correct handling of your unsubscribe processes to avoid legal or provider-related problems. To monitor and manage unsubscribes, you can use the Episerver Campaign REST API.

In order to view the system-internal unsubscribe list, use the GET/{clientId}/unsubscribes operation. The request in curl looks as follows:

curl -X GET "https://api.campaign.episerver.net/rest/123456789/unsubscribes?sort=created" -H "Authorization: BASIC k783r3fjn989dhnfjjdr83dgds1383NDfv="

The Unsubscribes REST API resource provides even more operations for managing unsubscribes:

Creating a Smart Campaign and mailing via REST API

Fri, 15 Jan 2021 15:13:14 GMT

Instead of using the front end, you can use the features and functionalities in Episerver Campaign remotely via REST API. For example, you can create a Smart Campaign including its mailings. In this blog post, I like to show you a basic example on how to do so.

To create and send a mailing campaign in Smart Campaigns (Episerver Campaign's marketing tool for sending out one-shot-campaigns), perform the following steps:

Create a Smart Campaign
Create a mailing and connect the nodes
Start the campaign

Creating a Smart Campaign

To create a Smart Campaign, use the POST/{clientId}/smartcampaigns operation. You need the following information:

Client ID. The ID of the client the REST API is set up for. You can find the client ID in Episerver Campaign under Administration > API overview > REST API.
Recipient list ID. The ID of the recipient list you want to use for your campaign. Use the GET/{clientId}/recipientlists operation to retrieve all recipient list IDs of your client. You can also find the recipient list IDs in the Episerver Campaign start menu under Administration > API overview > Recipient lists.
Tip: Use a test recipient list to send a test mailing before the actual dispatch. You can also use the POST/{clientId}/smartcampaigns/{campaignId}/messages/{mailingId}/test operation after you have created the mailing and connected the nodes.
Name. Specify a name for the campaign, such as Test campaign.

The request in curl looks as follows:

curl -X POST "https://api.campaign.episerver.net/rest/123456789/smartcampaigns" -H "Authorization: BASIC k783r3fjn989dhnfjjdr83dgds1383NDfv=" -d "recipientListIds=9876543210" -d "name=Test%20campaign"

In the response body of the request, you can find information about the created campaign, such as campaign ID, name, status, and creation date.

Creating a mailing and connecting the nodes

The created campaign is incomplete and requires further editing. Use the POST/{clientId}/smartcampaigns/{campaignId}/messages operation to create a new message node with the actual mailing and connect it with the recipients node that contains the recipient list.

You need the following information:

Client ID
Campaign ID. ID of the created Smart Campaign. To get the campaign ID, you can use the GET/{clientId}/smartcampaigns operation or go to the Episerver Campaign start menu > Campaigns > Smart Campaigns.
Media type. Media type of the mailing, for example email.
Sender address. Email address of the mailing sender.
Predecessor node ID. The ID of the recipients node. To retrieve the node ID, you can use the GET/{clientId}/smartcampaigns/{campaignId} operation.

You also need to specify further parameters, such as mailing name, mailing subject, media type, and set the "resetReplyToAddress" parameter to "true". When creating the mailing, you can only add plain text as mailing content. I will show you how to update the mailing with HTML or multipart content in a later blog post.

The request in curl looks as follows:

curl -X POST "https://api.campaign.episerver.net/rest/123456789/smartcampaigns/12345654321/messages" -H "Authorization: BASIC k783r3fjn989dhnfjjdr83dgds1383NDfv=" -d "senderName=John%20Smith" -d "predecessorNodeId=2" -d "name=Test%20mail" -d "subject=Test%20newsletter" -d "replyToName=John%20Smith" -d "content=This%20is%20the%20mailing%20content." -d "resetReplyToAddress=true" -d "mediaType=email" -d "senderAddress=user%40example.com"

You cannot divide the mailing content into individual content paragraphs via REST API. To do so, create the mailing in the Episerver Campaign front end by using the Template Kit. This also lets you personalize each content paragraph via target groups.

Starting the campaign

To send out the mailing, activate and start the campaign. Use the following operations:

Activating: POST/{clientId}/smartcampaigns/{campaignId}/activate

The request in curl looks as follows:

curl -X POST "https://api.campaign.episerver.net/rest/123456789/smartcampaigns/12345654321/activate" -H "Authorization: BASIC k783r3fjn989dhnfjjdr83dgds1383NDfv="

Starting: POST/{clientId}/smartcampaigns/{campaignId}/start

The request in curl looks as follows:

curl -X POST "https://api.campaign.episerver.net/rest/123456789/smartcampaigns/12345654321/start" -H "Authorization: BASIC k783r3fjn989dhnfjjdr83dgds1383NDfv="

Tip: After sending out the campaign, you can retrieve a report with information about opens, clicks, unsubscribes and bounces by using the GET/{clientId}/smartcampaigns/{campaignId}/report operation.

Setting up a newsletter subscription via REST API

Tue, 15 Dec 2020 13:46:45 GMT

To expand your database of email recipients and attract new potential customers, newsletter subscriptions are essential. I recommend the double opt-in method, which ensures that the recipient really wants to receive promotional emails.

This procedure works like this: When website visitors fill out the subscription form on your website and submit their contact information, they receive an email and are prompted to confirm the subscription by clicking the double opt-in link.

To set up the subscription using the Episerver Campaign REST API, perform the following steps:

Create an opt-in recipient list
Create an opt-in process
Set up the subscription form
Set up the REST API request

Creating an opt-in recipient list

To create an opt-in recipient list, you can use the recipient list management feature in Episerver Campaign. If you do not have enabled this feature in your client, you can also request an opt-in recipient list from customer support.

For an opt-in recipient list, at least the recipient list field "Email" must be assigned. This field is used for the recipient ID. Also, set the list type to "Opt-in".

Creating an opt-in process

To create an opt-in process, you can use the opt-in process self-service in Episerver Campaign. When creating, you specify the opt-in recipient list you created earlier, and add the double opt-in link to the opt-in email.

Setting up the subscription form

Set up a form on your website for collecting the website visitor’s contact data. Create at least an input field for the email address. The more recipient data you collect, the more precisely you can individualize and personalize newsletters. For example, you can add additional fields for the first name, last name, and salutation.

Each input field in the form must have a corresponding recipient list field into which the data is imported. For more information and tips on creating subscription forms, see the Episerver User Guide.

The following example shows a basic HTML subscription form:

<html lang="en">
<head>
  <title>Newsletter subscription</title>
</head>
  <body>
    <h1 style="font-family: Arial, sans-serif">Newsletter subscription</h1>
    <p style="font-family: Arial, sans-serif">To stay up to date on special offers and promotions, subscribe now!</p>
    <form action="" method="post">
     <input style="font-family: Arial, sans-serif" type="text" name="email" placeholder="Enter your email address" size="30"/>
     <input style="font-family: Arial, sans-serif" type="submit" name="subscribe" value="Subscribe"/>
    </form>
  </body>
</html>

Setting up the REST API request

To use the REST API, set up your client first. Use the POST/{clientId}/recipients/{recipientListId} operation to add a new recipient to the opt-in recipient list. You can use the "Try it out" feature of our resource documentation to create and test the request.

You need the following information for the request:

Client ID. ID of the client the REST API is set up for.
Recipient ID. Email address that the website visitor enters into the form.
Recipient list ID. ID of the opt-in recipient list that is used for the double opt-in process.
Opt-in process ID. ID of the double opt-in process.

Tip: You can find the IDs in Episerver Campaign under Administration > API overview. To retrieve the recipient list ID and the opt-in process ID, you can also use the GET/{clientId}/recipientlists and GET/{clientId}/optinprocesses operation.

If you have additional fields, such as last name or salutation, add the corresponding parameters to the request. The following curl request only uses the email address, and the Base64-encoded User:Password as authentication:

curl -X POST "https://api.campaign.episerver.net/rest/123456789/recipients/987654321" -H "Authorization: BASIC k783r3fjn989dhnfjjdr83dgds1383NDfv=" -d "optinProcessId=12345654321" -d "recipientId={emailaddress}"

Connect the API request with the subscription form, for example in a PHP file. Instead of using the Base64-encoded User:Password, add your API user and password directly into the PHP file.

The following PHP example only shows a basic implementation. Also, make sure your form is secured from misuse by using a CAPTCHA, IP blocking or similar measures according to your usage scenario.

<?php
if(isset($_REQUEST['subscribe'])){
$user = 'user@example.com'; // API user name, usually your email address
$password = 'password1234'; // password of your API user
$clientId = 123456789; // ID of the client the REST API is set up for
$recipientlistId = 987654321;  // ID of the opt-in recipient list that is used for the double opt-in process
$optinProcessId = 12345654321; // ID of the double opt-in process
$URL='https://api.broadmail.de/rest/'.$clientId.'/recipients/'.$recipientlistId;

$curl = curl_init();
curl_setopt($curl, CURLOPT_URL,$URL);
curl_setopt($curl, CURLOPT_SSL_VERIFYPEER, false);
curl_setopt($curl, CURLOPT_TIMEOUT, 30); //time out after 30 seconds
curl_setopt($curl, CURLOPT_RETURNTRANSFER,1);
curl_setopt($curl, CURLOPT_HTTPAUTH, CURLAUTH_BASIC);
curl_setopt($curl, CURLOPT_USERPWD, "$user:$password");
curl_setopt($curl, CURLOPT_POST, true);
curl_setopt($curl, CURLOPT_POSTFIELDS,"optinProcessId=”.$optinProcessId.”&recipientId=".$_REQUEST['email']."");
$result = curl_exec ($curl);
print_r($result);
}
else
{
?>
    <html lang="en">
<head>
    <title>Newsletter subscription</title>
</head>
<body>
<h1 style="font-family: Arial, sans-serif">Newsletter subscription</h1>
<p style="font-family: Arial, sans-serif">To stay up to date on special offers and promotions, subscribe now!</p>
<form action="" method="post">
    <input style="font-family: Arial, sans-serif" type="text" name="email" placeholder="Enter your email address" size="30"/>
    <input style="font-family: Arial, sans-serif" type="submit" name="subscribe" value="Subscribe"/>
</form>
</body>
</html>
<?php
}
?>

Now, your newsletter subscription is complete. Publish the page with the subscription form on your website. When website visitors enter their email address and click on the "Subscribe" button, the double opt-in process is initiated and the visitors become mailing recipients.