Email confirmation with ACS (triggered from service)

[sonjaluoto]

I'm working with Adobe Campaign Standard and I'm trying to create an email confirmation. What I have now is:

1. Profiles coming up to ACS from our company's website (via API).
2. Profiles are added into services (based on some profile information).

What I would like to happen after profile has been added to a service, is this:

1. ACS would automatically send an email confirmation message (sending should be triggered by adding profile to a service)
2. Confirmation link would update a boolean field in one of our custom resource

I don't want to use blacklist field in this case since each of our service will have their own email confirmation.

Every documentation I've read talks about this double opt-in process, which includes an acquisition landing page that I don't need at all. Is there another way to create an automated email confirmation message and link it to a certain service?

Have I missed some good documentation about this? Any ideas?

[florentlb]

Hi,

You should be able to select a confirmation message template in the properties of the service. You can replace this template (well, these templates as you can select one for subscription and one for unsubscription) by a template of your choice.

You can manage your email templates from Resources > Templates.

See the docs here: Creating a service

Let me know it this helps,

Florent.

[sonjaluoto]

Hi,

I have selected a confirmation message template in my service. I added a few profiles with my email address to the service but never got the confirmation message. Should selecting the confirmation message work as a trigger or should I create it somewhere else?

[florentlb]

Hi,

I'll double check with the team that this is supposed to work with subscriptions coming from the API.

Florent

[florentlb]

Hi again,

I got confirmation that the API does not trigger confirmation messages. A workaround would be to create a workflow that triggers every x minutes (where x has to be greater than 10), and that would retrieve all new subscribers to this specific service with an incremental query, and fire the confirmation email.

There is an example with services here: Incremental query

Hope this helps,

Florent.

[sonjaluoto]

Hi,

Thanks Florent, I managed to create an incremental workflow retrieving new subscribers to a service. However I'm still struggling with the confirmation email and landing page that changes one field in profile's data. Now I have:

1) confirmation email

2) confirmation landing page

On the landing page I have a button that should confirm the subscription (=change the field from false to true) but nothing happens. I get the thank-you page, but no data is changed in profile. I have defined the correct data field in landing page's properties -> job -> form parameter mapping. Is this the right way to do it?

[florentlb]

Hi,

Your use case might differ slightly from what is described here if that's what you are referring to: Setting up a double opt-in process.​ But the field should still be updated upon confirmation.

Which field are you trying to update (as you mentioned in your first message that it is in a custom resource)?

Let me know,

Florent

[sonjaluoto]

You're right, it's a bit different use case than the instructions (yes, I'm referring to the documentation you linked). I have a custom resource called "generalCampaign" and in there I would like to update a field called "emailConfirmed." I've set this up in the landing page properties:

I wasn't quite sure if the filter parameter should be "email", guide didn't say anything about that.

In addition I have a transactional email linking to this landing page.

[sonjaluoto]

Any tips for the above?

[florentlb]

Hi,

I'm not sure that your custom resource is available from the context of the landing page, that may explain why it is not updating. Is this resource linked to the profile resource?

Let me know,

Florent

[sonjaluoto · Accepted solution]

Hi,

you're right, my field in custom resource wasn't available. I found a work-a-round solution using another field (in profile table) and creating a landing page with a checkbox that changes the field value.

Br,

Sonja