Hi Arun,
Thanks for your response. Trying to give you some more perspective here.
1. The marketing channel eVar (context data) and s.campaign(context data) both fires with the clickthrough trackaction (event). Both are set to expire after 14 days and it has last touch attribution.
2. In Adobe Mobile Services, there is no way to set the 'Standard' Campaign variable which would feed the tracking code report. Hence, s.campaign is fired as a context data variable and then processing rule is used. Processing rule: If s.campaign(context data) is set, then overwrite the value of Campaign with s.campaign(context data)'.
3. I am not sure, if the order of the processing rule is messing up things here. Should this processing rule sit at the top of the list ?
4. When I pull up the data feeds, I see that the tracking code from previous channel persists. For example in the same visit:
- I come through email-->marketing channel eVar= email; tracking code= EML_XYZ;
- Then I come through Affiliate and purchase a product---> tracking code SHOULD BE 'AFF01_ABC'. But, we see that the previous tracking code persists. i.e. marketing channel eVar= affiliate; tracking code= 'EML_XYZ'. (Note: when I look into Charles, the right marketing channel with its corresponding tracking code fires. Nothing looks wrong there).
If I want to look at the order level, I find that even though I come from affiliate, the whole order gets attributed to the tracking code 'EML_XYZ' from email.
5. Should we fire the default campaign variable (how v0 fires for site) and change the processing rule accordingly?
Best,
Sree