Every plan is defined as a child element of a plan group.
An account is only able to see, and move between, sibling plans of the same plan group. This allows for controlled upgrades, downgrades, and cross-grades.
Individual landing pages and offers can be explicitly pegged to a specific plan group (this is the main mechanism behind price testing).
Additionally, every application will also have exactly one plan group that is set to be the default. The default plan group is used whenever an individual goes through a flow that does not require a specific plan group.
You can also explicitly peg landing pages and offers to use the default plan group. This is incredibly powerful: your main flow can be pegged to the default. Following a price test, you can simply change which plan group is the "default" and it will propagate through the associated flows.
Wherever possible, we recommend that you rely on the default plan group.
The first plan group you create will be marked as the default. As you add plan groups, you can change the default plan group.
Attributes:
| Name | Type | Description |
|---|---|---|
| id | string | V7 UUID generated when the plan group is created. |
| name | string | The human-readable name of the plan group. |
| plans | array | Array of Plans available within this group. |
| default | boolean | If this plan group is the default plan group for the application. |
| created_at | integer | Unix timestamp of when the plan group was created (in seconds since the Unix epoch). |
| updated_at | integer | Unix timestamp of when the plan group was last updated (in seconds since the Unix epoch). |