> For the complete documentation index, see [llms.txt](https://helps.ptengine.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helps.ptengine.com/en/faq/experience-edit/editor-not-opening.md).

# Editor won't open

If the Experience editor fails to open after entering a URL, one of the following is usually the cause. Work through the list below to identify and fix the issue.

1. Tracking tag not installed correctly
2. Page requires login
3. Page doesn't allow URL parameters
4. Page loads too slowly
5. Browser extension is active (e.g., Ghostery)
6. Iframe embedding is blocked
7. PV or UU limit has been reached

***

## Is the tracking tag installed correctly?

If the tag is missing, or the tag SID doesn't match the project ID, the editor won't open. Make sure the correct tag is installed on the page.

For installation instructions, see [Tracking tag setup](/en/faq/tag-and-domain.md).

***

## Does the page require login?

If the target page requires authentication, log in first in a separate tab and keep that session active before opening the editor.

Example: Opening the Insight Data Center page in the editor (a page that requires login)\
<https://www.ptengine.jp/app/********/insight/datacenter/overview>

Steps:

1. Open the target page in another tab in the same browser and log in. Keep the tab open and logged in.\\
2. Create a new campaign, enter the page URL, and open the editor.\\
3. The editor should now open successfully.\\

***

## Does the page allow URL parameters?

When the editor opens, Ptengine appends parameters to the target page URL. If the page is configured to block URL parameters, the editor won't load correctly. Update the page to allow parameter appending.

***

## Is the page slow to load?

If the page takes too long to load, the editor's verification timeout may be exceeded. Open the page in another tab first, wait for it to fully load, then try opening the editor again.

***

## Is a browser extension active?

Extensions like Ghostery can block the tracking tag from loading, which prevents the editor from opening. Disable the extension and restart your browser.

***

## Is Iframe embedding blocked?

Experience opens the editor by embedding an Iframe in your page. If your site blocks Iframe embedding, the editor won't open. Update your site's configuration to allow Iframes.

***

## Has the PV or UU limit been reached?

Once the PV or UU limit is reached, campaign creation and editing are restricted, and the editor becomes unavailable. Wait for the limit to reset or upgrade your plan to increase the limit.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://helps.ptengine.com/en/faq/experience-edit/editor-not-opening.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
