Every site implementation is different...
If you are using the Adobe Client Data Layer, that your developers are pushing events (with relevant data) to that data layer, when the lightbox is opened, you would get your developers to push that information to the data layer... then you would create a...
Oh, I should also add, if you are using WebSDK or sending data to CJA, the same applies... you have control over what triggers a page view, and what triggers an action...
Note, this is a setting that needs to be done per person.. it is not a company wide setting. As in, you cannot control this for "all users"... it is each user's responsibility to change this setting.
With Launch, you can choose to trigger an action (s.tl) or a page view (s.t) on any trigger. If you consider your lightbox to be significant enough that you want to track it as a Page View, then you should have no problem doing so.
There is no "magic switch" to turn on, if that is what you are ta...
Hi @davidl55903031,
Yep, I just confirmed the same... even though the Click URL is captured, the data doesn't appear to make it to the Processing Rules to be usable in a rule.
On a page with an oid value, I tried pulling up s_objectID in the console.. I wasn't able to get it to work, it just cam...
Unfortunately, this particular display isn't possible in Adobe Analytics Workspaces... You can only have a single breakdown at each level.
You will either have to do a breakdown of a breakdown... or create some sort of concatenation of all your UTMs into a single string.
Yes, I know that concat...
Well, first, your VISITOR segment is returning all data for the users that in the reporting period saw page A then B (this includes visits before and after this sequence.. the sequence may not even be in the same visit... they may have seen Page A on Feb 1 and Page B on Feb 26, and all page views, f...
Oh, yes... it would be a pretty big security hole to get all the parameter names without authenticating yourself, lol....
But, once you do get those values downloaded, they should remain for that suite (even if your login times out)... since "Show post processed hits" hasn't worked for over a year...
In the debugger, try using the "Refresh Report Suite Details":
For Launch, maybe a hard refresh should fix the issue (I am assuming you had Launch open, made some changes and you aren't seeing them reflected yet... so it's probably just a cache). Those don't change often, so it wouldn't be doin...
Yes, I was thinking the same thing... I believe the missing a.x.web.webpagedetails.url(Context Data) is the likely cuprit.
@Josh__Stephens I don't think you need the "c" in this. C stands for "Context Data", which Adobe already has identified with the "(Context Data)" at the end of the name... Wh...