External Campaign ID Tracking in mobile app

[Lee_Lemen]

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 

[Jennifer_Dungan · Accepted solution]

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.

[aguseranalytics]

Hi @Jennifer_Dungan ,

Since I have also come across the same set of requirement if we can pass on the tracking code along with lifecycle metrices so that we don't loose the attribution. Is this only possible from the app developers?

Do we have any such approach from Launch side where we can set the using the Mobile Core extension. If not then what could be the approach to solve this?

Thanks in Advance.

[Jennifer_Dungan]

Hi, you shouldn't loose attribution if you pass it on the page, and not on the Lifecycle. Your Marketing Channel rules should be picking up the use of campaign variables whenever they are used (and not limited to the "first hit in the visit" - otherwise you will be ignoring all your cross channel attributions during a visit).

The Lifecycle metrics are generally very limited (as I said, there is no context variables being included... and with the newer AEP SDK, the lifecycle metrics is once again far more "automatic" than it was in the ACP version of the app). I don't think it's possible to add anything to the lifecycle, even with the developers involvement... and certainly no way to add it in Launch.

For the past 5 years, I've sent the campaign data on the page that was opened, and all my reporting has been working properly, with all the proper attributions...  and while I would love to have lifecycle metrics merged onto the first page view (even if just to help reduce server calls), this doesn't seem like it's likely to happen.