Customer-Defined Signals with switch to Web/MobileSDK | Community
Skip to main content
U
user000111
New Member
June 18, 2025
Question

Customer-Defined Signals with switch to Web/MobileSDK

  • June 18, 2025
  • 1 reply
  • 293 views

Hello -

 

We currently create traits using many of the Customer-Defined Signals defined in the below article such as c_pageurl, c_pagename, c_evar19, c_contextdata.analytics.buttonclicktype, etc.

 

As we transition to the Web & Mobile SDK, is there something different that we should be using? Or do those Signal names carry over? We are trying to understand if we need to update the trait logic with the change to the SDK. Or will our traits/segments still work post-sdk change.

 

We’ve received feedback that the Schema Location is updating to be like this -- xdm._experience.analytics.customDimensions.eVars.eVar1 – but not sure if this is quite the same as signals?

 

https://experienceleague.adobe.com/en/docs/analytics/admin/admin-tools/manage-report-suites/edit-report-suite/report-suite-general/server-side-forwarding/ssf-reference

 

Thanks!

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

1 reply

ezhil_raja
ezhil_raja
Level 4
June 18, 2025

After migrating to Adobe Experience Platform WebSDK, signal names often change to align with the new XDM schema structure. This can impact downstream components like trait definitions in AAM or other activation tools.

For one of our clients, we handled this by updating trait definitions using an OR condition, allowing both the old and new signal names to coexist temporarily. This ensured uninterrupted audience qualification and smooth transition without data loss.

Always validate your schema mappings and downstream dependencies post-migration to avoid surprises.

Terms & ConditionsAccessibility statement

Loading footer...