Custom pages are displayed to your contacts when they perform one of 8 actions:
-
Subscribe successfully
-
Fail to subscribe successfully
-
Unsubscribe successfully
-
Fail to unsubscribe successfully
-
Confirm a subscription successfully
-
Fail to confirm a subscription successfully
-
Successfully request the next message in sequence
-
Fail to successfully request the next message in sequence
The following items in arpReach have custom page settings and the software will use them in the following precedence order:
-
Tracking tag custom pages
-
Subscription form custom pages
-
Autoresponder custom pages
-
Default system pages
Example 1:
A contact subscribes via a subscription form that has a tracking tag in its settings and that tracking tag has custom pages defined in its settings, then the tracking tag’s custom pages will be used for that contact.
Example 2:
A contact subscribes via a subscription form that has no tracking tag assigned to it but the subscription form has custom pages defined in its settings – the form’s custom pages will be used for that contact.
Example 3:
A contact subscribes by email to an autoresponder that has custom pages defined in its settings. Those custom pages will be used for that contact.
Example 4:
A contact subscribes by email to an autoresponder that has no custom pages defined in its settings. The system default pages will be used for that contact.