Build a journey around your visitors.

Check your project before editing.

Pathline CMS works with an existing Pathline template project. The companion has no additional fee and does not install the template into a blank site.

1. Keep all five Pathline CMS collections: Funnels, Questions, Choices, Rules and Results.
2. Use a Framer plan with capacity for five collections. For a custom domain, the standard Pro plan accommodates this configuration; Basic's two collections do not. Check the current limits before buying hosting.
3. The person synchronizing changes needs code-asset editing permission. CMS content access alone is insufficient.
4. Use an unpublished copy while learning. Keep Live delivery off and use sample answers.

• Check Framer plans

Open the companion in your copy.

Open the Pathline CMS Marketplace listing below while signed into the Framer account that can edit your copy of the template.

1. Choose Open Plugin, then select your existing Pathline project. Do not choose New Project: a blank project does not contain the supplied collections and component.
2. In the companion, choose Check configuration. Confirm that its starting question and progression match your project. The supplied sample contains six questions, three rules and three results; your edited configuration can have different counts.
3. Use Questions to open the native CMS collection. After editing, switch the top-left CMS menu to Canvas, then reopen Pathline CMS from the listing and select the same project.
4. Choose Validate and sync to apply your edits. Wait for the Synced confirmation, then preview both the landing section and /consultation before publishing.

Missing collections usually mean the wrong project is open. Select your template copy instead of creating replacement collections in an unrelated site. Inside CMS, the companion can check configuration but cannot synchronize. Return to Canvas first. If synchronization is still unavailable, ask an editor with permission to edit this project's code assets.

• Open Pathline CMS on Framer Marketplace

Edit a question, then apply it.

Start by changing a question's Title in Pathline Questions. Keep its slug unchanged: slugs identify questions and choices, while titles are visitor-facing labels.

1. For single choice, use Type single and Maximum 1. Add answer options in Pathline Choices, select their parent Question and set their numeric Order.
2. For multiple choice, use Type multiple; Minimum and Maximum count selections. For Type text, they count trimmed characters. Give text a sensible Maximum, such as 800.
3. Each question needs one fallback destination: Next question or Next result, never both. Optional questions can be skipped when Minimum is 0.
4. Return to Canvas, open the companion and choose Check configuration. Fix reported errors, then choose Validate and sync. Preview the changed prompt in both placements.

Publishing CMS edits alone does not update the questionnaire. Validate and sync is required. An invalid configuration leaves the previously synchronized journey unchanged. The companion does not publish your site.

Send an answer down a different path.

Example: a visitor choosing My business should see the business question. Other visitors should follow the home path.

1. In Questions, set the first question's fallback to the residential question.
2. In Rules, select that first Question, Operator equals and the My business item in Match choice. Set Next question to the business question and assign Priority 10.
3. Give every rule on the same question a different numeric Priority. Lower numbers run first; the first matching rule wins. If none matches, the question's fallback runs.
4. Use includes for a selected multiple-choice option, contains for case-insensitive text, equals for exact text, or empty for a skipped optional answer. Text rules use Match text.
5. Synchronize and test both paths. Return to the first question and change the answer: later answers are cleared so the old branch cannot enter the new result.

Rules inspect the current question's answer. Conditions combining several previous answers and a visual flow editor are not included. Validation catches missing destinations, cycles and unreachable items.

Choose where and how the journey appears.

In Pathline Funnels, keep one live configuration and choose its starting question and Layout. Horizontal shows one active question; vertical shows completed answers followed by the active question. Future questions remain hidden in the interface.

1. Select each PathlineFunnel instance on the canvas. Presentation chooses Landing section or Dedicated page. Progression / Use CMS setting follows the collection; Horizontal or Vertical overrides it for that instance.
2. Keep the landing wrapper's Scroll section named direction, or update its /#direction CTA links together. The dedicated campaign route is /consultation.
3. Edit the landing's text, images and typography on the native canvas. Set the funnel accent in its property controls.
4. Edit Results to explain each recommendation and its contact CTA. The result is shown before the contact form. Connect the final questions or rules to the appropriate result.

Each placement has its own session. Moving to the dedicated page or reloading starts over. Hidden questions are still public website configuration; never store confidential information in the CMS.

Connect real contacts separately.

The template sends nothing in demo mode. Live delivery requires your own HTTPS receiver, privacy notice and any downstream email or CRM service. These services are not included.

1. Prepare a receiver accepting JSON POST and CORS OPTIONS requests from the actual preview and published origins. Keep secret credentials on the server.
2. Configure HTTPS endpoint and Privacy URL on each placement that should accept contacts. Enable Live delivery only for controlled staging tests first.
3. Use synthetic details such as test@example.invalid. Check the received result and visited answers, then test failure and retry. Do not send test inquiries to a real sales destination.
4. Verify on the published staging domain before accepting real leads. A 2xx response means the receiver accepted the request; it does not prove a later email or CRM action succeeded.

The request includes version, funnel, result, contact, answers and submissionId. Requests omit browser credentials, reject redirects and time out after 15 seconds. Your receiver must validate, store and deduplicate submissions; consult the supplied contact-delivery contract before implementation.

Resolve the next blocking step.

Use sample configuration when reporting a problem. Include your version, the error and the steps to reproduce it; omit visitor data, credentials and protected template links.

Understand the two data flows.

Pathline CMS reads questionnaire configuration and writes the validated configuration to a code asset in the open Framer project. It has no application-owned analytics, account service or external configuration server. Framer operates the editor and plugin platform under its own policies.

1. The website questionnaire keeps answers in memory for its current session. The companion does not collect visitor submissions or host a lead database.
2. With Live delivery enabled, the visitor's browser sends entered contact details and confirmed answers to the site owner's receiver. That owner must provide privacy information and operate the receiver.
3. The checklist below stores no persistent data. Its ticks reset on reload. Support email and Framer are separate services with their own data handling.