Skip to main content

cmeta for Boost

Tag every Boost journey with your own identifiers — a user id, a placement, an experiment — and read them back when you measure the campaign.

Boost's journey endpoints accept your custom attributes as query parameters: any parameter prefixed cmeta_, plus the five standard UTM parameters (utm_source, utm_medium, utm_campaign, utm_term, utm_content). Attach them to the calls your product makes and they travel with the journey into your analytics.

Where to pass them​

Append cmeta_* / utm_* query parameters to any of the customer-journey and outreach calls:

  • Teasers — GET /teasers/{campaignId}?cmeta_user_id=42931
  • Event tracking — POST /track/{campaignId}?...
  • Rewards — GET /rewards/{campaignId}?...
  • The redeem click — GET /click?...
  • Outreach — the reward URL, outreach click, and both tracking pixels accept them too, so email-delivered rewards carry the same tags.

The rules are the ones every Paylode surface shares: name your own attributes with the cmeta_ prefix (letters, digits, hyphens, underscores), keep values under 255 characters, URL-encode them, and use the five utm_ names as-is.

curl "https://boost.paylode.com/teasers/9b2c1e40-7a3d-4c88-9f21-2a1b6c5d4e30?cmeta_user_id=42931&utm_source=app" \
  -H "X-API-Key: sk_example_9d4a2f7c1b8e"

Tag consistently across the journey — the same cmeta_user_id on teasers, track, and rewards is what lets you follow one customer's trip end to end in your reports.

Where they come back​

  • Boost engagement views — incentive clicks carry a cmeta dimension in your analytics, so you can break clicks down by your own tags.
  • Conversions — a rewarded action that converts lands in your conversion data with the attributes in its attribution set: cmeta_ prefixes are stripped on the way back (cmeta_user_id → user_id), utm_* names come back unchanged.

Query both through Analytics; the Boost-specific views and a worked query are in Boost performance.