Configure the Landing Page Settings

Learn how to configure the domain settings for a Landing Page validation rule so to ensure that the everything works correctly when a user navigate to it from an ad. 

Note: Before you use the Landing Page validation rule, you must whitelist our IP addresses so we can access your site. Alternatively, you can provide a user agent that we can use. 

Please, also be aware that false requests may be sent to a third-party ad server/verification tool if you use click trackers in your landing page URL. 

When a user clicks on a tracking URL to a landing page, several things could not work as intended. Take a few examples: 

• The landing page does not exist. Maybe someone took it down, or you forgot to update the URL
• Because the URL has many redirects, a few parameters in the tracking link may be lost along the way
• There are no tracking requests from the page to your analytics tool, even after consenting to the cookies
• etc.

By default, a Landing Page validation rule checks that the domains of all the landing page exits - that the URL is valid. Additionally, you can add settings to check if the number of redirects exceeds a certain limit, if the query parameters don't conform with your taxonomy, or whether a request is sent to your analytics tool.

This validation works by simulating a user navigating to the landing page from your ads using a headless browser. To pass the validation, the landing page must return a 200 response when we check the HTTP response.

Overview

As mentioned, the Landing Page validation rule checks that landing pages work correctly, in terms of domain, number of redirects, query parameters, and configuration of third-party analytics tools.

This is configured by defining domain settings:

Limit to specific domains

It lets you define for which exact domains the configuration applies to. 

Set a maximum number of redirects

It lets you define the maximum number of redirects before arriving on the landing page. 

Set required query parameters

It lets you define which UTM query parameter(s) or CID code should be present in the URL when arriving on the landing page. 

Validate analytics tool

It lets you define which analytics tool and specific property ID/report suite should be receiving a tracking request. If your analytics tool is implemented via a cookie consent solution, you must include it in the configuration.

All additional settings for your landing page can be grouped by domains. See `Multiple domains and settings´.

Redirects

You can use redirect settings if you have limits for redirects you allow for your landing pages.

You can configure the rule to set the maximum allowed number of redirects. To pass the validation, the landing page must not exceed the number of redirects defined in this field.

Setting a limit for redirects

Start by enabling the toggle `Set maximum number of redirects´ under your domain settings. You are now presented with an input field where you can set the number of redirects you allow for your landing pages.

Required query parameters

If you always require certain query parameters on your landing pages, you can add them to the rule as well. 

An example would be if your landing pages for search campaigns always include `utm_medium=search´. To pass the validation, the landing page must contain the required query parameters defined in the rule.

Setting required query parameters

Start by enabling the toggle for `Set required parameters´ under your domain settings.

Click `Add parameter´ to get started with your first parameter.

In order to define a parameter, you must provide a parameter key and operator. Depending on your operator, you may need to add a value as well.

We will use this example URL to explain how you set up the parameters: https://www.accutics.com?utm_medium=search

Parameter key

The parameter key must be unique.

Operator

Possible operators are `equals´, `RegEx´, and `is set´:

• Use equal if the value of your key is static or if you use a predefined template in your ad platform that contains the same macros for all ads. 

• Use RegEx if the value of your key is dynamic but still holds a taxonomy, which you can write through a regular expression.

• Use is set if the actual value is subordinate as long as the key is set. 

Value

This field is where you set the actual value of the parameter key unless the selected operator is `is set´.

Validating your analytics tool

If all landing pages must send a page view tracking request to your analytics tool, you can add analytics tool details here. We support Google Analytics and Adobe Analytics as analytics tools, and when selecting either, you can add the desired property/report suite IDs for your accounts. By doing so, you control exactly where your data is sent. 

For Adobe Analytics we support the mapping of variable (eVar) and parameter key, so you can ensure that variables are sent correctly. For Google Analytics we only support Universal Analytics (UA) implementation.

Configuring your analytics tool

Start by enabling the toggle for `Validate analytics tool´ under your domain settings.

The first step is to select your analytics tool, and the following configuration differs depending on your selection.

Adobe Analytics

When selecting Adobe Analytics, you have the option to provide one or more report suite IDs. You can add multiple IDs by pressing Enter after pasting the ID in the field. 

When selecting Adobe Analytics, you can also match your variable (eVar) with your parameter key to ensure that the right data is collected in the right variable. 

You can only select parameter keys you have defined under `Set required query parameters´. If you have skipped this step, adding a new query parameter will prompt you to add and define it. After you have done so, it will appear both under `Set required query parameters´ and next to your variable.

Google Analytics (Universal Analytics)

When selecting Google Analytics, you have the option to provide one or more property IDs. You can add multiple IDs by pressing Enter after pasting the ID in the field.

Cookie consent

If your analytics tool also requires user consent before sending any tracking request, uncheck the ´No cookie consent solution´. This lets you define the consent cookie we should recreate to simulate a real user visiting your landing page and hence, check that the tracking request is sent to the analytics tool correctly.

If you use Cookiebot or Cookie Information, you can simply select it via the dropdown option field. 

If you use another cookie consent solution, you must select `Custom´ and provide the name and value of your cookie. Follow these steps to find your cookie name and value:

Multiple domains and settings

Whilst these settings might be identical across your ad platform, you may also experience the need to divide your settings based on domains, and that’s why you start by adding domain group settings. 

This means that if you own multiple domains with different settings, you can use the ´The limit to specific domains´ feature to narrow down settings based on grouped domains.

Limit to specific domains

This setting lets you define for which exact domains the configuration applies. If your requirements differ between different domains, you can add multiple domain settings and limit each configuration to specific domains.

Start by enabling the toggle for `Limit to specific domains´ under your domain settings.

You are now presented with an input field where you can add multiple domains by pressing Enter.

The domains you enter in this field are the domains to which your settings for redirects, query parameters, and the analytics tool should apply. If you have one domain associated with Google Analytics and another domain associated with Adobe Analytics, you must add two domain groups to your configuration.

From a technical point of view, once Accutics Validate has extracted the landing page from the ad platform, it matches the domain to all added domain groups to determine which settings it should check for.