ACS - Trigger options | Community
Skip to main content
eveline8
eveline8
Level 4
March 22, 2018
Solved

ACS - Trigger options

  • March 22, 2018
  • 4 replies
  • 3183 views

Hi!

I need to create a campaign trigger for Cart Abandonment.

I'm following the documentation (https://helpx.adobe.com/campaign/standard/integrating/using/abandonment-triggers-use-cases.html) and I have a doubt when I have to create the event trigger in Campaign.

As indicated in the attached screenshot, I have to choose the targeting dimension in the trigger option.

What are the differences about the 2 choises (Real-time event and Profile)?

Thanks!

Eveline

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by florentlb

Hi Eveline,

So in your case you are using the Triggers integration, right?

If so, when I look at this specific section about Triggers in the documentation: Adobe Campaign Help | Configuring Campaign-Triggers integration​, it states that the transactional message is automatically created when the trigger is published, and that you only have to personalize it (including with profile data).

"If you enrich the event data with Adobe Campaign profile data, you can personalize the message based on this information. To personalize your message, select Transactional event > Event context and select a field."

So to me in any case with a Trigger event you will be able to use the event data, and in addition to that, you can use profile data if you enriched the event.

Hope that makes sense,

Florent

4 replies

florentlb
florentlb
Level 10
April 18, 2018

Hi Eveline,

As explained in the documentation: Adobe Campaign Help | About transactional messaging​, this choice is according to your use case.

  • Event transactional messages targeting an event. The data contained in the event itself is used to define the delivery target.

  • Profile transactional messages targeting profiles from the Adobe Campaign marketing database. You can use information from the Adobe Campaign database to send a transactional message based on customer marketing profiles.

    So basically, if you choose Event, you can only use the data stored in the event itself. And if you se Profiles, you will be able to add more personalization for the specific profile.
    Florent
    eveline8
    eveline8Author
    Level 4
    April 18, 2018

    Hi Florent,

    thanks a lot for your answer.

    When we set the Triggers, we insert some variables (prop or evar) from Adobe Analytics like Product type, Product image....

    So, if I understood well:

    In the first case I can use these variables that I have passed in the trigger for delivery personalization.

    In the second case I can use the information stored in each profiles in Adobe Campaign (like Fist Name, Last Name...) but I can't use the information passed in the triggering.

    Is it right? Or in the second case I can use the information passed in the trigger too?

    Thanks,

    Eveline

    florentlb
    florentlbAccepted solution
    Level 10
    April 19, 2018

    Hi Eveline,

    So in your case you are using the Triggers integration, right?

    If so, when I look at this specific section about Triggers in the documentation: Adobe Campaign Help | Configuring Campaign-Triggers integration​, it states that the transactional message is automatically created when the trigger is published, and that you only have to personalize it (including with profile data).

    "If you enrich the event data with Adobe Campaign profile data, you can personalize the message based on this information. To personalize your message, select Transactional event > Event context and select a field."

    So to me in any case with a Trigger event you will be able to use the event data, and in addition to that, you can use profile data if you enriched the event.

    Hope that makes sense,

    Florent

    eveline8
    eveline8Author
    Level 4
    April 19, 2018

    Thanks a lot Florent!

    Eveline

    Terms & ConditionsAccessibility statement

    Loading footer...