Developer forum

Hi Adrian

When is it one and when is it another?

In the user create apps you can fill out custom fields if you want a very distinct difference between the two. Or you can use 2 different user groups when they signup/creates an account.

Then you can simply use the group they are in - or create query based off the group or custom field.

Hi Nicolai,

There could be distinct actions. A user can create an account and receive a voucher. Then, later in the process, the user can decide to subscribe to the newsletter and will receive a different voucher.
I know I can identify them in separate groups, but I am not sure if it's enough to create the recipient lists just based on the groups.
If I remember correctly, the recurrent Email job would pick up the new members of a group. Which, in this case, may be enough.
Is this correct?

Thank you,
Adrian

Hi Nicolai,

One more thing. For the newsletter message to the rewarded users, I will need to include a module/app to send the voucher code. I remember that we used to have an app for this purpose, which was supposed to be attached to a paragraph. But I don't see any standard Email paragraph that would support attaching a module.

Is this by design? We are not supposed to attach modules/apps to Email paragraphs? Is there another way of sending over the voucher codes for rewards?

Thank you,

Adrian

Yes, that is correct. If new users show up in the recipient list of a recurring mail or a flow, the user is seen as new and will receive an email - just once.

We do not currently have an app paragraph for emails - but should be fairly simple to add - so just add that. I think the context voucher renderer will work for emails.

BR Nicolai

Hi Nicolai,

Thank you for the response.

I will add a new App paragraph for emails and use "Voucher renderer".

Thank you,

Adrian