Landingpage Editor Extension

Please find below a series of recent updates to the Landing Page Editor, aimed at making this powerful Maileon tool even more efficient and user-friendly. These extensions are designed to simplify workflows and speed up the creation process.

1. Direct editing options in the URL

 A personalised URL can contain key information about a page using the following GET parameters (case insensitive): contactid and checksum.  

Example: contactid=1234&checksum=123123123 

This information can be extended using query parameters, which are added after a question mark (?) and structured as key-value pairs separated by an equal sign (=) (fig.1). 

If you have created separate tabs in the editor for your landing page, navigate directly to the tab in the URL.  Start editing the landing page by adding the name of the tab in the URL supplemented by the question mark (?) as key-value pairs separated by an equal sign (=).

Once you name the tab, the landing page will use it as the starting point (fig. 2).

Note: After the equals sign, enter the name of the tab in all lowercase, without accents, and use hyphens instead of spaces.

2. Personalising Unsubscribe Pages Using the      Mailing ID URL Parameter 

Did you know that unsubscribe pages support a customisable parameter called the mailing ID? When used in the URL, this parameter allows the system to attribute the unsubscribe action directly to a specific mailing.

By using the specified URL parameter (fig. 3), you can automatically insert the mailing ID into the link. When this link is included in mailings—such as in a standard footer—the system dynamically replaces the parameter with the correct mailing ID for each individual campaign.

Example: mailingId=123

3. Fallback values: Set default values via URL

If a contact field has no value in the system—for example, when a landing page is used as a profile modifier or simply as a subscriber form, and the field is blank by default—you can set default values for certain fields via the URL.

• After the first tilde (~), specify the type of field to which you want to apply a fallback value (e.g., a standard field).
• After the second tilde, define the specific field within that type (e.g., EMAIL or FULLNAME) to which the fallback should apply.

The format of these values follows this pattern:
fallback~type~fieldname=value

Possible values for the type:

– standard,
– custom,
– preferences,
– transaction.

Possible values for the fieldname:
-transactionType>transactionPropertyName,
-preferenceCategory###preferenceName,
– uppercase standard field names (EMAIL, FIRSTNAME, etc.),
– case sensitive custom field names.

The following example illustrates the pattern:
fallback ~ standard~EMAIL=max (fig. 4).

The value provided will act as the default and can be used across all types of customisation features. It behaves the same way as if the value came directly from a contact field. However, it will not overwrite any existing value already stored in the system—it only applies when no data has been previously entered for that field.

Note: Both the key and the value are case sensitive. If the field name or value contains special characters, they must be URL-encoded. This encoding is typically handled automatically by web browsers or by the Maileon system.

 

4. Embedding a Landing Page into a Website Using an iFrame

Embedding a landing page inside a website is possible using iFrame, which allows you to insert one web page into another. When the page is embedded in an iframe a number of events are available for the embedding top page. You can find examples for the data provided by these events below:

• Display of subscription events on the main page: This action displays both the data entered by the user and any hidden field values, such as data originating from Maileon that is embedded in the page.
• Navigation between the main page and the embedded landing page.
• OnResize: Enables dynamic page resizing. This action occurs each time the page loads.

For details, please see the official documentation for developers.

5. Meta Pixel Integration 

Similar to the Facebook Pixel, but interaction happens through an API. With this feature, the landing pages also support webhooks.

A webhook allows you to specify a web address (URL) that will receive data automatically when a specific event occurs. When triggered, the event sends relevant data from the page to the designated address in real time.

Please find this feature in the Landing Page Editor at Page settings ->
Analitycs -> Subscription Webhook-URL (fig. 5).

This option ensures that when a user subscribes, the contact information they previously provided is sent to the web address specified in the webhook.

It requires an external service (e.g., Zapier) — this enables automation in other systems, sending data to Facebook, launching ad campaigns, and more.

Note: Unique parameters at the end of the URL (e.g., campaign ID) can also be transmitted using this method.