Triggers Integration with Adobe campaign Standard | Community
Skip to main content
S
shubhamRajeshirke
Level 2
June 17, 2021
Solved

Triggers Integration with Adobe campaign Standard

  • June 17, 2021
  • 3 replies
  • 3734 views

Hi All,

I tried to integrate triggers with ACS. For that i have created a trigger, an event, a transactional template and have published it. I am sending email id in one of the eVar from analytics and trying to enrich it with the profiles schema but it is not happening.

I am getting the error as "Unable to resolve alias to a valid profile in Adobe Campaign"  .

when i tried to trigger the same event through an api using postman i am able to receive the email.

Can anyone help me to map this trigger with the profiles schema.

 

Regards,

Shubham

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 costa_n11

Hi Shubham

Using Experience Cloud Trigger with ACS requires a few more steps than just defining the trigger and the message

  1. In People Core Service (People in the 9 dot menu of Experience Cloud), you need to create a new Customer Attribute, make sure to give an unique integration code, you could call it "emailId" for clarity

 

  1. Then on the website, when your email id is captured, you need to set the email id to the integration code via the setCustomerIDs of Experience Cloud ID Service, if you want to use later one Shared Audience, you could also set the "AdobeCampaignID" integration code (please respect the syntax) and make sure the "AdobeCampaignID" is set AFTER the "emailId" integration code

 

  1. Now in ACS, you have to define a Data Source using "emailId"

 

Now you have the backbone on your website to link your trigger to ACS

 

In ACS, when using trigger, the Profile MUST exist PRIOR the invocation of the trigger itself.

Looking at the error, you might have missed some of the above,

Thanks
Denis

3 replies

M
mmbb110
Level 9
June 18, 2021
Is this event based transactional or profile transactional message?
S
shubhamRajeshirkeAuthor
Level 2
June 18, 2021
I Think it is based on event. A trigger is triggered from analytics and in the eVar i am passing the email id . This eVar i am mapping with the email column in profiles schema in enrichment section to trigger the email. Basically i am following the cart abandonment example from the adobe documentation.
C
Adobe Employee
costa_n11Adobe EmployeeAccepted solution
Adobe Employee
June 24, 2021

Hi Shubham

Using Experience Cloud Trigger with ACS requires a few more steps than just defining the trigger and the message

  1. In People Core Service (People in the 9 dot menu of Experience Cloud), you need to create a new Customer Attribute, make sure to give an unique integration code, you could call it "emailId" for clarity

 

  1. Then on the website, when your email id is captured, you need to set the email id to the integration code via the setCustomerIDs of Experience Cloud ID Service, if you want to use later one Shared Audience, you could also set the "AdobeCampaignID" integration code (please respect the syntax) and make sure the "AdobeCampaignID" is set AFTER the "emailId" integration code

 

  1. Now in ACS, you have to define a Data Source using "emailId"

 

Now you have the backbone on your website to link your trigger to ACS

 

In ACS, when using trigger, the Profile MUST exist PRIOR the invocation of the trigger itself.

Looking at the error, you might have missed some of the above,

Thanks
Denis

    D
    dsmims
    Level 2
    September 9, 2021

    Just to add to @costa_n11 

    What I understand is that "Unable to resolve alias to a valid profile in Adobe Campaign" means ACS cannot link your trigger to an existing profile via the declaredID (if using this) or using the Marketing CloudID/ECID.

     

    The MarketingCloudID/ECID route, just requires less work, and starts by sending an email to a profile, they'd open and click in this email (taking them to your site). The click generates a MarketingCloudID/ECID (you can see the value on the tracking log "sourceID" field). This value will then persists on your website as a user navigates, at some point  hopefully they do something match the criteria for a trigger. That data is fired to ACS and that ID used to reconcile to an existing profile. 

     

    I believe this works best for "profile based transactional messages"

    Terms & ConditionsAccessibility statement

    Loading footer...