> For the complete documentation index, see [llms.txt](https://docs.ngsurvey.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ngsurvey.com/form-management/publish-deploy/website-intercepts/intercepts/intercept-layout.md).

# Intercept Layout

With intercept layout properties, you can fully control the appearance and on-screen positioning of each intercept. This allows you to seamlessly integrate intercepts into your website’s design and optimize the user experience.

* **`Style`**overrides the default style that is assigned to the survey, this allows you to set a custom style for each intercept and match the branding based on the visitors.
* **`Content size`**size of the intercept that is displayed to the visitor. The size will automatically shrink down and adapt if the visitors is using a mobile device. 
* **`Corners`**type of corners of the intercept.
* **`Shadows`** level of shadows of the intercept.
* **`Position`**position of the intercept on screen. If you want to fully center the intercept you can double click on the center icon.
* **`Button position`** if you have    
* **`CSS code`**enter any custom CSS that will be applied to your intercept you can use following CSS classes to customize your intercept.

```css
.ngs-survey__intercept
.ngs-survey__intercept-header {}
.ngs-survey__intercept-button {}
.ngs-survey__intercept-close {}
.ngs-survey__intercept-content {}
.ngs-survey__intercept-content-body {}
.ngs-survey__intercept-content-footer {}  
```

  


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.ngsurvey.com/form-management/publish-deploy/website-intercepts/intercepts/intercept-layout.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.