Landing Page Versions

You can test different content, presentation, and offers for a landing page defined at a specific path. When the experiment is run, one of the versions will be selected for the visitor. This selection process happens even if only one version is defined for a given URL.

In this way, as you add versions in the future, previous visitors will still be pegged to the original version they were shown.

Each landing page will have a default version. The default version is always shown for any recognized bot (Google, etc). Known bot traffic is excluded from experiment / visitor data. This allows you to have confidence that the page that Google sees is the page you want Google to see.

Landing page versions inherit the HTML Header of the landing page. It is only the <body> content that is changed.

The content attribute of the landing page version object is not returned by default in any of the API calls outlined below. To return the HTML Content, you must append the URL query parameter content=true to the API call.

Attributes:

Name	Type	Description
id	string	V7 UUID generated when the version is created.
name	string	Human-readable name to identify this version.
enabled	boolean	Disabled versions will not be factored when running the experiment. Ergo, disabled versions will not be rendered. If all versions of the landing page are disabled for the requested path, the default landing page will be rendered.
default	boolean	If this is the default version for the landing page. Default versions cannot be disabled.
experiment_version	object	The experiment version object associated with the landing page version.
content	object	The HTML Content to be embedded into the landing page version.
created_at	integer	Unix timestamp of when the landing page version was created (in seconds since the Unix epoch).
updated_at	integer	Unix timestamp of when the landing page version was last updated (in seconds since the Unix epoch).