Macros for Listing Factors and Variations

The following high-level Factor and Variation listing macro allows you to loop over all Variations (including Site Variations and QuickChanges) that SiteSpect attempts to apply on the current page. Use at least one of the macros in the table below as the {fmt} parameter. Specify a delimiter using {delim}.

__SS_LISTVAR{fmt}{delim}

Macro	Data Type	Description
__SS_FID__	Integer	Factor ID. The Factor_ID listed in the URL when you are editing a Factor or the ID visible in the tooltip when you hover over the Factor on the Factor List.
__SS_ISCONTVAR__	Integer	Is a Control Variation. A value of 1 if the applied Variation is a control; otherwise, it’s 0.
__SS_NEWRATING__	Integer	New visit rating. The visitor's new Visit Rating from matching the Factor.
__SS_PRIORITY__	Integer	Factor priority. The evaluation sequence of the Factor.
__SS_VGID__	Integer	Variation Group ID. The VariationGroup_ID listed in Summary View when you are editing a Campaign in the New Builder or the ID visible in the tooltip when you hover over the Variation Group Edit button in the Old Builder.
__SS_VID__	Integer	Variation ID. The Variation_ID listed in the URL when you are editing a Variation or the ID visible in the tooltip when you hover over the Variation on the Factor list.
__SS_VNAME__	Alphanumeric, cleaned	Variation name. The name of the Variation.

Example for __SS_LISTVAR

To create a list of all Factors and Variations shown on a page, with the Factor and Variation name delimited by an equal sign, and each Factor and Variation pair delimited by a semicolon, use the following macro:

__SS_LISTVAR{__SS_FNAME__=__SS_VNAME__}{;}__

Or consider using ID's if there is risk of exceeding the a field character limit.

__SS_LISTVAR{__SS_VGID__:__SS_VID__}{;}__

If two Variations are shown on the page, the dynamically generated text look similar to the following:

Headline_Factor=Bigger_Font;Cart_Factor=Blue_Cart_Button

Note: __SS_LISTVAR{..}__ will output Variations that apply on a page regardless if the user is counted or not. For example, a Variation for a Client Side Variation that uses a JS Path will need to be applied even if the user has not yet matched the Path or been counted.