medium=Mobile-app but half of entry pages don't contain that parameter.

[MarkVictoria]

Can anyone help me understand this:

 

Entry pages that are segmented to contain: utm medium, but does not contain utm medium.  

 

 

[Imbalakumar]

Hi @MarkVictoria 

• prop variables in Adobe Analytics have a maximum length of 100 bytes. If your UTM URL is longer than 100 bytes, it will be truncated.
• Check the length of your UTM URL and ensure it's within the 100-byte limit. If it's too long, you may need to shorten it or use a more efficient URL encoding method

Refer this URL for understanding the limitation is s.prop1 - s.prop75 in AppMeasurement - https://experienceleague.adobe.com/en/docs/analytics/implementation/vars/page-vars/prop

Thanks,

Bala

[Jennifer_Dungan]

While yes, props have a max character limit of 100 characters, this is clearly not the case here... line number 3 is definitely NOT at 100 characters, and it's extremely rare that the truncation would occur perfectly lined up to stop at ".html"

So while good advice, this is not the reason behind the issue here.

[DanIMS1]

Hi @MarkVictoria,

Is your segment a hit based segment or is it a visit or visitor based segment?
If your segment is a visit or visitor based you will be looking at the entry page for any visit or visitor that has seen the  query parameter and value of  "utm_medium=mobile-app" at any point in their visit or user life time.

If you want to only see the entry pages that contain "UTM_medium=mobile-app", you should create a hit based segment where "utm_medium=mobile-app" is present. This will then ensure any pages you look at contained the parameter, if you then use this with the entries metric and your URL dimension you will get the report you need.

[Jennifer_Dungan · Accepted solution]

I agree, this looks like a attribution issue..

Also, the Entry Page may not be the best dimension to use here. "Entry" dimensions are simply the first value send to the dimension during the visit.. but that may not correlate to the the UTM usage, for example:

• Page 1 = https://www.domain.com/
• Page 2 = https://www.domain.com/section/x
• (user gets an email, and opens a promotion)
• Page 3 = https://www.domain.com/promo?utm_medium=email&utm_campaign=marketing_email

All three of these pages will have "https://www.domain.com/" as the "Entry Page".

You would be better off pairing Page URL with the UTM Medium (v49) Instance metric.

All eVars have an "Instance" metric... this is where the value is explicitly set, so even if the eVar has a Visit level expiry, only the hit where the utm_medium exists in the URL and is explicitly set in the tracking will trigger an Instance metric. This will be a much more accurate way to pull the data.

[MarkVictoria]

Jennifer, 

Thanks. Lots of useful thought starters.  I dragged the utm_medium directly over so it would be a hit-based segment.  

The mid-session email opening is a possibility by in my industry, likely an edge-case so I won't worry about that.  The use of 'instances' is a good suggestion.  

Thanks again! 

[Jennifer_Dungan]

You're welcome..

But if your eVar has a Visit level expiry, dragging it into the table that way still isn't enough.

Example:

• Page 1 (?utm_medium=socialmedia)
  • eVar1 explicitly set to "socialmedia"
  • Page View metric triggered
  • eVar1 Instance metric triggered
• Page 2
  • eVar1 not set, but due to visit level expiry the value of "socialmedia" persists
  • Page View metric triggered
  • eVar1 Instance metric not triggered
• Page 3
  • eVar1 not set, but due to visit level expiry the value of "socialmedia" persists
  • Page View metric triggered
  • eVar1 Instance metric not triggered
• Page 4 (within same visit, clicked on marketing email ?utm_medium=marketing)
  • eVar1 explicitly set to "marketing"
  • Page View metric triggered
  • eVar1 Instance metric triggered
• Page 5
  • eVar1 not set, but due to visit level expiry the value of "marketing" persists
  • Page View metric triggered
  • eVar1 Instance metric not triggered

In a table, this will result in:

		Page Views	eVar1 Instance
eVar1		5	2
	socialmedia	3	1
	marketing	2	1

A visit attributed eVar will maintain the value throughout the entire visit, or until a new value is set... the eVar Instance is what distinguishes an explicitly set value from a persisted value. A persisted value is still a "hit".