Create your first Page

Create a personalized landing page for one prospect and get its shareable link. This walkthrough uses the Landit dashboard and a CSV containing one contact.

A template supplies the Page’s design and reusable copy. An enrichment groups the contacts you submit together. Landit processes each contact separately to create its personalized Page.

Before you begin

You need a Landit account, access to a template, and a LinkedIn person-profile URL for a contact you are authorized to process.

This walkthrough starts with one contact; the same CSV workflow supports a larger prospect list. A custom domain is optional for this first walkthrough. If your workspace has already configured one, make sure it serves Pages successfully over HTTPS before sharing its links.

1. Complete workspace setup

Open Setup in Landit. The checklist separates shared workspace setup from your individual profile.

If you own the workspace, complete Company profile: fetch the company’s LinkedIn profile, then confirm the company name, website, and logo. Complete Your profile by fetching your LinkedIn profile and checking your picture, first name, last name, and job title.

Once the company profile is ready, the workspace owner can select Start setup. Landit builds the Knowledge Base first and then creates the first template. These stages run in the background. Wait for the template stage to finish before using that generated template.

If you are a teammate, complete your own profile. Ask the workspace owner to finish shared setup and make an appropriate template available to you.

If setup fails, the owner can use Retry failed stage. Earlier completed stages remain complete. Review the reported problem before retrying.

2. Choose your template

Open Templates and choose a design for your campaign. You can explore its layout in the preview and use the AI conversation to customize the style or call to action. Template previews use sample prospect values; a generated Page uses your contact’s information.

For your first run, choose a template whose required information you can supply. If it references prompt variables, you need matching prompt definitions in your own account, including when a teammate owns the template. Understand variables explains the different sources.

Changes to a live template can affect existing Pages that use it. The editing guide explains how template changes appear on existing Pages.

3. Prepare a CSV

Export a comma-separated CSV with a header row and one contact. It must contain the exact, case-sensitive header linkedin_url. Use a LinkedIn person profile URL.

This illustrates the file structure. Replace the example URL with your contact’s real profile before uploading:

linkedin_url,campaign_note
https://www.linkedin.com/in/replace-with-your-contact,"A short note for this campaign"

campaign_note illustrates an additional column. Include it when your template uses {{campaign_note}}; use your template’s actual input fields for other columns. LinkedIn system fields such as {{linkedin.first_name}} are populated from the prospect profile rather than mapped from this CSV.

Keep the .csv filename extension lowercase. Save the file as UTF-8 and retain quotation marks around values containing commas.

4. Create an enrichment

Open Enrichments and create a new enrichment. Give it a recognizable name, such as First Page — October review, then select Choose template.

Select your chosen template and continue with Upload contacts. Choose your CSV, then select Match columns.

On the matching screen, map each template input to the CSV column that should supply its value. For example, map campaign_note to the campaign_note column when the template contains that input. Choose the column that contains the value you want to use for each input.

When ready, select Create enrichment pages. Processing starts in the background.

5. Retrieve the result

Return to Enrichments to follow the batch. When it is ready, select Download to retrieve the results CSV.

The output includes:

Column	Meaning
`url`	Shareable Page URL for a successful contact.
`error`	Failure reason for a contact that could not produce a Page.
`justlandit_job_title`	Enriched job title, when available.
`justlandit_company`	Enriched company name, when available.
`justlandit_years_at_company_in_month`	Estimated tenure expressed in months, when available.
`justlandit_picture_url`	Prospect image URL, when an image is attached.

Pages become available as processing completes. Follow individual Page statuses for ready links while the rest of the batch continues.

A completed batch can contain failed contacts. Check url and error for each row before using the file for outreach.

Open the returned Page URL to see the personalized result. If you would like a different style, layout, or call to action, you can refine the template through its AI conversation.

Share the Page link through your normal outreach workflow. Downloading the results CSV gives you the links; sending messages and CRM writeback are separate actions.

Public Pages expire two calendar months after creation. After expiry, a Page redirects to the workspace’s saved company website when one is available; otherwise it is unavailable. Plan campaigns with that lifetime in mind.

Troubleshooting

What you see	What to check
No available template	Finish workspace template generation or ask its owner to share a template with your workspace.
Missing `linkedin_url` warning	Check the header’s exact spelling and case, and confirm the file is a comma-separated CSV.
A contact fails	Read its `error` value. Check the person-profile URL, required prompt definitions, and available profile data before creating another run.
Batch remains in progress	Follow the individual Page statuses for completed results. If it stays unresolved, give your Landit contact the enrichment name and observed error.
Text is blank	Check the variable’s source. A template preview does not generate prompt-variable text.

Next step

Connect your custom domain to share Pages under your company’s hostname, or learn how variables work before adapting your template.