A valid request URL is required to generate request examples{
"traffic_read": true,
"visitors_last_28_days": 123,
"click_rate": 123,
"detectable_lift": 123,
"days_to_detect": 123,
"min_days": 123,
"min_visitors_per_variant": 123
}{
"detail": "<string>"
}{
"detail": "<string>"
}{
"detail": "<string>"
}{
"detail": "<string>"
}How long an A/B test on this collection would need
From the collection’s visitors and click rate over the last 28 days: the days a test with the given split needs before a 10% relative difference in click rate becomes visible, with 80% power at a two-sided 5% level. Read-only.
A valid request URL is required to generate request examples{
"traffic_read": true,
"visitors_last_28_days": 123,
"click_rate": 123,
"detectable_lift": 123,
"days_to_detect": 123,
"min_days": 123,
"min_visitors_per_variant": 123
}{
"detail": "<string>"
}{
"detail": "<string>"
}{
"detail": "<string>"
}{
"detail": "<string>"
}Authorizations
Shopify App Bridge session token of the embedded Depict: Search & Merchandising app. The shop in the token determines the merchant; merchant_id parameters must belong to that shop.
Path Parameters
Numeric Shopify collection id.
Query Parameters
Lite merchant id, e.g. shopify-<shop id>.
Percent of traffic that would go to variant B.
10 <= x <= 90Comma-separated Shopify market ids the test would run in; absent means every market. The traffic read is scoped to them.
Response
The estimate.
False when the traffic read failed: the counts below are then zeros that say nothing about the collection.
Share of those visitors who clicked a product; null without visitors.
Whole days a test at this traffic and split needs before a detectable_lift difference in click rate shows, readiness floor included. Null when the last 28 days give no pace or no clicks.
Was this page helpful?