Adobe Employee

Experience League LIVE: Post-session discussion - This is the way...to migrate Analytics to Web SDK

Forum|Forum|1 year ago
May 16, 2024
11 replies
12974 views

Use this thread to ask any questions related to the Experience League LIVE session titled, "This is the way...to migrate Analytics to Web SDK."

Experts are monitoring this thread to ensure your questions are answered. Thanks and we hope to hear from you!

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

J

josephlezcano

Question for you guys, Can we keep both AA & SDK extension and replace send beacon with direct call rule. Inside of the direct call rule we would that takes s object and format to the correct SDK format. There it will send off the proper SDK events.

I would like to do this so I can avoid some of the cleanup and it should allow for me to keep my S obj. This would be a hybrid approach to be able to have both and transition quickly to the SDK. Is something like this possible?

Thanks

joek81541110

Adobe Employee

Hey @josephlezcano ,

Yes, you can do that; you'd populate `data.__adobe.analytics` out of the `s` object.

As long as it's temporary. 😉

J

josephlezcano

Whats the negative side of that? why couldn't we keep it for longer?

H

HilaySh1

I am currently using the script tag to implement adobe analytics in my UI app. Any documentation on if/how to switch to Web SDK?

joek81541110

Adobe Employee

Hey @hilaysh1 ,

This documentation shows how to migration your AppMeasurement to Web SDK:

https://experienceleague.adobe.com/en/docs/analytics/implementation/aep-edge/web-sdk/appmeasurement-to-web-sdk

Hope that helps!

E

Erik_Kulp

I wasn't able to watch the entire webinar, so it might have been covered already, but is there an example of what a web developer would code differently from how they tag events now with App Measurement vs if they are tagging only for Web SDK version? We are about to stat a new project, and would prefer to start that using the Web SDK only approach, but devs currently only know how the old s. version of the code should look like.

joek81541110

Adobe Employee

Hey @erik_kulp ,

This documentation should help:

https://experienceleague.adobe.com/en/docs/analytics/implementation/aep-edge/web-sdk/overview

Let us know if you need more details.

I

Itzmyusrnme

Any feedback on an approach where all XDM mappings happen on the Edge using Data Prep? In the presentation there seems to be a concept of still having both XDM and Data objects included with the sendEvent call made client side, but I'm curious if there are any downsides to only including the Data object?

For example, is it okay to use:

dataObject = {
"__adobe": {"analytics": {"evar1": "some value"}},
"semanticData": {"dataPoint1": "some value"}
}

alloy("sendEvent", {
  "data": dataObject
});

I imagine that by doing it this way I can map data.semanticData.dataPoint1 to a custom XDM field in Data Prep (rather than working with an evar). Is there any downsides to this approach?

joek81541110

Adobe Employee

Hey @itzmyusrnme ,

I cannot think of a downside to sending everything under `data` and mapping in Data Prep.

Thanks.

A

andreis65119307

Level 3

Hi,

I'm using two actions to update the variable and then, with a third one, I'm sending the data.

It looks that the events from the two update variable actions are not merged in my case.

Any suggestions?

Thank You!

joek81541110

Adobe Employee

Hi @andreis65119307,

Are you doing something similar to the attached screenshot? It works on my side.

Can you provide more information? Is the Tags Property setting `run rule components in sequence` turned on?

Thanks

A

andreis65119307

Level 3

Hi @joek81541110

I'm updating the variable in two separate rules.

One rule updates the variable on product pages with the product data and one rule updates the variable on every page and sends the variable.

In the debugger I see the product data merged but the events are missing.

Yes, `run rule components in sequence` is turned on, Analytics Extension is using the above logic to construct the hit.

Thank You!

A

ankitagarwal05

Level 3

Hi Team,

Amazing session and new information about using the Update variable event type under AEP web SDK Extension.

My question is on the Schema structure we have for Adobe Analytics. I am using "Adobe Analytics ExperienceEvent Template" Schema structure which looks like the below:

{
"_experience": {
"analytics":{
"customDimensions": {
"eVars": {
"eVar1": "Raven",
}
}
}
}
}

But in update variable, the structure we have is like below:

{
"__adobe":{
"analytics": {
"eVar1": "Raven",
}
}
}

Due to this mismatch, I am not able to see the eVar1 value mapped to Adobe Analytics. Is there any Adobe Analytics Schema that we can use to map Analytics variables directly?

Thanks

A

andreis65119307

Level 3

Hi,

You don't need a schema for Analytics if the variable is set to generate an object as data.

Trace back your steps. Maybe in the send event, you used the data element in the XDM field instead of data.

M

MarshallSe

I am looking at more things than just this migration but was wondering why I wasn't seeing all the options I thought I should be seeing when going into Data Collection.

M

MarshallSe

I have access to Data Collection and I thought that all the pieces for WebSDK implementations were included but I don't see any options on left side of menu besides Tags. Should I have access to things like Data Sources, Schema, etc.? Or is this something that needs to be provisioned or purchased in addition?

A

andreis65119307

Level 3

Yes, you should. Probably you're missing some permissions in Platform.

M

MarshallSe

Thanks, I thought I was an admin on everything but will check to see if maybe I am missing permissions somewhere.

A

aguseranalytics

Level 3

Hi @joek81541110,

Thanks for the informative session.
Need to know the basic difference on why and when should we use the 'Data' variable object over XDM object? Like, earlier we used to create schema in AEP, add the Analytics field group in it, so that we can map it in Data-Collection and send to AA report suite.
And now checking the 'Data' object seems like working on Adobe Analytics extension configurations again, so under what use cases, we need to chose data variable over xdm object, any specific scenarios around that?

Thanks

joek81541110

Adobe Employee

Great question, @aguseranalytics!

I believe Mitch goes over the details in the first part of the demo, but in general, here's the heuristic when migrating:

IF: Staying on established solutions (like Analytics, Target, or AAM) for a while: use data only.

IF: Staying on established solutions AND adopting AEP apps (Like CJA, AJO, or RTCDP)
OR

IF: Moving to the AEP apps directly and will stop using the established solutions.

1. Use data only and map into XDM in Data Prep. (You can leverage the new Analytics mapping functions to map your events and products strings)

2. Use XDM directly on the client side.

I don't know that there's any use case for the Analytics fieldgroup any more.

I hope that helps.
Joe

A

aguseranalytics

Level 3

Thanks @joek81541110for explaining the above point!!

R

Ronny3

Level 2

After installing the Web SDK extension in a tag property in AEP Data Collection I found out that I can't see Datastreams in the left hand menu. Is it correct that an AEP licence is required to use the Web SDK extension instead of the Analytics extension? This would be a bummer.

joek81541110

Adobe Employee

Hey @ronny3 ,

You don't need an AEP license to use the Web SDK. It's a permissions issue.

Please follow the steps in the following doc, and you should be all set: https://experienceleague.adobe.com/en/docs/experience-platform/collection/permissions#manage

Thanks!

Y

YunaKi2

Hello, I can also add up on previous comments with andreis65119307.

We’ve set two rules: the first rule fires at the beginning to set all common variables (eVar, props, and events), and the second rule keeps updating variables and sends events to Adobe Analytics (AA) through the web SDK. However, events are not being attached from the first rule, and the event dropdown is limited to 250 options, unlike the current Adobe Analytics extension, which allows up to 500. Could you confirm whether attaching events using rules is not working? Additionally, is the dropdown menu for events intentionally set to 250?

joek81541110

Adobe Employee

Hi @yunaki2

We are releasing an enhancement to the drop-down to list 1000 events.

As for the rules not persisting data, I suggest working with your consultant or account manager to open a ticket for the engineering team to investigate.

Thanks.

Show more replies

Sign up

Login with SSO

Login to the community

Login with SSO

Scanning file for viruses.

This file cannot be downloaded