# Advanced Integration: Embed the Process Into Your Own Pages

The basic version of integration involves redirecting the user to the address returned by the conversation creation API.
This solution is simple, effective, and does not require additional integration work beyond defining the page to which
the user will be redirected after the process is completed.

Authologic also provides the option to embed the verification process within your website. Unlike simple redirection,
this solution requires you to take into account the following:

- this type of integration requires additional work,
- including the process within your website may require rebuilding the navigation,
- it should be taken into account that some verification methods require opening their own window,
- the webSDK code should be systematically updated

<warning>

Sites using WebSDK must be registered with Authologic. After providing Authologic with the website address,
you will receive the widget ID (`widgetId`) necessary to run the integration. An invalid **widget ID** will result
in a browser [CORS](https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS) error. For testing purposes you can
use `development_only` as the value of the `widgetId`. It will disable security and will only work in
the **sandbox environment**.

</warning>

<warning>

Conversation creation should also set the `layoutUrl` field pointing to the page where the webSDK is embedded.
Sometimes, there is a need to move process to another site and after the process is completed, Authologic must know
where to redirect the user.

</warning>

Integration may look slightly different depending on the technologies you use:

<card-group>
<card title="Javascript" to="/docs/websdk/js">

Integration directly into JavaScript.

</card>

<card title="React" to="/docs/websdk/react">

Integration within React applications.

</card>

<card title="Vue.js" to="/docs/websdk/vuejs">

Integration within the VueJS application.

</card>

<card title="Angular" to="/docs/websdk/angular">

Integration within the Angular application.

</card>
</card-group>

<note>

Despite our sincere intentions, it is difficult to create perfect technical documentation.
If you have an idea on how to improve this documentation, or you have trouble understanding any section,
please email us at [tech-support@authologic.com](mailto:tech-support@authologic.com)

</note>