Adobe plug-in: pt

The pt plug-in executes a function or method on a list of Analytics variables. For example, you can selectively run the clearVars method on several variables without manually calling the method each time. Several other plug-ins depend on this code to run correctly. This plug-in is not necessary if you have no need to run a specific function on more than one Analytics variable at a time, or if you’re not using any dependent plug-ins.

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 pt
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: pt v2.01 */
 s.pt=function(l,de,cf,fa){if(l&&this[cf]){l=l.split(de||",");de=l.length;for(var e,c=0;c<de;c++)if(e=this[cf](l[c],fa))return e}};
/******************************************** END CODE TO DEPLOY ********************************************/

Use the plug-in

The pt method uses the following arguments:

• l (required, string): A list of variables that the function contained in the cf argument can execute against.
• de (optional, string): The delimiter that separates the list of variables in the l argument. Defaults to a comma (,).
• cf (required, string): The name of the callback function contained in the AppMeasurement object to be called against each of the variables contained in the l argument.
• fa (optional, string): If the function in the cf argument calls for additional arguments when it runs, include them here. Defaults to undefined.

Calling this method returns a value if the callback function (in the cf argument) returns a value.

Example Calls

Example #1

The following code is part of the getQueryParam plug-in. It runs the getParameterValue helper function against each of the key-value pairs that are contained in the URL’s querystring (fullQueryString). In other to extract each key-value pair, the fullQueryString must be delimited and split out by an ampersand “&” character. The parameterKey refers to the query string parameter that the plug-in is specifically trying to extract from the query string

returnValue = s.pt(fullQueryString, "&", "getParameterValue", parameterKey)

The above line is a shortcut for running code that resembles the following:

var returnValue = "",
  parameters = fullQueryString.split("&"),
  parametersLength = parameters.length;
for(var i = 0; i < parametersLength; i++)
{
  returnValue = s.getParameterValue(parameters[i], parameterKey);
  if(returnValue !== "") break;
}

Version History

2.01 (September 24, 2019)

• Minor code changes to reduce overall size

2.0 (April 17, 2018)

• Point release (recompiled, smaller code size).
• Added support for both H-code and AppMeasurement.

1.0 (23 September 2013)

• Initial release.