> For the complete documentation index, see [llms.txt](https://docs.iadvize.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.iadvize.dev/use-cases/visitor-experience/authenticated-messaging/web-client-side-implementation/brief-timeline-of-the-integration-process.md).

# Brief timeline of the integration process

There are 4 main steps:

1. Brand creates and shares its public key as described in the documentation
2. Brand implements backend and frontend logics as described in the documentation
3. If Brand plans on launching the authenticated messaging on web but wants to keep Mobile SDK on simple mode, then we need to activate the flag hybrid mode on the iAdvize side
4. When those implementations are ready, iAdvize saves the Brand's public key in its database and activates the authentication


---

# 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://docs.iadvize.dev/use-cases/visitor-experience/authenticated-messaging/web-client-side-implementation/brief-timeline-of-the-integration-process.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.