Setting eVar in one page and all it's click action

[shreyaDh2]

Hi,

I have a question regarding eVar capturing when moving from mobile App to Web View.

In our mobile app two pages Product Display Page(PDP) and Product Listing Page (PLP) will be converted to web view (The PDP and PLP running in website will be loaded inside mobile app). We want to capture App ID in these web view. So when moving from App to web view in query parameter APP ID will be passed. In Adobe Launch data element will be created for this app id. Now thing is that I want to create one rule which will capture appID  in eVar but this rule will trigger in both PLP and PDP page load and all the existing click action of PLP and PDP. So that I don't have to touch existing launch rules of these pages.

Please suggest what to do.

Thankyou.

[SSampsa · Accepted solution]

Hey!

I'll give it a shot, please let me know if I've misunderstood what you are looking for.

You have 2 rules (PDP and PLP), which both need to use the eVar with appID in it. AppID is passed on via URL query parameter and you have created a data element that captures this.

What you want is to have the eVar set, but done so that you don't add it to the existing rules, they should not be touched (personally I would just add this data element idirectly n those rules to the specific eVar, but there might be circumstances where this is not feasible).

If these are your criteria, my solution would be along these lines:

1. Create a new rule
2. Rule is set to have the same triggers as PDP and PLP rules, but higher priority (default is 50, so set priority e.g. to 40)
3. Rule runs the Analytics action to set variables and assigns data element to evar

That is it. The rule will run at the same triggers as PDP and PLP, but before them, set the evar and do nothing else. Original rules do not need to be modified.

Hopefully this helps to solve your problem.

[Sukrity_Wadhwa]

Hi @shreyaDh2,

Was the given solution helpful to resolve your query or do you still need more help here? Do let us know. In case the given solution was helpful, then kindly choose it as the 'Correct Reply'.

Thanks!

[DhivyaVinoth]

Hey, 

We had similar challenge while capturing parameters passed into a webview from mobile. One thing that helped us was using a global rule for URL based conditions and assigned a dedicated eVar for App ID.

Have you checked whether the APP ID is consistent across both PLP and PDP when opened through different journeys like deeplink. That could affect how you set the condition in Launch.