AA and WebSDK | Community
Skip to main content
S
SCB21
November 4, 2022
Solved

AA and WebSDK

  • November 4, 2022
  • 3 replies
  • 1259 views

Hi,

What would be the impact if we bring both AA and WebSDK into AEP?  Would this impact any profiling or segmentation in general?

Thanks

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 Danny-Miller

@scb21 I'm assuming you mean through two mechanisms:

  1. AA Data Connector
  2. Web SDK

This will impact:

  1. Schema design, each uses a different Field Group
  2. The same event comes in twice, once for AA and once for Web SDK
  3. How you segment
    1. Because you have different schema designs, users can segment using different fields
    2. Any aggregation may pick up both events
    3. Any sequence segmentation may cause strange results depending on how users understand and use 2 above.
  4. Any use of the Data Lake (e.g. Query Service or CJA)
    1. Each will have its own dataset
  5. Latency
    1. The AADC takes a little longer to come into AEP
  6. AJO
    1. Related to 2
    2. Two events coming in may cause AJO to trigger twice
  7. Destinations may have a remote chance of triggering twice

3 replies

Anil_Umachigi
Adobe Employee
Anil_UmachigiAdobe Employee
Adobe Employee
November 6, 2022

@scb21 Could you expand more on the question/use case? 

When you say segmentation/profiling? is this within reporting interface( analysis workspace) or "Segments" ( a.k.a audiences) within AEP? 

S
SCB21Author
November 8, 2022

HI @anil_umachigi,

It's for segments

VaniBhemarasetty
Adobe Employee
VaniBhemarasettyAdobe Employee
Adobe Employee
November 8, 2022

@scb21  Are you planning to create a dataset where are you going to send AA data that is collected and the web SDK data which is already added in the data streams at the same time?

 

Danny-Miller
Adobe Employee
Danny-MillerAdobe EmployeeAccepted solution
Adobe Employee
November 8, 2022

@scb21 I'm assuming you mean through two mechanisms:

  1. AA Data Connector
  2. Web SDK

This will impact:

  1. Schema design, each uses a different Field Group
  2. The same event comes in twice, once for AA and once for Web SDK
  3. How you segment
    1. Because you have different schema designs, users can segment using different fields
    2. Any aggregation may pick up both events
    3. Any sequence segmentation may cause strange results depending on how users understand and use 2 above.
  4. Any use of the Data Lake (e.g. Query Service or CJA)
    1. Each will have its own dataset
  5. Latency
    1. The AADC takes a little longer to come into AEP
  6. AJO
    1. Related to 2
    2. Two events coming in may cause AJO to trigger twice
  7. Destinations may have a remote chance of triggering twice
    Terms & ConditionsAccessibility statement

    Loading footer...