# Page Not Found

The URL `files/dcyfFzWhHMVtUX8copNK` does not exist. This page may have been moved, renamed, or deleted.

## Suggested Pages

You may be looking for one of the following:
- [How to setup Shopify?](https://referral-rocket.gitbook.io/docs/integrations/shopify/how-to-setup-shopify.md)
- [Add Referral Widget on Shopify Stor](https://referral-rocket.gitbook.io/docs/integrations/shopify/add-referral-widget-on-shopify-stor.md)
- [Campaign Participants](https://referral-rocket.gitbook.io/docs/getting-started/campaigns/campaign-participants.md)
- [Understanding the Test Plan: Perfect for Testing, Limited for Production](https://referral-rocket.gitbook.io/docs/faq/understanding-the-test-plan-perfect-for-testing-limited-for-production.md)
- [Campaign Types](https://referral-rocket.gitbook.io/docs/getting-started/campaigns/campaign-types.md)

## How to find the correct page

If the exact page cannot be found, you can still retrieve the information using the documentation query interface.

### Option 1 — Ask a question (recommended)

Perform an HTTP GET request on the documentation index with the `ask` parameter:

```
GET https://referral-rocket.gitbook.io/docs/integrations/shopify/how-to-setup-shopify.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

### Option 2 — Browse the documentation index

Full index: https://referral-rocket.gitbook.io/docs/sitemap.md

Use this to discover valid page paths or navigate the documentation structure.

### Option 3 — Retrieve the full documentation corpus

Full export: https://referral-rocket.gitbook.io/docs/llms-full.txt

Use this to access all content at once and perform your own parsing or retrieval. It will be more expensive.

## Tips for requesting documentation

Prefer `.md` URLs for structured content, append `.md` to URLs (e.g., `/docs/integrations/shopify/how-to-setup-shopify.md`).

You may also use `Accept: text/markdown` header for content negotiation.