Boost performance
Measure the lift from each of your Boost campaigns — how many teasers were shown, how many incentives were delivered and clicked, and the business value those deliveries represent.
"Campaign" here means a Boost campaign — a "do this, get that" reward journey where a customer completes an action and receives a reward.
Boost performance is available through your analytics data, scoped to your account. You query the same way you query anything else (mint a token, send a query) — this page shows the measures and dimensions that matter for Boost and a worked example you can adapt.
Before you begin
- An analytics token. Mint one as described in Authenticate.
- Familiarity with the query format. See Query your metrics.
What you can measure
Boost engagement is split across a few views, each capturing one stage of the journey. The useful measures for reporting are counts and delivered value:
| View | Measure | What it counts |
|---|---|---|
boost_teasers_shown | count | Reward teasers shown to customers. |
boost_incentives_delivered | count | Incentives delivered on completed journeys. |
boost_incentives_delivered | total_business_value | The business value of those deliveries. |
boost_incentives_clicked | count | Deliveries that were clicked through. |
boost_events_custom | count | Custom events you track on a journey. |
You can break any of these down by campaign or journey:
| Dimension | Meaning |
|---|---|
campaign_id / campaign_name | Which campaign the activity belongs to. |
journey_id | A single customer's run through the campaign. |
event_name | The name of a custom event (on boost_events_custom). |
Time dimension (all Boost views): event_date.
A worked example — deliveries and value by campaign
This asks: for each campaign over the last 30 days, how many incentives did I deliver and what was the delivered business value?
curl -G https://cube.paylode.com/cubejs-api/v1/load \
-H "Authorization: eyJhbGciOiJIUzI1NiJ9.EXAMPLE_PAYLOAD.EXAMPLE_SIGNATURE" \
--data-urlencode 'query={
"measures": [
"boost_incentives_delivered.count",
"boost_incentives_delivered.total_business_value"
],
"dimensions": ["boost_incentives_delivered.campaign_name"],
"timeDimensions": [{
"dimension": "boost_incentives_delivered.event_date",
"dateRange": "last 30 days"
}],
"order": { "boost_incentives_delivered.count": "desc" }
}'
One row per campaign (trimmed):
{
"data": [
{ "boost_incentives_delivered.campaign_name": "Spring Signup Reward", "boost_incentives_delivered.count": "412", "boost_incentives_delivered.total_business_value": "8240.00" },
{ "boost_incentives_delivered.campaign_name": "Refer a Friend", "boost_incentives_delivered.count": "173", "boost_incentives_delivered.total_business_value": "3460.00" }
]
}
To turn deliveries into a funnel, run the same shape against
boost_teasers_shown.count (top of funnel) and boost_incentives_clicked.count
(reward click-through), grouped by the same campaign_name. Pass the token in
Authorization with no Bearer prefix, and parse the string measure values
before doing math.
This is the analytics view of Boost — engagement counts and delivered value aggregated over time. It's distinct from the per-campaign statistics you can read directly from the Boost API while running a campaign; that surface is described in the Boost guides. Use analytics for reporting and trends over your own data.
Related
- Boost — what a campaign, teaser, incentive, and journey are.
- Query your metrics — the full query format.
- Data freshness — why recent figures keep moving.
For the analytics query host and the token endpoint schema, see the API Reference.