Expand my Community achievements bar.

Applications for the 2024-2025 Adobe Analytics Champion Program are open!
SOLVED

External Campaign ID Tracking in mobile app

Avatar

Level 2

Dear all,

 

What is the best practice to track the external campaign ID when mobile launch via deeplink?

 

Capture External Campaign ID in lifecycle call or the first state event send (sendEvent)? 

 

sendEvent should be pretty straightforward to do the xdm mapping.

 

but I don't find any related instruction document to tell me the sample coding syntax about how to add that to the lifecycle call (swift and java).

 

Do you guys can share me the ideas?

 

Thank you so much!

 

Regards,

Lemen 

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

Currently we are sending our Campaign Data on the first page... that said, I am not sure if that is the best.. but so far in our implementation we are still trying to figure out how to get context variables added to our lifecycle metrics. While it should be possible, our developers broke lifecycle when they tried (we're using React Native), and we haven't had a lot of time to investigate this much, so it got put on hold.

 

Part of my concern over what is the "right" solution, is that on web, the Instance of Campaigns is available to correlate to the actual page view.. whereas on mobile app, it's either on the page view (but not the first hit of the visit) or it's on the first hit (lifecycle) but then the campaign is only the attributed data and not the instance. So there's lots of considerations...

 

I wish I could merge the lifecycle metrics into the first page and get the best of both worlds.

View solution in original post

1 Reply

Avatar

Correct answer by
Community Advisor

Currently we are sending our Campaign Data on the first page... that said, I am not sure if that is the best.. but so far in our implementation we are still trying to figure out how to get context variables added to our lifecycle metrics. While it should be possible, our developers broke lifecycle when they tried (we're using React Native), and we haven't had a lot of time to investigate this much, so it got put on hold.

 

Part of my concern over what is the "right" solution, is that on web, the Instance of Campaigns is available to correlate to the actual page view.. whereas on mobile app, it's either on the page view (but not the first hit of the visit) or it's on the first hit (lifecycle) but then the campaign is only the attributed data and not the instance. So there's lots of considerations...

 

I wish I could merge the lifecycle metrics into the first page and get the best of both worlds.