Skip to content

docs(xsolla): correct primary keys for project-scoped Store tables #21311

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Gilbert09 merged 1 commit into from
Oct 19, 2026
Merged

docs(xsolla): correct primary keys for project-scoped Store tables #21311

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 11 additions & 8 deletions contents/docs/cdp/sources/xsolla.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ availability:
sourceId: Xsolla
---

The Xsolla connector syncs your payment and subscription data into PostHog, including transactions, subscriptions, payouts, reports, promotions, projects, and per-project subscription details.
The Xsolla connector syncs your payment and subscription data into PostHog, including transactions, subscriptions, payouts, reports, promotions, projects, and per-project subscription and Store details.

## Prerequisites

Expand Down Expand Up @@ -52,13 +52,16 @@ These tables read data at the merchant level:

### Project-scoped tables

These tables are read once per project that the merchant owns. Each row includes a `project_id` column, and the primary key is `(project_id, id)` because the Xsolla API does not guarantee globally unique IDs across projects.
These tables are read once per project that the merchant owns. Each row includes a `project_id` column, and the primary key includes `project_id` because the Xsolla API does not guarantee globally unique IDs across projects. Subscription tables use `(project_id, id)`. Store tables use `(project_id, sku)`.

| Table | Description | Sync |
| ----------------------- | -------------------------------------- | ------------ |
| `subscription_payments` | Subscription charges for each project | Full refresh |
| `subscription_plans` | Subscription plans for each project | Full refresh |
| `subscription_products` | Subscription products for each project | Full refresh |
| Table | Description | Primary key | Sync |
| ----------------------- | ----------------------------------------- | ------------------- | ------------ |
| `subscription_payments` | Subscription charges for each project | `(project_id, id)` | Full refresh |
| `subscription_plans` | Subscription plans for each project | `(project_id, id)` | Full refresh |
| `subscription_products` | Subscription products for each project | `(project_id, id)` | Full refresh |
| `virtual_items` | Store virtual items for each project | `(project_id, sku)` | Full refresh |
| `virtual_currencies` | Store virtual currencies for each project | `(project_id, sku)` | Full refresh |
| `bundles` | Store bundles for each project | `(project_id, sku)` | Full refresh |

## Sync details

Expand All @@ -68,4 +71,4 @@ These tables are read once per project that the merchant owns. Each row includes

- **Resumable syncs** – If a sync is interrupted, it resumes from the last completed window, project, and page offset on the next run.

- **Project fan-out** – For project-scoped tables (`subscription_payments`, `subscription_plans`, `subscription_products`), PostHog first lists the merchant's projects, then reads each project in turn.
- **Project fan-out** – For project-scoped tables (`subscription_payments`, `subscription_plans`, `subscription_products`, `virtual_items`, `virtual_currencies`, `bundles`), PostHog first lists the merchant's projects, then reads each project in turn.
Loading