Kilkaya

summary official websites true false 162false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type developer integrations true false 160false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type false unhandled content type tracking service event support matrix overview of the supported events and their configuration true false 163,262false left unhandled content type false unhandled content type false unhandled content type false left unhandled content type false unhandled content type false unhandled content type false left unhandled content type false left unhandled content type false left unhandled content type purchases purchases and attributes attributes are not supported ( ) ( ) actions actions and views views contains special handling regarding url tracking more detailed information can be found below in the description of the event configuration for actions and views general structure in tracking config json tracking service key name in " tracking config json " is " kilkaya kilkaya " general structure { "kilkaya" { "eventsenabledbydefault" true, "viewsenabledbydefault" true, "purchasesenabledbydefault" false, "attributesenabledbydefault" false, "events" { // your configured list of events }, "views" { // your configured list of events }, "purchases" {}, "attributes" {} } } event configuration actions kilkaya supports action events action event "action event key" { "templates" { "title" "value of template", "type" "value of template", "section" "value of template" } } example "issue downloaded" { "templates" { "title" "value of template", "type" "value of template", "section" "value of template" } } kilkayas special behavior for url tracking as mentioned in the official documenation of kilkaya an action event must send the values for " url url " and " tourl tourl " both of them are added automatically in purple experience for the case that an action event will not change the view the value of "url" and "tourl" will be the same views kilkaya supports view events view event "view event key" { "templates" { "title" "value of template", "type" "value of template", "section" "value of template" } } example "storefront feed" { "templates" { "title" "value of template", "type" "value of template", "section" "value of template" } } kilkayas special behavior for url tracking as mentioned in the official documenation of kilkaya a view event must send the value for " url url " this is added automatically in purple experience purchases kilkaya does not support purchase events attributes kilkaya does not support attributes additional supported functionality no additional functionality is currently supported how to configure native purple app kilkaya does not provide any native integration web integration enable sdk kilkaya is not explicitly enabled if a valid configuration of kilkaya is present in the " experience config json ", the sdk is integrated into the html document structure in experience config json plugin configuration { "purple" { "analytics" { "kilkaya" { "configuration" { "cdnhost" "provided by kilkaya", "installationid" "provided by kilkaya" } } } } } consent management if you use one of the cmps supported by purple, you must specify the cmp specific vendor id for kilkaya, which you can get from your cmp frontend additionally, the iab vendor id for kilkaya can also be added structure in experience config json plugin configuration with consent { "purple" { "analytics" { "kilkaya" { "configuration" { "cdnhost" "provided by kilkaya", "installationid" "provided by kilkaya" }, "consent" { "vendorid" "", "iabvendorid" "" } } } } }