URL Structures have specific orders for this, and is the definition of a query-string and a hash.  For a query-string to truly exist in good URL format, it would need to be before the hash.  Once you hit the "#" symbol in URL structures, that denotes the start of the hash and you've already passed t...

Events need the same type of set/no-set logic based on the value that is available to sprops and evars within the "Set Variables" action block.With variables, as it works today, if eVar2 is set to a data element that returns an empty string - it will not set the variable or send the info within the ...

Hi laetizia_2018​Crashes are always a different record than the other activity. (think of a crash as a whole new trackAction or s.tl call).  You're initial thought process is correct about enabling the "backdate option" -> the goal is to make that record of a crash part of the previous session.  In ...

There really isn't too much difference in most applications between doing a does not exist (include), and an exists (exclude) condition.  But when you start nesting conditions in your segmentation it's good to have both options (not to mention some people can conceptualize one function better than t...

Hello Frank,You are correct that the two examples leave you with VERY different data.  I'll try to break it down working from the inter-most aspect of the segment and working outward.  The main aspect of this comes up all the time when I review other's reporting or during training sessions, I'd even...

There's no hard rules for when to use an sprop vs an evar, and most of the information you'd find by googling is based on old reporting (i.e. not counting the new functionality in Analysis Workspace).The old rule of thumb was pretty much:  "sprops if you need the classic pathing reports" , "evars if...

Hey MktgCloudUser,I'm going to guess a bold assumption here, but I think it's likely the issue: "Is that a Core - Custom Code Action Block?"  If it is, then hooray we've found the issue!  If not, just ignore this long post Unfortunately, using a custom code action in this manner will not work for th...

From official documentation standpoint, yes I believe that's your only option (checking for the existence of turbine, basically).I would avoid '_satellite._container' , just from a general practice standpoint.

The short answer is 'no, you don't need to use an sprop' .  As a general rule-of-thumb, you're doing things correctly by collection a custom event (sign in), and then collecting one or many eVars in order to break it down (sub-domain).

There's a few different things you could use.  Personally I love ' _satellite.property.name ' because it returns the name of the Launch Property directly.However, just according to the official launch documentation, you could use _satellite.buildInfo ._satellite.buildInfo has various pieces of infor...