> For the complete documentation index, see [llms.txt](https://docs.ubiquity.co.nz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ubiquity.co.nz/documentation/data-capture/events/deploying-your-event.md). # Deploying Your Event Every event has a unique URL. How you share that URL determines what data you can collect and how personalised the experience can be. ### Event Link Every event has a live URL accessible from the Event Dashboard. You can share this link in a regular email, add it to your website, or embed the event registration form as an inline frame using the **Get Deployment Code** option.

Registrations collected via a plain link are recorded as anonymous. You will not know who registered unless they provide their details in the form. *** ### UbiQuity Email Sending your event via UbiQuity emails connect each registration to a database contact. This gives you the ability to: * Send reminder emails only to contacts who have not yet registered * Filter your database based on registrations * Merge database fields into the event form, confirmation pages, and triggered emails To deploy via a UbiQuity email, ensure your event is active, then create a mailout and use the Insert UbiQuity Link button to insert the event link into your email content.

A screenshot of the button used to insert UbiQuity links in the standard content editor. — Use the highlighted button to insert UbiQuity links.

You can also add your event link to a form triggered email, a survey Thank You page, or anywhere else in UbiQuity where the Insert UbiQuity Link function is available. --- # 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.ubiquity.co.nz/documentation/data-capture/events/deploying-your-event.md?ask=&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.