AEP Mobile SDK sendEvent API - Using Context Data or not? | Community
Skip to main content
John_Man
Community Advisor
John_ManCommunity Advisor
Community Advisor
July 10, 2024
Solved

AEP Mobile SDK sendEvent API - Using Context Data or not?

  • July 10, 2024
  • 1 reply
  • 1048 views

Hi,

 

We are migrating from ACP Mobile SDK to AEP Mobile SDK, and would like to migrate all the trackState/Action calls to sendEvent API.

 

Since there is an extensive data structure defined in the existing Context Data, we are not planning to convert them into the XDM structure on the client side code, and will use sendEvent API to send the existing Context Data instead, and then use Data Prep in Data Stream to map the Context Data fields to the XDM Analytics fields (in this way we can take out all the processing rules in AA).

 

Is the above a good pratice or there's any potential drawbacks? Especially on using sendEvent API to send Context Data instead of XDM.

 

Thanks,

John

 

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

@john_man 

You can't send non XDM data using send event API.

If you are planning to migrate AEP mobile SDK but still want to use track state and track action events you can use edge bridge extension to send data using track state and action API to edge network and then utilize data prep to map into analytics variables.

1 reply

Ankit_Chaudhary
Community Advisor
Ankit_ChaudharyCommunity AdvisorAccepted solution
Community Advisor
July 12, 2024

@john_man 

You can't send non XDM data using send event API.

If you are planning to migrate AEP mobile SDK but still want to use track state and track action events you can use edge bridge extension to send data using track state and action API to edge network and then utilize data prep to map into analytics variables.

    John_Man
    Community Advisor
    John_ManCommunity AdvisorAuthor
    Community Advisor
    July 13, 2024

    Hi @ankit_chaudhary 

     

    Yes, we are aware of using Edge Bridge extension which can keep using track State/Action. Our app developer is happy to change it to use sendEvent API, but since the existing context data is quite complex, they do not have the capacity to convert them to use XDM at this moment.

     

    We have done some test, and sending context data with sendEvent API works fine, as long as we keep the following as part of the sendEvent API,

     

    {xdmData:{"eventType" : "web.webpagedetails.pageViews"}

     

    So the question goes back to whether this is a good practice or supported approach or if there is any potential draw back?

     

    Thanks,

    John

     

      Terms & ConditionsAccessibility statement

      Loading footer...