# Embed a connectivity journey

Define your markets, offer types, customer identity, payment arrangement and support responsibility. Confirm the integration and hosted journey options available for your selected service before choosing which parts your team will build.

Start with one offer and one complete customer journey. A working purchase screen is only one step: the customer also needs a way to install the service, return to it and get help.

## 1. Connect discovery

Present eligible offers where they help the customer: in a trip, account, membership or device workflow. Show the actual coverage, allowances and renewal or validity terms.

## 2. Preserve the customer’s intent

Carry the selected offer and authorized customer into the purchase journey. Retain your acquisition identifiers through permitted analytics fields; keep installation credentials out of them.

## 3. Follow the purchase

Separate checkout success from network fulfillment. Provide a status and resume path tied to the existing order so the customer can finish after an interruption.

## 4. Guide installation and return

Choose the device-appropriate setup path and define the return to your app. The customer should be able to find the plan and help after closing the original confirmation page.

## 5. Add subscriber self-service

Connect usage observations, top-ups, renewal changes and support to the same line. Measure purchase, installation and first use as distinct outcomes.

Expose only the actions supported by the selected service. For example, a package top-up should not be presented as a subscription renewal, and an unavailable usage observation should not be displayed as zero usage.

## Define the application boundary

| Your application keeps       | The service outcome to verify                                                   |
| ---------------------------- | ------------------------------------------------------------------------------- |
| Customer and accepted offer  | The order corresponds to the intended service and agreed terms                  |
| Order reference              | Purchase and fulfillment can be recovered after an interrupted response         |
| Profile or service reference | Installation and management refer to the existing allocation                    |
| Return and support routes    | The customer can resume from their account without the original browser session |

Retain references in your authorized application records. Keep private activation material out of analytics events, public URLs and routine support messages. Use the supported installation journey to deliver credentials to the intended customer.

## Troubleshooting

If a customer returns without finishing installation, recover their existing order and profile. Do not create another service just because the original browser session ended. Keep a support path available when the underlying service cannot complete the next step.

## Test interruption and recovery

Close the browser after purchase and reopen the customer’s account. Verify that the existing order appears and leads to the correct next step. Repeat after installation starts. The return journey should help the customer continue from the recorded state.

Test an uncertain purchase response, unavailable installation details and a delayed usage observation. Each should preserve the existing service reference and offer a useful recovery or support action. Follow the [eSIM API guide](/docs/guides/esim/api) for purchase recovery and the [installation guide](/docs/guides/esim/installation) for device setup.

## Next steps

- [Embed a connectivity journey with Bird](/products/esim/embedded-connectivity)
- [eSIM resource library](/products/esim/resources)
- [Get started with eSIM](/products/esim/getting-started)

## Related resources

- [What is an eSIM?](/explained/esim/what-is-an-esim) (answer)
- [eSIM](/products/esim) (product)
- [eSIM connectivity guide](/docs/guides/esim/overview) (docs)

[Get an implementation brief](/learn/workspace?topic=esim)