Adobe Employee

Tutorial Discussion: Migrate Target from at.js to Web SDK tutorial

Forum|Forum|2 years ago
February 23, 2023
7 replies
69090 views

Use this thread to ask any questions related to the Migrate Target from at.js 2.x to Platform Web SDK tutorial on Experience League. Experts are monitoring this thread to ensure your questions are answered.

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

Amrish_Popat

Level 2

HI @dwright-adobe

We have planned to GO Live with WebSDK but also keep AppMeasurement.js active for 3 weeks after WebSDK go Live. The idea was to study if WebSDK and AppMeasurement.js collect the exact same data in 2 separate Analytics reportsuites. And later the plan was to remove appmeasurement.js when we are confident.

But I am aware that AppMeasurement for Analytics & WebSDK for Target will create issues. Its mentioned in this Adobe Article https://experienceleague.adobe.com/docs/platform-learn/migrate-target-to-websdk/plan-migration.html?...

"A mixed implementation of Platform Web SDK for Target and AppMeasurement for Analytics on a particular page is not supported. However, a mixed implementation across different pages is supported, for example Platform Web SDK on page A, and at.js with AppMeasurement on page B."

Does that stop us from going Live? Do we have to disable AppMeasurement before WebSDK GO Live? AppMeasurement and WebSDK set up works fine on our PreLive but the question is will it impact analytics data ingestion, AEP data ingestion or Target activities/operations in Live?

D

dwright-adobe

Author

Adobe Employee

Hi @amrish_popat ,

Thanks for kicking off this discussion!

It sounds like you are planning on running both Web SDK and AppMeasurement.js simultaneously for a period of time so you can compare the two Analytics implementations side by side. That is outside the scope of this Target migration tutorial, but there are other migration materials we are working on which I am very close to. We have other customers using this approach to help ensure a smooth migration of their Analytics implementation, and I think it's a really good idea. It will result in extra Analytics hits, but you can limit this by simply shutting off the Web SDK sendEvents when you have the amount of data you want.

When it comes to migrating Analytics to Web SDK now and Target later, it hasn't been extensively tested. You can do what you want, but Adobe wouldn't be able to help you if you run into issues, hence "not supported". If you use Analytics data for your Target reporting (A4T) this will definitely break. I can tell you from my personal experience as the implementer of Adobe Target on the Experience League docs and tutorials, we are using Web SDK for Analytics and at.js for Adobe Target and I have not experienced any issues. I am not using A4T. Also, the Web SDK Analytics implementation was already in place before Target was implemented, which is slightly different from your scenario.

"Does that stop us from going Live?" You can do what you want, but you will be limited in your support from Adobe if you encounter issues.

"Do we have to disable AppMeasurement before WebSDK GO Live?" There are other customers who have used this approach, so I think you should be fine with this, especially since this is for a limited time and you are using separate report suites.

"Will it impact AEP data ingestion?" You should be careful if you are currently using the Analytics source connector to ingest data from your AppMeasurement report suite into Platform. If you have two Analytics implementations feeding into Platform and compromising your data integrity.

"Will it impact Target activities/operations in Live" It will definitely, impact A4T. The rest, I can't tell you for sure. Again, this is "unsupported" territory.

Amrish_Popat

Level 2

Hi @dwright-adobe

Thanks a ton for the quick response. Further to this, I wanted to clarify that we would ideally want to keep appmeasurement and websdk for Analytics but only Websdk for target and reading the migration of planning page; it tells me that appmeasurement for analytics and websdk for target won’t work, which isn’t exactly what we want

so just confirming that if websdk is for both AA and AT, and Appmeasurement for a time being parallely won’t impact target activities and A4T?

T

tejpalsinghsahni

Level 2

HI @dwright-adobe ,

we are migrating at.js to websdk, one of the things we utilize mostly is form base component with global scope and utilize js to update content , as per adobe form based compone with scope as _view_ should render automatically with the checkbox as part of your load rule. but this is working for VEC and not for form based any suggestion .

r

T

TRolic1

Level 2

@dwright-adobe We migrated our main web property to Web SDK in June '23, and observed an immediate and drastic drop (-87% May vs July; full month pre-sdk vs full month post-sdk) in ootb AA bounces, and increase (+151%) in ootb AA page views. We do have ongoing Adobe Support engagement on this. How do we better limit calls from impacting basic ootb hit-based metrics?

Note- Visits stayed relatively flat (+3% for full month prior to Web SDK go live vs full month after).

Thanks.

Tom

D

dwright-adobe

Author

Adobe Employee

Hi Tom,

How are you implemented? Do you have a single call per page load that is used for both Target and Analytics? Or do you have two calls per page load, with one at the top used for personalization and one at the bottom for analytics?

T

TRolic1

Level 2

Two calls- We have a page top (AEP Web SDK, sendEvent) rule and a page bottom (Core, Custom Code, sendEvent) rule.

Tom

T

tarun_jamana8469

Adobe Employee

Hi @dwright-adobe

Had a question related to how can we address A4T reporting while migration. are there any known issues or caveats and will this have any business impact. I did check on the idMigrationEnabled property which will help read the AMCV cookie set by previous adobe experience cloud implementations. Do the customers need to take care of anything else.

D

dwright-adobe

Author

Adobe Employee

Hi @tarun_jamana8469 ,

Good question. Be sure to check the migration checkbox for Target too, so that the mbox cookie details will transition.

I haven't heard of any specific issues with migrating activities with A4T. Are you going to use a two call or single call implementation of Web SDK? The A4T mechanism is a little different between those options, which is good to be aware of.

T

tarun_jamana8469

Adobe Employee

The single call or a two call implementation is not yet finalized with the customer. Can you please help me understand how the A4T differs between these mechanisms

S

SachinJ

Level 2

I am currently integrating Adobe Target with WebSDK to implement a personalization experiment and have made the following progress:

WebSDK and Target Extension Setup: Successfully configured WebSDK with the Adobe Target Extension.
Catalog Upload: Uploaded a catalog in Adobe Target using a CSV feed containing product data, including thumbnails, categories, and other relevant details.
Recommendation Models: Built custom and in-built recommendation models to deliver personalized recommendations, specifically a "Recommended for you" feature based on the current item.
Activity Creation and Testing: Created an activity and successfully tested it in a lower environment.

However, we are encountering several challenges where I would appreciate some guidance:

Catalog Corruption: When events are triggered from WebSDK, the catalog is being corrupted. Fields such as thumbnail, name, and value contain empty values, and only the SKU is passed.
Recommendation Rendering Issues: Due to the above catalog issues, the recommendation design displays broken names, links, and images after catalog is corrupted.
Event in WebSDK: With the current WebSDK setup, display events (screenshot attached) are being triggered on the PDP page along with pageViews and productViews. No custom entity attributes are being passed at all but some how catalog gets this and sets it empty, except sku.

I am seeking advice on how to prevent the catalog from being updated with empty values, as I have been unable to locate documentation addressing this issue. Any insights on how to optimize this setup for a production environment would be highly valuable.

For reference, I have consulted the following documentation resources:

Thank you in advance for your assistance.

D

dwright-adobe

Author

Adobe Employee

I just wanted to let you know I see your message, but I haven't heard other reports of this happening. I see in your screenshots you are using custom scopes. Be aware that you cannot set different params on custom scopes made in the same call. All scopes will include the same params.

Are you sure there is no issues with your feed? Are you able to see some records from your feed that are intact? Are you sure you have escaped the fields in your field that need to be escaped? https://experienceleague.adobe.com/en/docs/target/using/recommendations/entities/feeds

S

SachinJ

Level 2

Hi @dwright-adobe ,

Here is my response:

Are you sure there is no issues with your feed?
- I don't think so as I have followed the methods of uploading feeds via .csv from here: (I am attaching sample feed in the response). And after successful feed I see all details filled in accurately as per the feed details "https://experienceleague.adobe.com/en/docs/target/using/recommendations/entities/feeds"
Are you able to see some records from your feed that are intact?
- Yes, Initially when there is no corrupt feed update, all the product catalog looks good without loss of data, but as and when time passes and more mbox events flow in PDP, catalog starts getting updated with only entity.id retained rest is overwritten with blank value
Are you sure you have escaped the fields in your field that need to be escaped?
- I am not 100% sure here if I understood this correctly, but here is what I have done, the field that are blank in feed I have left it with "blank space" as suggested in the above link, coz without blank space feed does not work while uploading. I think am missing the escaped part ? Can you elaborate more on this please. Also, I am confused because instead of corrupting all the fields it overrides all except entity.id.. and I see entityId as is.(Screenshot attached)

product_catalogue_for_target(2)-copy-csv.zip

G

GavinAttard

Level 2

Hi @dwright-adobe

From documentation and postings the below scenario is not clear to me, wondering if you can shed some light.

Client has AA (appmeasurement) and AT.js and use A4T.
The plan is to migrate AA to WebSDK using the data object in the first instance and keeping at.js.
Will this impact the business ability to use A4T?

D

dwright-adobe

Author

Adobe Employee

Hi @gavinattard ,

Thanks for writing. A4T is not supported in that scenario.

The tutorial includes this language:
"Because Platform Web SDK combines and enables multiple Adobe applications, you must coordinate the Target migration of other Adobe applications like Analytics and Audience Manager. All Adobe libraries on a given page should be migrated at the same time. A mixed implementation of Platform Web SDK for Target and AppMeasurement for Analytics on a particular page is not supported. However, a mixed implementation across different pages is supported, for example Platform Web SDK on page A, and at.js with AppMeasurement on page B."
https://experienceleague.adobe.com/en/docs/platform-learn/migrate-target-to-websdk/plan-migration

Because this tutorial is about migrating Target to Web SDK (and not migrating Analytics to Web SDK), it probably didn't occur to us to specifically point out the Web SDK for Analytics and at.js for Target scenario.

A

ajaym75199991

Level 3

@dwright-adobe

We have recently migrated to AEP web sdk for our Analytcis, Target & AAM setup for our various websites and are in process to implement Target server side implementation using delivery API for some of our criticle scenarios of personalisation.

As per

https://experienceleague.adobe.com/en/docs/target-dev/developer/server-side/server-side-overview

clearly suggest If your implementation uses the Adobe Experience Platform Web SDK, you should use the Adobe Experience Platform Edge Network Server API.

Will this client side integration of Analytics, Target & AAM along with Adobe Target delivery API setup works together?

if yes, will A4T works with above setup? is it as per best practices?

What is ideal way to implement A4T & target server side implementation in website where AEP web sdk is implemented?

D

dwright-adobe

Author

Adobe Employee

@ajaym75199991 ,

Good questions. Hybrid server implementations are beyond the scope of the at.js to web sdk migration tutorial and I have limited experience with them. I think you should definitely use the Edge Network Server API (and not the Delivery API) and I think a lot of your questions will be addressed in this document: https://experienceleague.adobe.com/en/docs/experience-platform/web-sdk/personalization/hybrid-personalization#overview

Sign up

Login with SSO

Login to the community

Login with SSO

Scanning file for viruses.

This file cannot be downloaded