AEP integration with adobe target | Community
Skip to main content
Poonambhatia1990
Poonambhatia1990
Level 2
September 26, 2023
Solved

AEP integration with adobe target

  • September 26, 2023
  • 1 reply
  • 3776 views

Hello All,

 

1. I would like to understand the end to end process of stitching AEP with adobe target

2. What benefits we can have by using AEP 

3.Our websites are built on SPA framework which needs to use above point1 to be implemented first in order to run the test  
4.We are using experience fragment which appears blank when assembled in adobe target (regardless of above point)

 

Appreciate your assistance on it.

 

Regards,

Poonam

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 dwright-adobe

Ok. Most of the major integration components work (profile attribute and audience sharing) work with at.js, but the attributes and segments are not available until the next session after authentication with at.js. It's much faster with Web SDK, but not required.

 

Here is one way to think about the business value. If you are a Target power user, you are probably familiar with the usefulness of Target's profiling system. You can collect and store info about the user across sessions and then use it for personalization. For example, you could have a Target profile capture the last product they viewed in a session and then show them a personalized message with that product on the very first page view when they return to the site. With the Real-Time CDP integration, assuming it's a known user (people authenticate on your website), the profile becomes much larger. Not only can you profile based on browsing behavior, but you also have access to attributes from additional, non-web, non-mobile sources like your CRM, call center, loyalty system etc.

1 reply

D
Adobe Employee
dwright-adobeAdobe Employee
Adobe Employee
September 27, 2023

@16399477 ,

Review these videos to see if they contain the details you need. The second video dives into the set up process:

https://experienceleague.adobe.com/docs/integrations-learn/experience-cloud/tutorials/rtcdp-target/web-sdk-and-target-destination.html?lang=en

 

Do you have Target implemented with Web SDK or at.js? Both will work, but a Web SDK implementation will be able to retrieve Platform data faster.

 

One of the main benefits of integrating Platform with Target is that you will have access to known customer data in Target which you have ingested into Platform. Ideally you would be ingesting data from many sources into Platform (CRM, loyalty, call center, etc). This is rich data that you can use for onsite and in-app personalization in Adobe Target, similar to how you might be using Target's native profile system today. You would have more customer data to work with.

 

To get rich, known customer data from Platform, you typically need to have an authentication step on your website or mobile app and send the resulting customer id up through your Web SDK or at.js implementation. Platform builds an identity graph which can then help build a rich profile in Platform access other datasets enabled for Profile. When the Web SDK or at.js call go to Target, Target makes a call to Platform on the Adobe backend to retrieve this profile information so it can be used in Target activities.

 

Your SPA architecture shouldn't come into play, assuming you have implemented Target in a way that works with your SPA.

 

Not sure why your experience fragments from AEM are not working correctly. If you see them returned in the network request from your Web SDK or at.js call, then it sounds like an issue with applying them to your page.

 

    Poonambhatia1990
    Poonambhatia1990Author
    Level 2
    September 28, 2023

    Thanks @dwright-adobe  for reply.

    We haven't implemented web sdk yet, still on at.js, our organization has planned to move to AEP which will raise a need to integrate web sdk.

    AEP is new for me hence trying to understand the why and what impact of using it with adobe target.

      D
      Adobe Employee
      dwright-adobeAdobe EmployeeAccepted solution
      Adobe Employee
      September 28, 2023

      Ok. Most of the major integration components work (profile attribute and audience sharing) work with at.js, but the attributes and segments are not available until the next session after authentication with at.js. It's much faster with Web SDK, but not required.

       

      Here is one way to think about the business value. If you are a Target power user, you are probably familiar with the usefulness of Target's profiling system. You can collect and store info about the user across sessions and then use it for personalization. For example, you could have a Target profile capture the last product they viewed in a session and then show them a personalized message with that product on the very first page view when they return to the site. With the Real-Time CDP integration, assuming it's a known user (people authenticate on your website), the profile becomes much larger. Not only can you profile based on browsing behavior, but you also have access to attributes from additional, non-web, non-mobile sources like your CRM, call center, loyalty system etc.

        Terms & ConditionsAccessibility statement

        Loading footer...