First, for "general" new vs repeat users, I guess this depends on your definition of "new" and "repeat"... if "all-time" new, then Adobe has some pre-made segments called "First Time Visits" and "Return Visits" (based on the all time visit number being 1 or greater than 1).   However, if you want so...

I should add, I haven't switched to XDM Streams yet, but like passing products directly in the old ACP method, you should be able to pass the products string (without needing to map it using processing rules).   Technically, you should be able to set ALL your values directly into the XDM Stream with...

Hi,    If you are using XDM Streams you can set it.. but if you are using the old ACP SDK, and setting data using context variables and mapping, s.products actually has to be sent through the request directly using &&products=[entire formatted products string], and if you are passing events with you...

I would check Admin > Report Suites > (choose suite) > Edit Settings > Conversion > Conversion Variables   The first item is your campaign variable (s.campaign, v0, Tracking Code, etc)   Check your Expire After here?

Hi,   So for Campaign. I noticed your processing rules are used query string s_cid. That may be what you are using, most people just use cid, but if it is s_cid you should be good i.e. do you URLs have ?s_cid=xxxxx_xxxxx_xxxx or ?cid=xxxxx_xxxxx_xxxx   If your param is really cid, that would cause s...

It really does.... just for a test.. can you try something else? just to see if the cookie gets properly set? Maybe try a prop and another eVar (something that should always be there)... 

So Marketing Channels and Campaigns are slightly different... Campaign only looks at your query strings, whereas Marketing Channel can look at many different dimensions (including Campaign, or just looking at the query strings directly - which I would recommend doing).   By default, Marketing Channe...

Hmm on the surface, this looks fine...    The only thing I can think of is your eVar2 being explicitly set? Or is it maintaining a value from a previous page (I assume not since it's called "page id", so I would expect that to be set for every page)   There should be no difference between maintainin...

This sounds like my example above then... an attribution issue....   In addition to Page B failing to be set, if the form submission happens before the page load (i.e. if you are using Window Loaded, and there is any resource preventing the page from completing to load... like an ad or a third party...

Silly question, but in your calculation I assume you are taking into account the visitor identification, and only looking at the "page view rows" (and not actions performed on the same page - I think post_pagename should cover this)? And I assume you are also taking into account the exclude_hit to m...