Hi Team,
Any help will be appreciated on understanding how websdk event call will differentiate?
Views
Replies
Total Likes
@you may want to have a look at the WebSDK's new guided events feature in the sendEvent action dialog.
this will hide/remove some fields from the requests, depending on which configuration you choose.
it has been a challenge in the past to not unintentionally send data to analytics when you only want to do a target activity. Hence, they have come up with a solution that shall help you during the setup
Web SDK uses an interact call to send data to AEP and load target as well using send event command however you can use xdm.eventType field in experience event schema to identify the different request types.
Generally I've seen organizations will load target and send XDM data in the same page view call depending on the use cases, however you can also load target separately on page top without sending any data using send event command and use Decisioning Proposition Fetch event type to differentiate it from page view, link click and other events.
Check this for accepted values in event type field
The Web SDK allows you to send data to Adobe Experience Platform (AEP) and load Target by using a "send event" command. To tell different types of requests apart, you can use a field called "xdm.eventType" in the event data.
If you only need to load Target at the top of the page without sending any extra data, you can still use the "send event" command. Just set it to a special type called "Decisioning Proposition Fetch." This makes it evident to you how it differs from other behaviors such as clicking links or viewing pages.
Also, there's a new event feature in the Web SDK's sendEvent action dialog. It makes it easier to manage different types of events.
Views
Replies
Total Likes
Views
Likes
Replies