Re-subscribing customers using API and requesting product information by Group Id

The year has just begun, and we’re already ready to tell you about the most important updates to the Retail Rocket platform. Read the article if you want to learn about the new features with which you can save your team time and money.

Re-subscription of users via API

We have added the ability to re-subscribe customers to email newsletters. If a customer has previously refused to receive emails, you need to resubscribe them to get them back into the mailing list. Previously it could be done via a pop-up window on the site or with the help of support. We added the ability to resubscribe users through a single API to simplify the process and improve the customer experience. This opened up new possibilities in different situations:

Cross-channel re-subscription on the website or app. Customers can now choose to re-subscribe and the type of content they’re interested in from any device.

Subscription Landings. Online retailers can place social media posts that direct users to a subscription page.

Surveys. Shoppers can now be engaged with a short survey about their preferences or reasons for unsubscribing, at the end of which they can be given the option to re-subscribe to an email newsletter.

Checkout process. During the checkout process, you can give customers the opportunity to re-subscribe to the newsletter. For example, by placing a checkbox with a subscription form next to the email input field.

We have prepared documentation on the API method of re-subscription to make it easier to understand everything.

Only customers who have clearly expressed a desire to receive emails again can be re-subscribed. The API method will not re-subscribe recipients who have marked emails as spam or who have received a “hard bounce” status.

Getting information about products from a group by groupId

Previously, to implement selectors in product blocks, you had to duplicate information about products from the group in each product of the group. For example, for a t-shirt with sizes from S to XL you would need to:

• Tell the integration team that for each product in the group you need an additional parameter with all the id’s of the products in the group. For a t-shirt – a parameter with 4 id.
• Partner to finalize the feed by adding a parameter.
• The layout team had to write “heavy code” to request information for each id.
  

All this complicated the work and increased the time of publishing products with selectors. Now partners do not need to finalize the feed. It is enough to pass one parameter to save time for both the integration team and the partner.

To implement a selector in blocks, you need to pass the “groupId” parameter to the feed.