Happy to help

Here is the recommended short term solution, intended to be used as part of the alloy onBeforeEventSend callback. I've just implemented something based on this and it has alleviated the extra pageviews for now, throwing the "phantom" hits into the Custom Links reporthttps://gist.github.com/jfkhoury/...

Hi there... Yeah I did confirm it was the Target calls generating the extra pageviews. I tried setting tinkering with the pagename, both by ensuring that xdm.web.webPageDetails.name was undefined and even setting up a processing rule to delete Pagename, neither of which was successful unfortunately....

Hello gang... We've been running with the WebSDK for a bit now and all has seemed just fine. We've been impressed with the performance as well as the relative ease of implementation. Note that we use the NPM module directly, incorporated into our front-end build process. Throughout testing as well a...

@dwrightI hereby nominate you a genius!    For some reason I completely missed that transactionID was not one of the auto-mapped variables... And sure enough when I started poking around in Processing Rules just now, I spot this item in the list:  a.x.commerce.order.payments.0.transactionid(Context ...

That is perhaps correct for purchaseID, but not transactionID. purchaseID and transactionID are not the same 

Hi gang, I'm working through the final details in our transition to the WebSDK for data collection and I have encountered a snag... It seems that when transactionID is specified in the XDM JSON, that value never seems to get forwarded to Analytics. I know this because 1) Our TransactionID processing...

Hi there, thank you for replying  I am using 2.6.4, but this isn't so much an issue with Response Tokens but rather Activities with "empty" Experiences, or Experiences with no modifications (custom code or VEC, etc). We use such Experiences for our control groups or default content. Using at.js, if ...

Count me in!

And.... I just figured it out. I've been testing with a "dummy" A/B test that doesn't actually do anything. Both variations are simply default content. When requested via getOffer() with at.js, Target does in fact select my Activity and deliver it (as seen in the responseTokens), however with alloy ...