s.apl in adobe analytics implementation vs Web SDK
Thanks for the above. I am trying to implement the setup hoping that it will be used for CJA (this use case is being considered).
I guess the question is whether to use the direct mapping
xdm._experience.analytics.event101to200.event108.id = (function anon() {
if (window._dl.instruction) {
var reference = Bootstrapper.data.resolve(60352);
var timeTaken = Bootstrapper.data.resolve(60389);
var instructionType = Bootstrapper.data.resolve(67043);
if (timeTaken > 0) return timeTaken + ":" + reference;
}
})();
OR
push everything as is in adobe currently into data._adobe.analytics properties.
@Jennifer_Dungan if I understand correctly, you are implying that the CJA requires direct mapping ?
HI @Franc_G
tbh, lately I am only using the second approach. The schema Adobe came up with to fill the AA object is an example how you can completely overengineer stuff.
So, with the Web SDK "Update Variable" action, you can define many things like with the old App Measurement interface, BUT you can also have a piece of custom code which lets you define and work with your dedicated "s" object.
content.__adobe = content.__adobe || { };
content.__adobe.analytics = content.__adobe.analytics || { };
let s = content.__adobe.analytics;
s.prop99 = "hello";
s.eVar10 = "world";
s.events = "event10";
// not more s.linkTrackVars or s.linkTrackEvents
My approach is
- create a Web SDK data variable for Analytics
- have a central rule with a Web SDK "update variable" that triggers on my page view AND interaction events that first clears existing data and sets the commonly to be sent data
- in my page view / interaction rules
- have an Web SDK "update variable" action that sets the event-specific data
- have a Web SDK "send event" action that sends the Web SDK variable as data
Cheers from Switzerland!
Hi @Franc_G
you can download the source of the plugin here https://experienceleague.adobe.com/en/docs/analytics/implementation/vars/plugins/apl
and with a tiny adjustment adapt it to e.g. work on your _satellite instance.
I typically do that in a library loaded event custom code.
Instead of function apl, just do a _satellite.apl = function ... (essentially paste the whole block).
and use _satellite.apl() instead of s.apl()
works like a charm
Cheers from Switzerland!
@bjoern__koth thanks for the above. If I understand it correctly, you are suggesting to load the apl plugin as custom code (as part of alloy.js base code) ? There is a custom code section, so we can put it in there. We have another property available, so will put it in there (see screenshot provided).
Question - I am changing the execution context in here - function declaration vs expression. Anything to watch out for ? Thanks
No, I am basically creating a functionality outside of the Analytics/WebSDK instance that can be reused everywhere.
The code itself has no depencies to AppMeasurement or the Adobe world.
If you want to not have any plugin dependencies, you can also write your own helper function
const apl = (list, item, delimiter) => {
if (typeof list !== "undefined" && typeof list !== "string") {
_satellite.logger.debug(">>> apl: list is of an unexpected type, ", list);
return item;
}
list = list || "";
delimiter = delimiter || ",";
// If the list is empty, return the item
if (list === "") {
return item;
} else {
list = list.split(delimiter);
if (!list.includes(item)) {
list.push(item);
}
return list.join(delimiter);
}
}
// testing
let list = "";
list = apl(list, "foo");
list = apl(list, "bar");
// 'foo,bar'
But as @Jennifer_Dungan mentioned, you can probably also just make your life easy and use her one-liner.
I just reuse the _satellite.apl every now and then in different other custom code locations.
Cheers from Switzerland!
Related Conversations
