Navigate to the checkout page on your site and open the debugger bookmarklet. You'll see the variables that are firing on that page. If you don't see any checkout events, you'll know that there is an issue with your implementation that you'll want to resolve.

PageName has a limit of 100 bytes; pageURL actually has a limit of 255 bytes.

Hi,You may opt to use the JS plug-in getLoadTime to calculate the page load time and capture the value in the desired variable. Post which, you would be able to run breakdown report with Geo dimension such as City and get the desired data.

You are firing the event correctly i.e. the server call right after that action/success takes place. However, yes, the credit of the event give is by default on Linear basis and thus would be divided between all pages viewed within that Visit before that event was fired.This logic is in place so that you can see influence of each page towards any conversion.You should only require exact allocation, if you have same event firing on multiple location and you want to know which page is most popular...

That's correct. Whichever Visitor Identification method you choose to use, it must be consistent across all your sites/orgs.

Hi,Allocation mostly comes into picture for success/conversion events like commerce events (Order, Revenue etc.), custom success events etc.

Hello Christy, I like your approach because I'm not comfortable with putting it in Library Management so that I can keep my code most recent version. I'm working with a Single Page App, so i'm not sure if this will work. Something's not working correctly because I'm not seeing anything returned.Here's my data element custom code: /* * Plugin: getPreviousValue_v1.0 - return previous value of designated * variable (requires split utility) */ var s = _satellite.getToolsByType('sc')[0].getS(); s.get...

The unspecified value might be coming from bot traffic.... In that case you might want to set up a segment in workspace to filter out unspecified values.