不及格的自定义链接部分的SiteCatalyst EVAR值 [英] Some SiteCatalyst eVar values not passing in Custom Link

问题描述

我现在面临一个疯狂的事了的SiteCatalyst自定义链接（内部）要求
我通过下面的code触发一个s.tl（）：

I'm facing a crazy matter with a SiteCatalyst Custom Link (internal) request.
I'm firing an s.tl() through the code below:

var s_custom = s_gi("report-suite");
s_custom.linkTrackVars = "eVar76,events,list3";
s_custom.linkTrackEvents = "event87";
s_custom.events = "event87";
s_custom.eVar76 = "value";
s_custom.list3 = "option1,option2";
s_custom.tl(this, 'o', 'link name');

该问题涉及的 eVar76 ，其价值不包括在该请求，即使s_customTrackerObject包含它。事实上，如果我检查的对象，我觉得它。
这种奇怪​​的似乎影响只是高号eVars，像eVar76，77，80，99等，不会降低的。
更换eVar76与eVar55，56或60，为前，是导致在值通常包含在请求师范行为。
这是不依赖于eVars实存，或激活，在报表包这是预期的，因为没有preliminar调用，以便检查设定，或启用，eVars在该报告套件作出的Adobe服务器。

这是一个非常愚蠢的行为，逼着我来代替用另一个所需EVAR。
我只想补充一点，这个自定义链接是一个页面加载ppared $ P $（DOM准备）在Adobe DTM规则，但我想，没有特别的设置应以做要修复它。
这是第一次，一个SC变量不包括在请求符合预期。
非常感谢对我的支持。

The issue concerns the eVar76, whose value is not included in the request, even if the "s_custom" TrackerObject contains it. In fact, if I inspect that object I find it.
This strange seems to affect just "high" number eVars, like eVar76, 77, 80, 99 and so on, not lower ones.
Replacing eVar76 with eVar55, 56 or 60, for ex, is resulting in a normale behaviour where values are normally included in requests.
This is not depending on eVars existance, or activation, in the report suite and this is expected because no preliminar calls are made to Adobe server in order to check the set, or enabled, eVars in that report suite.

This is a very silly behaviour forcing me to replace the desired eVar with another one.
I just add that this Custom Link is prepared by a Page-load (DOM ready) rule in the Adobe DTM, but I suppose that no particular setting should be done in order to fix it.
This is the first time that an SC variable is not included in request as expected.
Thanks so much for supporting me.

推荐答案

核心的Adobe Analytics（分析）库code建立请求字符串与循环查找事件/ eVars最多可用最大。土坯分析只在最近，以适应这种增加，更新到核心AppMeasurement库code的由膨胀为100〜1000和eVars事件从75至二百五十〇分之一百，所以。

The core Adobe Analytics library code builds the request string with a loop that looks for events/eVars up to the max available. Adobe Analytics only recently expanded events from 100 to 1000 and eVars from 75 to 100/250, so in order to accommodate this increase, an update to the core AppMeasurement library code was made.

注意：虽然的Adobe一直在更新旧ħ库旁边AppMeasurement，他们做的没有的更新旧ħ库，以适应这种增长。因此，为了跟踪 eVar76 +和 event101 + JavaScript中的变量（如 s.eVar76 ='foobar的'），则必须升级到最新AppMeasurement库。

Note: Although Adobe has been making updates to the Legacy H library alongside AppMeasurement, they did not update the Legacy H library to accommodate this increase. So, in order to track eVar76+ and event101+ within javascript as the variable (e.g. s.eVar76='foobar'), you must upgrade to the latest AppMeasurement library.

另外，如果你使用的是旧版H.23 +库可以代替填充它作为一个的 contextData 变量然后将其映射到事件/ EVAR /道具的处理规则（如取值.contextData ['eVar76'] ='foobar的'，然后在处理规则，你就必须如如果[（contextdata）eVar76] [设置]，然后覆盖[eVar76]以[（contextdata）eVar76] ）

Alternatively, if you are using Legacy H.23+ library you can instead populate it as a contextData variable and then map it to the event/eVar/prop in a processing rule (e.g. s.contextData['eVar76']='foobar' and then in processing rule you'd have e.g. if [(contextdata) eVar76] [is set] then overwrite [eVar76] with [(contextdata) eVar76])

参考：的https://marketing.adobe.com/resources/help/en_US/sc/implement/evars_events.html

这篇关于不及格的自定义链接部分的SiteCatalyst EVAR值的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！