Help migrating the at.js library to websdk via Tealium | Community
Skip to main content
A
AlejandroCo3
New Member
August 4, 2025
Question

Help migrating the at.js library to websdk via Tealium

  • August 4, 2025
  • 2 replies
  • 345 views

Hello,

 

We have been migrating from at.js to WEBSDK for some time now, and even though we have reviewed the events, they are not being ingested correctly into Adobe Experience Platform. We have everything configured, both the extension and configuration of the WEBSDK tag in Tealium, as well as the configuration of the datastreamID. The target experiences are also displayed on the website, but since the data is not ingested into CDP-AEP in CJA, nothing appears, because both the events from our main XDM and those from the “adobe_target_classification_events” schema-dataset are missing, which match using the correlationID.

 

In the logs, we have seen that it fails because an object from the schema is missing in the decisioning.propositionDisplay event, but we do not know how to add the XDM of the missing object. However, we also do not know how they are ingested into the “adobe_target_classification_events” dataset.

 

Has anyone already performed this migration and can help us? We would greatly appreciate it, as we are unable to move forward in any way.

 

Regards,

Alex

 

2 replies

AnkitJasani29
AnkitJasani29
Level 6
August 5, 2025

Hi @alejandroco3 ,

You can try below approch

  1. Configure the AEP Web SDK in Tealium
  2. Send view events with renderDecisions
  3. Fire propositionDisplay XDM
  4. Map into CJA (Add your main XDM dataset and the Adobe Target Classification Events lookup in CJA)

More details here

Thanks,

Ankit

    A
    AlejandroCo3Author
    New Member
    August 5, 2025

     

    Hi Ankit, thanks for your help.

    We've already done all this, but the problem is that no data is being stored in CDP-AEP. For the “web.webpagedetails.pageViews” event, no target appears, and for the “decisioning.propositionDisplay” event, we need to include the XDM of the custom object, but we can't find a way to include this object in the decisioning HIT.

     

    All calls are sent with renderDecision set to true.
    The decisioning call only contains the “_experience,” and since the JSON structure differs from the AEP schema, the ingestion fails. It should include our custom object.

     

    Thanks,

    Alex

    Michael_Soprano
    Michael_Soprano
    Level 10
    August 7, 2025

    slight off topic - but for which this one is used for - “adobe_target_classification_events” dataset?

    Terms & ConditionsAccessibility statement

    Loading footer...