Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

SOLVED

AA and WebSDK

Avatar

Level 2

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

1 Accepted Solution

Avatar

Correct answer by
Employee

@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

View solution in original post

0 Replies

Avatar

Level 6

@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? 

Avatar

Employee Advisor

@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?

 

Avatar

Correct answer by
Employee

@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