Avatar

Correct answer by
Employee

Here is an example of a deep link with context data:

app://home/promo?a.deeplink.id=test-deep-link1&a.launch.campaign.trackingcode=promo1&a.launch.campaign.source=promo1source&a.launch.campaign.medium=promo1medium

It looks to me like your structure is OK. For debugging, mobile hits are sent using POST so you need to make sure your debugger can see those hits. To see this data in reports, use Analysis Workspace and drag the Launch Name dimension to a freeform table. You should have instances of test-deep-link1.

Mobile Services also maps the other context data in the example deep link to dimensions, filter the dimension list by "launch" and you'll see them.

View solution in original post