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 happenseven 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.

Thecontent 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.

HTML Content

HTML Content defines what content appears inside of a landing page version.

Attributes:

Name	Type	Description
content	string	The content that will be embedded within the `<body>` tag.
plan	object	The plan associated with the landing page version. If not defined, it will be inferred from the landing page.
discount	object	The discounts to apply to all signups generated by the landing page version. If not defined, it will be inferred from the landing page.