Request for Event Schema Guidance: Adobe Mobile SDK with Processing Rules & Migration to AEP | Community
Skip to main content
J
jaishal
Level 4
September 30, 2025
Question

Request for Event Schema Guidance: Adobe Mobile SDK with Processing Rules & Migration to AEP

  • September 30, 2025
  • 4 replies
  • 1050 views

Hi Adobe Community,

My organization currently uses Adobe Experience Cloud services and the Adobe Mobile SDK to send data via Processing Rules. I’m looking for documentation or examples of the event schema used in this setup—specifically how events are structured and sent to Adobe Analytics or other services.

Additionally, we’re planning a future migration to Adobe Experience Platform (AEP) using Adobe Experience Platform Edge Network (AEP). I’d like to understand the equivalent XDM event schema structure for this implementation—how events are defined, what standard/custom field groups are typically used, and how to construct and send these events using the Mobile SDK.

Any guidance, schema samples, or best practices would be greatly appreciated!

Thanks in advance.

4 replies

Jennifer_Dungan
Community Advisor and Adobe Champion
Jennifer_DunganCommunity Advisor and Adobe Champion
Community Advisor and Adobe Champion
September 30, 2025

I wish I could offer some advice... honestly, we don't have any plans to move to CJA any time soon, so we cheated and used the Adobe Data model instead of full XDM schemas... leaving most of our old context variable code in place, and continue to use Processing Rules... 

J
jaishalAuthor
Level 4
September 30, 2025

Do you have documentation or any adobe documentation for current context data variable event schema for all events and eVars with you?

    Jennifer_Dungan
    Community Advisor and Adobe Champion
    Jennifer_DunganCommunity Advisor and Adobe Champion
    Community Advisor and Adobe Champion
    September 30, 2025

    The best part about using the Adobe Data model, I didn't actually have to configure a true schema... I just created a basic empty schema, lol

     

    https://experienceleague.adobe.com/en/docs/analytics/implementation/aep-edge/data-var-mapping

     

    This is literally my schema... it only has the stuff that is automatically there when its created:

     

    There are two ways to go about using the Data Model... if you want to keep your trackState and trackAction calls, I believe you can use the Edge Bridge extension.

     

    We actually changed our implementation to SendEvent, since we did want to make use of a few features that could only work using the newer sendEvent (such as collecting referrer data for our Universal Links).

     

    But basically, we pass a few things into the XDM (like the ECID, pageName, etc) and the rest through the Adobe Data model (using our existing context variable formatting and existing rules - with a few minor adjustments).

     

     

    Note, somehow we ended up with 2 XDMs (one with some of our custom data, like app name) which shows here, but the standard one with the ECID doesn't show up... but we can see the results in the raw data and in the post-processing.

      Vinay_Chauhan
      Community Advisor and Adobe Champion
      Vinay_ChauhanCommunity Advisor and Adobe Champion
      Community Advisor and Adobe Champion
      October 2, 2025

      Hi @jaishal 

      Great question, you’re essentially comparing two different models -

      1. Current (Mobile SDK + Processing Rules --> Adobe Analytics)

      • With the Mobile SDK today, data is sent as context data / variables and transformed using Processing Rules before it lands in Adobe Analytics.

      • There isn’t a fixed “event schema” in this model - events are just hits with key/value pairs that get mapped to Analytics variables (eVars, props, events, etc.).

      2. Future (AEP Edge + XDM schemas)

      • When you move to AEP and the Edge Network, events must conform to an XDM schema.

      • The base is the XDM ExperienceEvent class (includes fields like _id, timestamp, and an identityMap).

      • You extend this with field groups:

        • Standard ones like Mobile Lifecycle Details, Commerce Details, Device / App Information, etc.

        • Custom field groups for business-specific in-app actions or attributes.

      • The Adobe Mobile SDK for Edge lets you send structured xdm payloads.

      Jacinda E
      Community Manager
      Jacinda ECommunity Manager
      Community Manager
      October 6, 2025

      Hi @jaishal - just wanted to follow up here. Did Jennifer and/or Vinay's responses in this thread help you solve your issue? If so, please consider selecting a correct answer to resolve the question and help others who might have a similar question in the future find this thread 😊

      manojsingh-tech
      manojsingh-tech
      Level 2
      October 6, 2025

      hi @jaishal  ever and props is easy to do as said in the documentation. But if you are looking for events it's tricky, We did it in our mobile app, we have done something like this. if you are going with AEP Mobile SDK then in the datastream you can fire the events and you can also manipulate the data steam before it reaches the AEP.

      here is an example. in the Data steam you will have the option of Edit Mapping.  in the source you can provide the evar and prop you will be using to fire the events. 

       

      Source field - you have to put the ever you want to use and also the string where that event has to fire 

      Targeted field - specify then event which you want to fire.

       

      Terms & ConditionsAccessibility statement

      Loading footer...