Page tree

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.



%ses-brand offers a newsletter interface. This allows user to un/subscribe from/to newsletters and see the newsletter status or update newsletter details information in his profile.

In standard implementation of %ses-band there is no specific newsletter provider connection. The standard offers only processes, templates, routes, configurations and interface which can be used for newsletter integration. So only a newsletter provider service with specific API implementation of this provider has to be implemented. One plugin for %ses-brand is Newsletter2Go.

Newsletter features in %ses-brand

  • Double-opt-in process (via shop) when user subscribes to newsletter
  • User can subscribe from the newsletter box
  • User can subscribe during the registration process
  • User can un/subscribe from his profile
  • User can update his newsletter details from his profile
  • User newsletter details are updated after ordering in the checkout
  • The newsletter status is fetched from the newsletter provider after the login and user see the status in his profile. The newsletter status is stored in the CustomerProfileData together with the list of ids of newsletter topics, so it can be rendered in the template if required.

    Code Block
    {# true if user subscribed at least one newsletter #}
    {{ ses.profile.sesUser.subscribesNewsletter }}
    {# list of subscribed newsletter ids #}
    {% set dataMap = ses.profile.getDataMap.dataMap %}
    {% set newsletters = dataMap.subscribed_list_ids %}
    {% if newsletters|default is not empty %}
      {% for newsletter in newsletters %}
        {{ newsletter }}
      {% endfor %}
    {% endif %}

Default attributes

Following attributes are offered by default. These attributes ('created on' is an exception this is set by newsletter2go automatically) are send to the newsletter provider if available:

  • First name
  • Last name
  • Gender
  • Telephone Number
  • Date of birth
  • User language
  • Last order date
  • last order amount
  • Order amount total

Additional attributes

There are places where you can add or modify additional user data and send it to newsletter provider.

  1. Before a user subscribes to the newsletter.  In standard the user language (current locale) is sent.
    Any data from the customer profile can be sent, however custom EventListener has to be implemented for that, see FAQ.
  2. After user updates his profile or creates an order. In standard the newsletter details will be updated with latest information about:
    • last_order_date - date when last order was made 
    • last_order_amount - order amount from last order
    • order_amount_total - total amount for the user
    Any data from the customer profile can be sent, however custom EventListener has to be implemented for that, see FAQ.

Attributes, that do not exist in the newsletter provider has to be created first.

Double-opt-in (DOI) process

When user subscribes to newsletter via shop (newsletter box, registration, profile), shop first checks if user already exists in the newsletter provider. It can happen, that user already subscribed in the past.

If the user is not known to the newsletter provider, DOI process is started.

User data is stored in the shop in a token, and the user receives an email, where he has to confirm his email address.

After user clicked on the link in the confirmation email, the token is invalidated and user is subscribed to the newsletter. If he is logged in, he can immediately update the status in his profile.

Important terms used in this document


Include Page
Term - ERP
Term - ERP

Before you start 

Please keep in mind that newsletter is really connected with a lot of different modules with the webshop. Be sure to check these out:

Table of contents:

Table of Contents

Child Pages:

Children Display


Include Page
Newsletter - FAQ
Newsletter - FAQ


See Newsletter - Templates


Include Page
Newsletter - Cookbook
Newsletter - Cookbook


Include Page
Newsletter - API
Newsletter - API