Adobe plug-in: inList

The inList plug-in allows you to check if a value already exists within either a delimited string or a JavaScript array object. Several other plug-ins depend on the inList plug-in to work. This plug-in provides a distinct advantage over the JavaScript method indexOf() where you it does not match partial strings. For example, if you used this plug-in to check for "event2", it won’t match with a string containing "event25". This plug-in is not necessary if you don’t need to check for values in delimited strings or arrays, or if you want to use your own indexOf() logic.

Install the plug-in using the Adobe Experience Platform Launch extension

Adobe offers an extension that allows you to use most commonly-used plug-ins.

1. Log in to launch.adobe.com using your AdobeID credentials.
2. Click the desired property.
3. Go to the Extensions tab, then click on the Catalog button
4. Install and publish the Common Analytics Plugins extension
5. If you haven’t already, create a rule labeled “Initialize Plug-ins” with the following configuration:
   • Condition: None
   • Event: Core – Library Loaded (Page Top)
6. Add an action to the above rule with the following configuration:
   • Extension: Common Analytics Plugins
   • Action Type: Initialize inList
7. Save and publish the changes to the rule.

Install the plug-in using Launch custom code editor

If you do not want to use the plug-in extension, you can use the custom code editor.

1. Log in to launch.adobe.com using your AdobeID credentials.
2. Click on the desired property.
3. Go to the Extensions tab, then click the Configure button under the Adobe Analytics extension.
4. Expand the Configure tracking using custom code accordion, which reveals the Open Editor button.
5. Open the custom code editor and paste the plug-in code provided below into the edit window.
6. Save and publish the changes to the Analytics extension.

Install the plug-in using AppMeasurement

Copy and paste the following code anywhere in the AppMeasurement file after the Analytics tracking object is instantiated (using s_gi). Preserving comments and version numbers of the code in your implementation helps Adobe with troubleshooting any potential issues.

/******************************************* BEGIN CODE TO DEPLOY *******************************************/
/* Adobe Consulting Plugin: inList v2.1 */
s.inList=function(lv,vtc,d,cc){if("string"!==typeof vtc)return!1;if("string"===typeof lv)lv=lv.split(d||",");else if("object"!== typeof lv)return!1;d=0;for(var e=lv.length;d<e;d++)if(1==cc&&vtc===lv[d]||vtc.toLowerCase()===lv[d].toLowerCase())return!0;return!1};
/******************************************** END CODE TO DEPLOY ********************************************/

Use the plug-in

The inList method uses the following arguments:

• lv (required, string or array): A delimited list of values or a JavaScript array object to search
• vtc (required, string): The value to search for
• d (optional, string): The delimiter used to separate individual values in the lv argument. Defaults to a comma (,) when not set.
• cc (optional, boolean): If set to true, a case-sensitive check is made. If set to false or omitted, then a case-insensitive check is made. Defaults to false.

Calling this method returns true if it finds a match, and false if it does not find a match.

Example Calls

Example #1

If…

s.events="event22,event24";

…and the following code runs…

if(s.inList(s.events,"event22"))

…the conditional if statement will be true

Example #2

If…

s.events="event22,event24";

…and the following code runs…

if(s.inList(s.events,"event2"))

…the conditional if statement will be false because the inList call did not make an exact match between event2 and either of the delimited-values in s.events

Example #3

If…

s.events="event22,event24";

…and the following code runs…

if(!s.inList(s.events,"event23"))

…the conditional if statement will be true because the inList call did not make an exact match between event23 and either of the delimited-values in s.events (notice the “NOT” operator at the beginning of the inList variable call).

Example #4

If…

s.events = "event22,event23";

…and the following code runs…

if(s.inList(s.events,"EVenT23","",1))

…the conditional if statement will be false. Although this example isn’t practical, it demonstrates the need to use caution when using the case sensitive flag.

Example #5

If…

s.linkTrackVars = "events,eVar1";

…and the following code runs…

if(s.inList(s.linkTrackVars,"eVar1","|"))

…the conditional if statement will be false. The value of the d argument passed into the call (i.e. “|”) assumes that the individual values in s.linkTrackVars are delimited by a pipe character, whereas in reality, the values are delimited by a comma. In this case, the plug-in will try to make a match between the whole value of s.linkTrackVars (i.e. “events,eVar1”) and the value to look for (i.e. “eVar1”).

Version History

v2.1 (September 26, 2019)

• Added the option for the cc argument to not be a boolean. For example, 1 is a valid case check value.

v2.0 (April 17, 2018)

• Point release (recompiled, smaller code size).

v1.01 (September 27, 2017)

• Optimized code to reduce size

v1.0 (2009)

• Initial release.