> For the complete documentation index, see [llms.txt](https://knowledge-base.letsgetdigital.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge-base.letsgetdigital.com/the-admin-panel/navigation/virtual-platform/external-navigation.md).

# External navigation (Virtual event)

This page describes how to setup external navigation with a custom user reference.

It is also possible to provide references for external navigation links in order to make it possible to recognise a user in external/own software.

This can be done by adding the variables`lgd_user_id` or `lgd_user_code` in the url parameters.

The software then automatically replaces these values with the corresponding values of the user. These values correspond to the values known in the [API](https://docs.letsgetdigital.com/).

The table below shows the variable as it can be used in the link and what value it corresponds to from the API.

| Variable in URL | API endpoint | Endpoint field |
| --------------- | ------------ | -------------- |
| `lgd_user_id`   | User         | `id`           |
| `lgd_user_code` | User         | `code`         |

### Examples

Add the following link to the navigation items: \
`https://www.letsgetdigital.com?your_id=lgd_user_id&your_code=lgd_user_code`

If a user with id `27` and code `TESTINGCODE123` will click on the link, the following link will be opened:\
`https://www.letsgetdigital.com?your_id=27&your_code=d5f3ef4396e64221092ec573dfe35b`

{% hint style="info" %}
The `lgd_user_code`is sent as an md5 hash of the `customer_id` and `code` field with an indent in between: 

```
md5(customer_id-code)
```

{% endhint %}


---

# 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://knowledge-base.letsgetdigital.com/the-admin-panel/navigation/virtual-platform/external-navigation.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.