> For the complete documentation index, see [llms.txt](https://docs.dapta.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dapta.ai/dcal/share/your-booking-page.md).

# Your links and profile page

Understand your dCal links: the profile page that lists your events, one link per event, team pages and one-off invite links. Learn what each part of the address means, where to copy it, how to change

Everything you share from dCal is a link. Your guests open it on any device, with no account and nothing to install, pick a time and book. This page explains the links you have, what each part of the address means and where to copy them.

***

## The links you have

| Link                      | Address                                                     | Opens                                                                                                                                  |
| ------------------------- | ----------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------- |
| **Your profile page**     | `book.dcal.ai/{account code}/{handle}`                      | A page with your name, photo and the list of your visible events. This is what the dashboard calls **Your booking link**.              |
| **An event**              | `book.dcal.ai/{account code}/{handle}/{event slug}`         | The booking page of one event, straight to the calendar.                                                                               |
| **A team page**           | `book.dcal.ai/{account code}/team/{team slug}`              | The list of a team's events. See [Your team page](https://docs.dapta.ai/dcal/teams/team-page.md).                                      |
| **A team event**          | `book.dcal.ai/{account code}/team/{team slug}/{event slug}` | The booking page of one team event.                                                                                                    |
| **A one-off invite link** | `book.dcal.ai/booking/{code}`                               | A booking page that works for one booking, then stops. See [One-off invite links](https://docs.dapta.ai/dcal/events/one-off-links.md). |

For example, Jane Doe's profile page could be `https://book.dcal.ai/k7m2xq/jdoe`, and her intro call `https://book.dcal.ai/k7m2xq/jdoe/intro-call`.

Your booking links live on `book.dcal.ai`. Your dashboard and sign-in stay on `app.dcal.ai`. Booking links you shared earlier with `app.dcal.ai` in them keep working, one-off invite links included: they send guests to the same address on `book.dcal.ai`, with everything after it kept, UTM tags included.

***

## What each part means

| Part             | What it is                                                                                                                                                                                                                                                                                                              |
| ---------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Account code** | A six-character code for your workspace, for example `k7m2xq`. dCal creates it with the workspace, and everyone in the workspace shares it. Capital letters do not matter in it. If your workspace has a [custom link](https://docs.dapta.ai/dcal/share/custom-link.md), that word takes its place, for example `acme`. |
| **Handle**       | Who you are inside the workspace, for example `jdoe`. dCal makes it from your name the first time you sign in: your first initial and your last name, without accents, plus a number if someone in your workspace already has it. You can change it (see below).                                                        |
| **Event slug**   | The end of each event's address, for example `intro-call`. You set it on the event. See [Create an event](https://docs.dapta.ai/dcal/events/create-an-event.md).                                                                                                                                                        |

***

## Copy your links

**Step 1:** For your profile page, open **Home**. Once you have at least one visible event, the **Your booking link** box shows the address with **Copy** and **Open**. **Copy** puts it on your clipboard and flashes **Copied**.

**Step 2:** For one event, open **Events**. Each row has three icons on the right: **Open booking page**, **Copy link** and **Embed on your site**. Click **Copy link**: you see **Link copied.** The same icons sit at the top of the event's edit page.

<figure><img src="https://3835013762-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCy5rSNtQmtqYCGzJlNEB%2Fuploads%2Fgit-blob-6baed29d97cc3c9e9b97cfcb3b012610b4293ba5%2Fdcal-your-booking-page-01-event-row-icons.png?alt=media" alt="The Intro call row on the Events page with the visibility switch and the Open booking page, Copy link and Embed on your site icons, Copy link boxed"><figcaption><p>Every event row carries its own link. The second line shows the end of its address and its length.</p></figcaption></figure>

**Step 3:** For a team event, open **Teams**, open the team and use the same icons on the event's row. Team events also appear under **Team events** on the **Events** page.

You can also copy your profile link from **Settings** > **Booking Page**, in the **Your booking link** field.

***

## Your profile page

Your profile page is the one link that shows all your events. It carries your cover image and logo when you set them, your photo (or your initials), your name, your bio, and a card for each visible event with its title, description and length.

Where the link lands depends on your events and on two settings in **Settings** > **Booking Page**, under **Meetings**:

| Your setup                                                                                           | Your profile link opens                                                                    |
| ---------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------ |
| Several visible events                                                                               | Your profile, listing them.                                                                |
| Exactly one visible event                                                                            | That event directly, unless you tick **Always show my profile, even with one event type**. |
| **Show the landing page (list of events)** off, and an event chosen in **Send visitors directly to** | That event directly.                                                                       |

Adding `?landing=1` to the end of your profile link always shows the profile, whatever these settings say. The order of the events is the one you set under **Meetings**; without one, the shortest event comes first. See [Profile and layout](https://docs.dapta.ai/dcal/design/booking-page-studio.md).

> **⚠️ Note:** A hidden event is not on your profile, and its own link does not open. To let one person book a hidden event, send them a [one-off invite link](https://docs.dapta.ai/dcal/events/one-off-links.md).

***

## Change your handle

**Step 1:** Open **Settings**, then **Booking Page**. Under **Profile**, type the new handle in **Public handle**.

**Step 2:** dCal checks it as you type: **Available**, or **Taken**. When it is taken, dCal suggests a free one, for example **Try jdoe-2**; click the suggestion to use it. The **Your booking link** field below updates as you type.

<figure><img src="https://3835013762-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCy5rSNtQmtqYCGzJlNEB%2Fuploads%2Fgit-blob-065e065e48c58ce18734cfc0ff1c74b450631a85%2Fdcal-your-booking-page-03-public-handle.png?alt=media" alt="The Public handle field with the value janedoe and the status Available boxed"><figcaption><p>dCal checks your new handle as you type.</p></figcaption></figure>

**Step 3:** Click **Save** at the top right of the page. You see **Saved.**

You can also change it in **Settings** > **General**, in **Public handle**, and click **Save**.

| Rule           | Detail                                                                                                                                            |
| -------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- |
| Characters     | Lowercase letters, numbers and single hyphens, with no hyphen at the start or the end.                                                            |
| Length         | 3 to 40 characters.                                                                                                                               |
| Unique         | No one else in your workspace can have it.                                                                                                        |
| Reserved words | A few words used by the product itself cannot be a handle, such as `admin`, `api`, `booking`, `calendar`, `help`, `login`, `settings` and `team`. |

> **⚠️ Note:** Changing your handle, or the end of an event's address, breaks the links you already shared: the old address does not send people to the new one. Choose your handle before you share it widely. If you do change it, update every place where the old link lives: your email signature, your website, your social profiles, saved replies and any embed snippet.

Only the account code part is different: when your workspace gets a [custom link](https://docs.dapta.ai/dcal/share/custom-link.md), the old six-character code keeps working.

***

## Link previews

When you paste a profile or event link into WhatsApp, Slack, LinkedIn or an email app that shows previews, people see a card made from your booking page, in your colors.

| Link                | Title                                                        | Description                                                                                  | Image                                                                                                           |
| ------------------- | ------------------------------------------------------------ | -------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------- |
| Profile page        | Your name, plus your workspace name when it is different     | Your bio, or **Book time with {your name} online.**                                          | A card with your photo or initials, your name, your bio and **Book a time**                                     |
| Event               | **{event} with {your name}**                                 | The event description, or **{length} min with {your name}. Pick a time that works for you.** | A card with your photo or initials, your name, the event title, its description and length, and **Book a time** |
| Team page           | The team name, plus your workspace name when it is different | **Book time with {team} online.**                                                            | The team logo, when the team has one                                                                            |
| Team event          | The event and team names                                     | The event description, or **{length} min with {team}. Pick a time that works for you.**      | The team logo, when the team has one                                                                            |
| One-off invite link | **Booking**                                                  | A general line about the product, in English                                                 | None                                                                                                            |

When Dapta branding is shown on your pages, the card also carries the product name in small type. See [The Dapta badge](https://docs.dapta.ai/dcal/design/dapta-branding.md).

> **💡 Tip:** Write a description on your events and a bio on your profile. They become the text of the preview, which is what most people read before they tap.

After you change your photo, colors or an event, the preview card can take up to 10 minutes to update. Apps that already showed your link may keep their earlier preview for a while.

One-off invite links are never shown by search engines.

***

## Track where bookings come from

Add UTM tags to any of your booking links to see which campaign, ad or post brought each booking. For example:

`https://book.dcal.ai/k7m2xq/jdoe/intro-call?utm_source=newsletter&utm_medium=email&utm_campaign=october`

* **What is kept.** Each booking keeps the five UTM tags of the link it was booked from: `utm_source`, `utm_medium`, `utm_campaign`, `utm_term` and `utm_content`. Other parameters are not kept. Bookings that an AI agent or an integration makes through the API keep none.
* **On your website.** On a booking page embedded in your website, the booking keeps the UTM tags of your website page, as long as the snippet's `embed.js` script is on that page. If the address in the snippet has UTM tags of its own, those win, and the two are never mixed. See [Embed on your website](https://docs.dapta.ai/dcal/share/embed.md).
* **Cleaning.** A tag that is empty, longer than 128 characters, or that holds a control or hidden formatting character is dropped. A booking never fails because of its UTM tags.
* **Group events.** The booking keeps the UTM tags of the first person who booked the time.
* **Where you find them.** On the booking's own page in your dashboard, under **Campaign**: click the booking in **Bookings**. See [See your bookings](https://docs.dapta.ai/dcal/bookings/see-your-bookings.md).
* **Where they travel.** As `utm` in every booking webhook, when the booking has any (see [Payload reference](https://docs.dapta.ai/dcal/integrations/webhooks/payload-reference.md)), in the answers of `GET /v2/bookings/{uid}` (see [Cal.com-compatible API](https://docs.dapta.ai/dcal/developers/cal-com-compatible-api.md#reading-moving-and-cancelling)) and in the MCP tool `get_booking` (see [MCP tools](https://docs.dapta.ai/dcal/developers/mcp-tools.md)). With [HubSpot](https://docs.dapta.ai/dcal/integrations/hubspot.md) connected, the meeting lists them and they can fill contact properties. If the event passes booking details on its [redirect after booking](https://docs.dapta.ai/dcal/events/event-settings.md#redirect-after-booking), your thank-you page receives them too.

***

## Open a link in Spanish or English

Booking pages show their buttons and messages in English or Spanish, following the language of the visitor's browser. To choose it yourself, add `?lang=es` or `?lang=en` to the end of any of your links, for example `https://book.dcal.ai/k7m2xq/jdoe/intro-call?lang=es`. It works on every public link: your profile page, your events, team pages, team events and one-off invite links. See [What your guests see](https://docs.dapta.ai/dcal/what-guests-see.md).

## Related

* [Embed on your website](https://docs.dapta.ai/dcal/share/embed.md)
* [Custom link](https://docs.dapta.ai/dcal/share/custom-link.md)
* [Profile and layout](https://docs.dapta.ai/dcal/design/booking-page-studio.md)
* [One-off invite links](https://docs.dapta.ai/dcal/events/one-off-links.md)
* [What your guests see](https://docs.dapta.ai/dcal/what-guests-see.md)


---

# 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.dapta.ai/dcal/share/your-booking-page.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.
