Hi Jennifer, thanks for you comment. I actually already wrote an adapted
version of it, that works now and since I either way can't use the
version of Adobe (which will get fixed soon maybe) for the new WebSDK
implementation, since it is connected with the App Measurement, I will
go with my own version. Will you create a (global) client care ticket or
is it something that I have to do with my "clients specific client
Hi Jennifer, sorry, I did not explain my approach very well, so let my
try again. 1. I have this issue with a client who actually uses the "out
of the box" plugin (without any changes to code) via Adobe Launch. There
I found the issue. To reproduce it, I set up the following on a test
website: 1. Installing App Measurement and instantiate it. (as written
in the documentation) When trying it out I get an error that
"this.c_r(..) is not defined (since its part of the app measurement .. I
Hi all, I currently have a client, where I migrate the old
appMeasurement-Implementation to the new WebSDK Implementation. They
currently use s.getValOnce(..).
Since this needs the App Measurement to work, I rewrote the plugin a bit
and I think the cookies times are not set correctly with this plugin.
When executing this line: s.getValOnce(s.eVar1,"TestCookie-10Days",10)
// Results in D=pageNa...
Hi People, I'm working on an Adobe Target Implementation for the WebSDK.
The delivery of different mboxes/decisionScopes works fine for me. When
doing reporting directly in Adobe Target (no a4t) I want to confirm,
that every time I do "sendEvent" (like in the following code) : 1. The
response will contain all activities of the local-mbox ("click-mbox")
where the conditions set in Adobe Target are true (of course only in the
target environment, that is configured in the data stream) 2.
Hi there, I have a rather specific question when it comes to activating
BackdateSessionInfo. "When the hits are enabled, the Adobe SDK backdates
the session info hit to 1 second after the final hit in the previous
session. This means that crash and session data will correlate with the
correct date on which they occurred. One side effect is that the SDK
might create a visit for the backdated hit. One hit is backdated on
every new launch of the application."-Source: