---
title: "VL TVE Activate 01 Module"
slug: "vl-tve-activate-01-module"
updated: 2026-09-03T17:51:29Z
published: 2026-09-03T17:51:29Z
canonical: "docs.viewlift.com/vl-tve-activate-01-module"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.viewlift.com/llms.txt
> Use this file to discover all available pages before exploring further.

# VL TVE Activate 01 Module

## Introduction

**VL TVE Activate 01** is a System Screen module in **Template Builder**. It powers the TVE **device activation** page — the place where a customer enters the code shown on a TV or OTT device so that device can use the same TV provider access as their account.

On the website, this experience typically lives at `/tveactivate`. The customer enters an activation code, then chooses a TV provider (when required) to finish linking the device.

This article explains how to create the TVE Activate page in Template Builder, configure **VL TVE Activate 01**, publish it, and verify the experience on the web.

## Purpose

The purpose of this article is to help you:

- Create a **TVE Activate** System Screen in Template Builder
- Add and configure the **VL TVE Activate 01** module
- Edit activation copy, Roku options, errors, and brand color
- Understand what customers see when they activate a TVE device on the **website**
- Publish and verify the live TVE Activate page

## Scope

This article covers:

- Creating a System Screen page for TVE device activation in **Template Builder**
- Adding **VL TVE Activate 01** to the page layout
- Module settings: Roku and QR options, Localization, Errors, and Brand
- How TVE Activate appears on the **website**, including sign-in and Choose a Provider

It does not cover:

- **VL TVE 01** (TV provider connect at `/tve`)
- **VL Link Your Account / Activate Device** (account-to-device linking that is not this TVE Activate module)
- Enabling TVE or configuring TV provider credentials in AppCMS
- **VL Authentication 01** / **VL Authentication 02** as the main sign-in page (except how activation sends unsigned customers to sign in)

## Prerequisites

Before you begin, ensure you have:

- Access to **Template Builder** for your site
- Access to **ViewLift Tools** / AppCMS to confirm **TVE** is enabled and TV providers are configured
- A test activation code from a TV or OTT device (or your usual TVE test device)
- Copy ready: web title, subtitle, placeholder, Activate button, tooltip, and retry / session error text

> **Example used in this article** Throughout the steps below we use a TVE Activate page named **TVE Activate** at path `/tveactivate`. Replace the sample values with your own.

---

## TVE Activate flow overview (website)

The flowchart below shows the typical customer journey on the **website** when **VL TVE Activate 01** is published at `/tveactivate`.

![image (6).png](https://cdn.document360.io/15e0c142-c823-4c77-a8e8-9d32ca937982/Images/Documentation/image%20(6)(2).png)

**Notes**

- Customers often arrive from a TV or OTT device that displays a code, or from a deep link such as `/tveactivate?code=YOURCODE`.
- The page chrome includes **Back** and a close control.
- Unsigned customers who continue activation are sent to Authentication. After sign-in they return to `/tveactivate` (with the code in the URL when it was stored).
- **Choose a Provider** tiles come from **AppCMS TVE settings**, matched to providers available through TV provider authentication.
- After a successful provider step, the customer typically goes to the **homepage**. A Roku box activation can go to a thank-you page instead.
- If **Activate Roku Device** is on, or the URL includes `device=roku_box`, the site treats the session as a Roku activation.

---

## Step 1: Open Template Builder

1. Log into **ViewLift Tools**.
2. Open **AppCMS → Edit Template Builder** (or open Template Builder for your site from your usual entry point).
3. Confirm you are on the correct site and language (if localization is enabled, use the language selector on the Template Builder home screen before editing page copy).

![tb-home.png](https://cdn.document360.io/15e0c142-c823-4c77-a8e8-9d32ca937982/Images/Documentation/tb-home(7).png) *Template Builder home. From here you create pages and open System Screens.*

---

## Step 2: Create the TVE Activate System Screen

The TVE Activate page must be a **System Screen** so that **VL TVE Activate 01** is available in the module picker.

1. In Template Builder, go to **Pages**.
2. Select **+ ADD NEW** (or **Create a New Page**).
3. Enter **New Page Name**: `TVE Activate` (or your preferred name).
4. In **New Page Type * Developers Only**, select **System Screen**.
5. Optionally set **Target Language (If localized Page)** if you are creating a language-specific TVE Activate page.
6. Select **CREATE**.

### Set the page path

1. On **Page Settings**, set the page path to `/tveactivate` (recommended).
2. Confirm the page type is **System Screen**.
3. Save page settings if prompted.

![Image](https://cdn.document360.io/15e0c142-c823-4c77-a8e8-9d32ca937982/Images/Documentation/image-E6HQFRK4.png) *Page Settings. Set the path to `/tveactivate` so TV device links and post-login return URLs resolve correctly.*

> **Tip:** Keep `/tveactivate` consistent. Device deep links can include a code, for example `/tveactivate?code=YOURCODE`. Connecting a provider from a browser or app (without a device code) uses **VL TVE 01** at `/tve`.

---

## Step 3: Add VL TVE Activate 01 to the layout

1. Open the TVE Activate page.
2. Select **Edit Layout**.
3. Select **Add a New Module**.
4. Because the page is a System Screen, the picker shows **system** modules.
5. Search for or select **VL TVE Activate 01**.
6. Insert the module into the page layout.

![Image](https://cdn.document360.io/15e0c142-c823-4c77-a8e8-9d32ca937982/Images/Documentation/image-JKRTBH5O.png) *Edit Layout → Add a New Module. Search for and insert **VL TVE Activate 01**.*

![Image](https://cdn.document360.io/15e0c142-c823-4c77-a8e8-9d32ca937982/Images/Documentation/image-HRK99DDD.png) *TVE Activate System Screen layout with **VL TVE Activate 01** placed on the page.*

System Screens typically use a single primary system module. Avoid stacking unrelated content trays on this page.

---

## Step 4: Configure activation options

Open the **VL TVE Activate 01** module settings. These fields sit above Localization.

| Field | Description | Default example |
| --- | --- | --- |
| **Activate Roku Device** | Treat this page as a Roku activation session. The website also treats `?device=roku_box` as Roku. | Off |
| **Activate TVE (Web) title** | Web form headline in Template Builder. | `Activate Device` |
| **Activate TVE (Web) subTitle** | Supporting line under the web headline. | `Have activation code? Enter it below to enjoy content today!` |
| **Authetication Session Error** | Message when the provider session cannot continue (this is the field name in Template Builder). | *(empty — the website can show a generic error if this is blank)* |
| **Retry CTA Label** | Button on the provider-step error state. | *(empty — the website uses `Retry` if this is blank)* |
| **Activate Device Url** | Device activation URL you can store on the module. | *(empty)* |
| **Toggle QR Image** | Show or hide the QR image on device screens that use a QR option. | Off |

![Screenshot 2026-09-03 at 11.18.13 PM.png](https://cdn.document360.io/15e0c142-c823-4c77-a8e8-9d32ca937982/Images/Documentation/Screenshot%202026-09-03%20at%2011.18.13%E2%80%AFPM.png) ![Image](https://cdn.document360.io/15e0c142-c823-4c77-a8e8-9d32ca937982/Images/Documentation/Screenshot%202026-09-03%20at%2011.18.47%E2%80%AFPM.png) ***Activate Roku Device**, web title and subtitle, session error, Retry, Activate Device Url, and Toggle QR Image.*

On the **website** code-entry form, customers see the headline **Activate Device** (default), **Activate TVE (Web) subTitle**, the code field, tooltip, and **Activate**. **Retry CTA Label** and **Authetication Session Error** appear after a provider-session error, not on the first form.

---

## Step 5: Configure Localization

The Localization block includes additional titles and device-screen copy.

| Label | What it controls | Default example |
| --- | --- | --- |
| **Activate Device Title** | Device / activation title. | `Activate Device` |
| **Activation Code Description** | Instructions for entering the code on a device screen. | `Sign in or create an account, then enter the code: When connected, this page automatically updates.` |
| **Go To Label** | “Go to” prefix used with the activation URL on device screens. | `Go to` |
| **Get New Code CTA** | Request a new device code. | `Get New Code` |
| **Option Label** | Divider between code entry and QR (for example **OR**). | `OR` |
| **QR Code Title** | QR section heading. | `Scan QR code` |
| **QR Code Description** | QR section instructions. | `Use your camera app or QR code reader on your mobile device.Make sure the QR code is clearly visible on your device’s screen. When connected, this page automatically updates.` |
| **Device Code Fetch Error** | When a new device code cannot be loaded. | `Error in fetching code. Please try again later.` |
| **Input Box Placeholder Text** | Placeholder in the code field. | `Enter Code` |
| **Processing Text** | In-progress message where the activation flow shows a processing state. | `Processing` |
| **Activation Success Message Text** | Success message after activation completes (where that state is shown). | *(empty)* |
| **Activate** | Submit button on the web form. | `Activate` |
| **Case Sensitve Tooltip Text** | Tooltip next to the code field (this is the field name in Template Builder). | `This code is case sensitive` |

The **website** form uses **Input Box Placeholder Text**, **Activate**, **Case Sensitve Tooltip Text**, and **Activate TVE (Web) subTitle**. Device-oriented lines (Go To, Get New Code, QR title and description) are for activation screens that show those elements.

---

## Step 6: Configure Errors

Expand **Errors**.

| Label | When it is used | Default example |
| --- | --- | --- |
| **Cross Country Error** | Phone number is not allowed in the customer’s region. | `This phone number is not allowed to use in this region` |
| **Default error** | General processing failure. | `There was an error processing your request.` |
| **SignIn/ SignUp error** | No account found for the email. | `Sorry, we can't find an account with this email address. Please enter a registered email address and try again.` |
| **Facebook** | Facebook sign-in failed. | `Facebook login failed` |
| **google** | Google sign-in failed. | `Google login failed` |
| **Amazon Code Fetch Error** | Amazon code could not be loaded. | `Error in fetching code from amazon. Please try again later.` |
| **Amazon Login Error** | Amazon account configuration failed. | `Error in getting configuration from amazon account. Please try again later.` |
| **Password Length Error** | Password length is outside the allowed range. | `Password should be between 5 and 50 characters` |
| **Incorrect email/password** | Email or password is wrong. | `Your email or password is not correct. Please try again.` |
| **Name validation** | Name length is invalid. | `Name should contain minimum 3 characters & maximum 100 characters` |
| **Email Not Exist** | No user for the email. | `Failed to find user with the provided email.` |
| **Email Already Linked** | Email is already linked to another account. | `This email address is already linked to an existing account. Please login using the account.` |
| **Email Verification Failed** | Email is not valid. | `Email address is NOT valid. Please check your email and use the valid one. If you still get this error reach out to customer support.` |
| **Password Not Valid** | Password does not meet length rules. | `Password should contain minimum 5 & maximum 50 characters` |
| **Device Limit Exceeded** | Too many devices on the subscription. | `You have exceeded the maximum number of devices allowed for your subscription. Please log out of one or more devices` |
| **Phone Not Valid** | Phone number format is invalid. | `Phone Number is Not Valid. Please Enter a Valid Phone Number` |
| **Phone Already Linked** | Phone is already linked to another account. | `This Phone Number is Already Linked to an Existing Account.` |
| **Verify OTP Failed** | OTP is incorrect. | `OTP IS NOT CORRECT. PLEASE ENTER THE CORRECT OTP` |
| **Send OTP Failed** | OTP could not be sent. | `Sending OTP to your Number has failed. Please try again using a different number` |
| **Phone Not Linked** | Phone is not linked to an account. | `This Phone Number is not Linked to any account` |
| **Invalid Request Params** | Request could not be processed. | `Error Processing Request` |

On the **website** provider step, a failed session uses **Authetication Session Error** (or a generic error if that field is empty) and **Retry CTA Label**. Sign-in during activation uses your published Authentication page; keep matching sign-in error copy there as well.

---

## Step 7: Configure Brand

Expand **Brand**.

| Setting | Default (example) | Purpose |
| --- | --- | --- |
| **MVPD Background Color** | `#FFFFFF` | Background of each provider tile on Choose a Provider. |

Match this color to **VL TVE 01** so connect and activate feel like one product.

---

## Step 8: Save and publish the TVE Activate page

1. Save the module settings.
2. Review the page layout once more.
3. **Publish** the TVE Activate System Screen.

Until the page is published, apps and web will not show your latest TVE Activate configuration.

Changes can take several minutes to appear because of caching. To verify sooner, use a private window, another browser, or clear cookies and cache.

If unsigned customers must sign in during activation, also publish an Authentication page (see **VL Authentication 01**) at the path your site uses for sign-in (typically `/authentication`).

---

## Step 9: How it looks on the website

After publish, open your site’s TVE Activate URL, for example:

`https://www.example.com/tveactivate`

### Activation form

Customers usually see:

- **Back** and a close control in the flow chrome
- Headline **Activate Device** (default)
- **Activate TVE (Web) subTitle**
- Code field with **Input Box Placeholder Text**
- Tooltip with **Case Sensitve Tooltip Text**
- **Activate**

![Image](https://cdn.document360.io/15e0c142-c823-4c77-a8e8-9d32ca937982/Images/Documentation/Screenshot%202026-09-03%20at%2011.19.27%E2%80%AFPM.png) *Website `/tveactivate` form with title, code field, tooltip, and Activate.*

### Signed-out customer

1. The customer can open `/tveactivate` and type a code.
2. Selecting **Activate** sends them to Authentication when a signed-in session is required.
3. After sign-in they return to `/tveactivate` (with `?code=` when the code was stored).
4. If they opened `/tveactivate?code=YOURCODE` while signed out, the code is stored for that return trip.

### Signed-in customer

1. Enter a code and select **Activate**, or open `/tveactivate?code=YOURCODE` so the code is filled and the flow continues.
2. The page loads available TV providers and shows **Choose a Provider**.
3. Provider tiles use logos from **AppCMS TVE settings** and **MVPD Background Color**.
4. Selecting a provider opens that TV provider’s authentication experience.
5. On success, the customer typically goes to the **homepage**.
6. If the provider session cannot continue, the page shows **Authetication Session Error** (or a generic error) and **Retry**.

![Image](https://cdn.document360.io/15e0c142-c823-4c77-a8e8-9d32ca937982/Images/Documentation/image-J4JRXKBE.png) *Choose a Provider after a code is submitted, with TV provider logos.*

### Roku and other device variants

| Setup | What the customer sees |
| --- | --- |
| **Activate Roku Device** is on, or the URL includes `device=roku_box` | The site treats the visit as a Roku activation. After provider authentication, the customer can go to a thank-you page instead of the homepage. |
| Site TVE setup uses a checkout step | A signed-in customer who still needs a plan can be sent to checkout after the activation code is present. |
| Customer already has a connected TV provider and a valid device code | Device activation can complete and send the customer to the homepage. |

---

## Verification checklist

- TVE Activate page exists as a **System Screen**
- Page path is `/tveactivate`
- **VL TVE Activate 01** is on the layout
- TVE is enabled in AppCMS and TV providers are configured
- Web subtitle, placeholder, Activate, and tooltip copy are reviewed
- Retry and session error copy are reviewed
- **MVPD Background Color** matches the site
- **Activate Roku Device** is on only if this page is for Roku activation
- Page is **published**
- Signed-out customers who continue activation are sent to Authentication, then back
- Signed-in customers can enter a code, choose a provider, and finish (or see Retry)
- `/tveactivate?code=` prefills the code
- Authentication at `/authentication` (or your site’s sign-in path) is published

---

## Troubleshooting

| Problem | What to check |
| --- | --- |
| **VL TVE Activate 01** is not in the module list | Confirm the page type is **System Screen**. |
| Page path is wrong | Open Page Settings and set path to `/tveactivate`. |
| Customer is sent to Authentication | Activation continues after a signed-in session. Publish Authentication and complete sign-in. |
| Provider list is empty | Enable providers in AppCMS TVE settings and confirm TVE authentication is configured for the site. |
| A specific provider is missing | Confirm it is in AppCMS TVE settings and available through TV provider authentication for that customer. |
| Retry appears after choosing a provider | Review **Authetication Session Error** and **Retry CTA Label**. Confirm the activation code is still valid. |
| Labels do not change on the site | Save module settings, publish the page, and allow cache to clear. For localization, edit copy in the correct language. |
| Customer expected `/tve` instead | `/tve` is **VL TVE 01** (connect a provider). This page is device activation at `/tveactivate`. |
| Roku customers go to the wrong page | Confirm **Activate Roku Device** and whether the device URL includes `device=roku_box`. |
| QR or “Go to” copy never appears on the website form | Those Localization fields are for device screens that show QR / URL instructions. The website form is title, code, tooltip, and Activate. |

---

## Best Practices

- **Use one TVE Activate System Screen** at `/tveactivate`.
- **Keep `/tve` and `/tveactivate` as separate pages** — connect vs device activate.
- **Enable TVE and providers in AppCMS** before you expect Choose a Provider to fill.
- **Publish Authentication** so unsigned customers can return with their code.
- **Turn on Activate Roku Device only** on the page you use for Roku activation.
- **Localize** subtitle, placeholder, Activate, tooltip, and errors when the site has multiple live languages.
- **Test signed-out, signed-in, deep-link code, and Retry** before launch.
- **Publish after every meaningful change** — draft System Screens do not update production.

---

## FAQs

**Q. What page type should I use for VL TVE Activate 01?** **System Screen**. Set the path to `/tveactivate`.

**Q. How is this different from VL TVE 01?** **VL TVE 01** is the TV provider **connect** page (`/tve`). **VL TVE Activate 01** is the **device activation** page (`/tveactivate`), where the customer enters a code from a TV or OTT device.

**Q. How is this different from VL Link Your Account / Activate Device?** That is a separate System Screen module for linking a device to an account. Use **VL TVE Activate 01** when the device is activating **TVE** with a provider code.

**Q. Must the customer be signed in?** They can open the form signed out. Continuing activation typically requires sign-in, then a return to `/tveactivate`.

**Q. Can I pass the code in the URL?** Yes. `/tveactivate?code=YOURCODE` fills the code and continues the flow.

**Q. Where does the provider list come from?** On the website, from **AppCMS TVE settings**, matched to providers available through TV provider authentication.

**Q. Does this page process subscription payment?** No. It activates a TVE device. If the site still requires a plan, the customer can be sent to checkout.

**Q. Why are some field names misspelled?** **Authetication Session Error** and **Case Sensitve Tooltip Text** are the field names in Template Builder.

---

## Important Information

- **VL TVE Activate 01** must be placed on a **System Screen** at `/tveactivate`.
- This page is **device activation**. Provider connect without a device code uses **VL TVE 01** at `/tve`.
- Continuing activation typically requires a **signed-in** customer. Sign-in uses your Authentication page.
- The website provider picker uses **AppCMS TVE provider settings**.
- Create the page, add the module, configure copy and colors, then **publish**.
- Cache can delay frontend updates by several minutes.

---

## Glossary

| Term | Definition |
| --- | --- |
| TVE Activate | System Screen module for entering a TV / OTT device activation code. |
| System Screen | Template Builder page type used for sign-in, TVE, checkout, and other system flows. |
| Activation code | Code shown on a TV or OTT device and entered on `/tveactivate`. |
| Choose a Provider | Screen where the customer selects a TV provider after submitting a code. |
| MVPD | TV provider (pay-TV operator) shown as a tile on Choose a Provider. |
| VL TVE 01 | Separate module for connecting a TV provider at `/tve`. |

---

## Contact Support

If you need help beyond this article, contact the ViewLift support team.

- **Email:** techsupport@viewlift.com
- **Phone (US):** +1-800-859-0420
- **Phone (UK):** +44-203-014-8921

Support hours: B2C requests are handled Monday to Friday. B2B support is available 24/7.

---