Mapping Default page(Page Name) dimension for trackAction Calls in apps

[aguseranalytics]

Hi Team,

We had a use case where pageView(custom event) and pageViews(by default metrics) numbers were not matching, because one of the probable reasons was, for few of the link click calls are going as trackState calls in apps therefore changed them to trackAction calls. Now, wanted to set the mapping of by default page variable in processing rules for apps for those trackAction calls via processing rules. Is this possible? Though Adobe itself stricks out the pagename value for link tracking or track Action calls is there any other way around. Please add in if there are any possible alternates.

Thanks in Advance!!

[SamuelPaulPeter]

No — you cannot map or force the default Page Name for trackAction (link) calls using processing rules. This is by design.

Why this happens

• In apps, trackState = page view → Page Name is valid

• trackAction = link event → Adobe intentionally strips Page Name

• Processing rules cannot override this behavior

So pageView (default metric) ≠ custom pageView events when actions are used.

What you can do instead

Use a custom dimension for “context page”

• Pass the current page/screen name in a custom eVar with trackAction

• Report on that eVar instead of Page Name for action-based flows

Convert key actions back to trackState

• If the interaction represents a screen/view change, it should be a trackState, not trackAction

Accept the model difference

• trackState = navigation

• trackAction = interaction
  Trying to make actions behave like page views will always cause mismatches

[Sumit-Kumar]

Just to add to the above,

to match custom pageviews PV (eventX) with default PageViews PV metric fire your custom event(pageviews) only on trackState calls(if doing via processing rules then Set eventX(pageviews) only when pagename  is set ), not on trackAction. This keeps both numbers aligned.

PVs won't increment for trackAction. If you want your custom event(for pageviews) to match default PVs, trigger it only on trackState.