Redirects allow you to use multiple URLs and map back to a single destination.
Similar to landing pages, redirects also embed the concept of Referrals . Referral cookies are set before the redirect happens, meaning you can redirect to an external host and the last touch cookie will still be present when the visitor comes back to your site.
Landing page / reverse proxy path collision
If an enabled redirect and an enabled landing page are both defined for the same path, the redirect will have precedence
If an enabled redirect has a path prefix that matches an enabled reverse proxy, the reverse proxy will have precedence
Attributes:
| Name | Type | Description |
|---|---|---|
| path | uri | The path to identify the redirect. Must be unique for the application. |
| target | uri | The target URL to which to redirect the traffic. Can be a relative or absolute endpoint. |
| enabled | boolean | If this redirect is currently enabled. Disabled redirects will be ignored. Redirects are automatically enabled upon upsert. |
| referral_methodology | string | The Methodology used to merge referral parameters defined in the landing page vs supplied in the URL. |
| referral | object | The default Referral object associated with the landing page version. |
| created_at | integer | Unix timestamp of when the redirect was created (in seconds since the Unix epoch). |
| updated_at | integer | Unix timestamp of when the redirect was last updated (in seconds since the Unix epoch). |