> For the complete documentation index, see [llms.txt](https://partner-docs.covergenius.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://partner-docs.covergenius.com/xcover-journeys/integration/data-exchange.md). # Data Exchange How context and customer data flow between your system and the journey, including query parameters for non-PII and server-to-server channels for PII. ### How data reaches the journey Data flows through two channels. **Query parameters** carry non-PII context (country, booking references, product categories) from your platform to the journey. **Server-to-server calls** between the Cover Genius backend and your API handle customer PII — names, emails, addresses, and other personally identifiable information never pass through the browser. ### Query parameters Query parameters pass non-PII context to the journey when loading it. The `country` parameter (ISO 3166-1 alpha-2, e.g. `AU`, `US`) is used for content localization. Beyond that, partners can pass any non-PII data relevant to their integration — booking references, product categories, session identifiers, or campaign tags. These are defined during onboarding based on what context the journey needs. ``` https://xcj.xcover.com/acme-travel/en/?country=AU&booking_ref=ABC123&product=motor ``` The journey reads these parameters on load and uses them to configure the flow, fetch content, or pass context to the Cover Genius backend. Work with your Cover Genius integration manager to define the parameters your integration requires. {% hint style="warning" %} **Never include PII in query parameters.** Personally identifiable information (names, emails, phone numbers, addresses, dates of birth, etc.) is exchanged exclusively through server-to-server channels. {% endhint %} ### Customer data (PII) Customer PII is always exchanged server-to-server between the Cover Genius backend and your API. PII is never passed through URL parameters or any client-side channel. The method for obtaining customer data depends on your authentication model. In all cases, the Cover Genius backend handles the data exchange — no PII flows through the browser. ### Booking notifications After a customer completes a purchase, Cover Genius notifies your system that a booking has been confirmed. The notification format and delivery method are configured during onboarding — contact your Cover Genius integration manager to set up endpoints and review the payload format for your integration. {% hint style="info" %} Looking for real time, in browser or in app events instead, such as journey ready, offer selection, or purchase complete? See [Messaging](/xcover-journeys/integration/messaging.md) for the live event channel between your app and the journey. {% 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://partner-docs.covergenius.com/xcover-journeys/integration/data-exchange.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.