That's really interesting.. I don't use flow diagrams much myself, so I hadn't noticed this... this looks like a deliberate decision from Adobe... not sure why... but I guess they figured IF you want to see pathing starting from X, you don't want to see the flows where users immediately exit? Which ...

There are multiple "endpoints" based on what you are trying to do...    https://developer.adobe.com/analytics-apis/docs/2.0/guides/endpoints/   I suspect you are trying to access the "Reporting API" endpoint https://developer.adobe.com/analytics-apis/docs/2.0/guides/endpoints/reports/     I haven't ...

Yes, if you have data that clearly identifies those UIDs into a few usable groups, Classifications would be a great solution.   The best part of classifications is that it can change retroactively... so if you make a mistake, or you need to re-classify a value as something else, you can do so.   Her...

Just to help expand on @bjoern__koth's answer, I'm going to add some examples.   First off, let's assume your campaign eVar is set to Visit expiry (I am also going to assume that you are using some code to split your values on the pipe, since you talk about "cntest" is isolation of the "sg" value)  ...

Unfortunately, Adobe only stores dimensions (props, eVars, lists, etc) as text... even the "numeric" designation you mentioned doesn't change how the values are stored, it really only opens up options for tracking.   For example, when an eVar is set, and the value persists, you don't necessarily kno...

Your web implementation is not JSON right now.... it's a string. The data layer is JSON, and your script is putting data into an array, then flattening that array into a string.

It should!    And since you have that, matching the format and values is all the more important. Differences could cause the regex to not work... it was probably those [ and { that were causing issues if your developers already started sending data in the JSON format causing issues.

Yes, though you might want to add a note to replace null value with "[na]" to match your web implementation.   Also, as per your screenshots, you are not yet segregating your web data... unless you are using classifications, in which case, the same classification logic will apply.

Yes, your developers are trying to send it as JSON... they have to convert it into a single string value. No [ or { or ] or } unless they are part of the literal text...   Like in your example, your "NA" we actually showing as "[na]", in that case, to match what you have from your website, you will ...

The 255 character limit is affecting your web traffic right now... eVars can only hold 255 characters... anything above that is truncated. The Database field on the Adobe server will not hold more than that.   Even if you are sending all the data to Adobe with Launch, I can absolutely guarantee that...