Submissions are now open for the 2026 Adobe Experience Maker Awards
SOLVED
EventType in Mobile SDK implementation through Edge for Analytics.
We are using Edge.sendEvent() to track mobile app interactions in analytics adobe suite.
Question 1) For something like this, do you use eventType in your XDM schema? Does it matter at all for analytics? Based on my understanding, the use of eventType in the payload would look like the below. Does that look right?
Question 2)
I see two event type options, one for screenviews and one for link clicks. What would I use for non click events like scrolling, and form view (just viewing a form)?
- web.webinteraction.linkClicks
- web.webpagedetails.pageViews
1 Accepted Solution
Correct answer by
Hi @BertBru
an eventType is required (afaik) in a sendEvent call, but the value you choose is "mostly" up to you.
In other words, while the event value for page views and link clicks does not explicitly have to be set to this specific value, it is recommended to use the default values since there might be functionalities that only work with these. For instance, the Launch Web SDK extension has an "event bundling" feature that only works with the default page views event type.
More importantly, additional fields must be set like for instance
web.webPageDetails.pageViews.value = 1 to indicate a page view and web.webInteraction.linkClicks = 1 for interaction tracking which are missing in your payload.
Have a look at these pages, should hopefully make it clearer.
https://experienceleague.adobe.com/en/docs/experience-platform/xdm/classes/experienceevent#eventType
So, you will still be using pageviews and linkclicks eventTypes.
For your concrete question about the form views, I would choose link clicks since you may likely anyway track a page view of the surrounding page. But this really depends on your requirements.
Sometimes, when a form fills out the whole page, the page name could indicate this instead and a page view could suffice.
Cheers from Switzerland!
Correct answer by
Hi @BertBru
an eventType is required (afaik) in a sendEvent call, but the value you choose is "mostly" up to you.
In other words, while the event value for page views and link clicks does not explicitly have to be set to this specific value, it is recommended to use the default values since there might be functionalities that only work with these. For instance, the Launch Web SDK extension has an "event bundling" feature that only works with the default page views event type.
More importantly, additional fields must be set like for instance
web.webPageDetails.pageViews.value = 1 to indicate a page view and web.webInteraction.linkClicks = 1 for interaction tracking which are missing in your payload.
Have a look at these pages, should hopefully make it clearer.
https://experienceleague.adobe.com/en/docs/experience-platform/xdm/classes/experienceevent#eventType
So, you will still be using pageviews and linkclicks eventTypes.
For your concrete question about the form views, I would choose link clicks since you may likely anyway track a page view of the surrounding page. But this really depends on your requirements.
Sometimes, when a form fills out the whole page, the page name could indicate this instead and a page view could suffice.
Cheers from Switzerland!
Thank you! Your explanation and the links are very helpful.
Regarding this
web.webPageDetails.pageViews.value
I see similar fields inside of _experience.analytics, any idea why? and if one can replace the other?
Related Conversations
