Skip to main content

Send Boost rewards by email

Put a campaign's reward in your own email, SMS, or push — with a tracked link and open-tracking pixels — and count the engagement.

Boost doesn't send messages for you. Instead it gives you the pieces to drop into whatever channel you already use: a tokenised reward URL that tracks the click and redirects to the offer, and tracking pixels you embed to count who saw the teaser and who saw the reward. You send the message; Paylode counts what happens.

This is the outreach path. If you're rendering rewards on your own site instead, see Go live with Boost or rendering the journey in your own product.

How it works​

Three URLs make up an outreach reward, all on https://boost.paylode.com:

  • The reward URL — generated per perk, carries a token identifying the campaign and reward. Put it behind your "Redeem" call to action. Following it records the click and redirects the customer to the offer.
  • The teaser pixel and the reward pixel — 1×1 transparent images you place in the message body. Loading them records a teaser view or a reward view.

You can tie all three to a single customer with a journeyId. Outreach journeys are yours to control: pick a unique id per recipient and pass it on each URL, and Boost associates the views and click with that one journey. If you omit it, Boost derives one from the campaign id.

Before you begin​

  • A campaign id and the perk id of the reward you want to feature.
  • Your API key — generating a reward URL is authenticated with your X-API-Key header. See Authentication. The pixel and click URLs carry their own credentials and need no key.
  • Your own sending channel — an ESP, SMS provider, or push service.

Steps​

1. Generate a reward URL​

Ask for a URL for the perk you want to feature with GET /outreach/campaign/{campaignId}/reward-url:

curl "https://boost.paylode.com/outreach/campaign/9b2c1e40-7a3d-4c88-9f21-2a1b6c5d4e30/reward-url?perkId=4821" \
  -H "X-API-Key: sk_example_9d4a2f7c1b8e"

The response is the URL, as a JSON string:

"https://boost.paylode.com/outreach/click?token=sk_example_rwurl_a1b2c3d4"

The perk must be an incentive on that campaign; otherwise the call returns 400 PERK_IS_NOT_IN_CAMPAIGN.

2. Build the message​

Put the reward URL behind your call to action, and optionally add your own journeyId so the click ties back to a specific recipient:

<a href="https://boost.paylode.com/outreach/click?token=sk_example_rwurl_a1b2c3d4&journeyId=7c9a1e40-3b2d-4f88-9a21-6d5b2c1e4f30">
  Claim your reward
</a>

When the recipient clicks, Boost records the click and responds with a 302 redirect to the offer — the same tracked redemption a customer would get on your site.

3. Add the tracking pixels​

Embed the pixels as images. Load-on-open counts the view. Use the teaser pixel where you show the offer as a tease, and the reward pixel where you present the redeemable reward. Pass the same journeyId to correlate them:

<!-- Teaser view -->
<img src="https://boost.paylode.com/outreach/campaign/9b2c1e40-7a3d-4c88-9f21-2a1b6c5d4e30/tracking-pixel/teaser?journeyId=7c9a1e40-3b2d-4f88-9a21-6d5b2c1e4f30"
     width="1" height="1" alt="" style="display:none" />

<!-- Reward view -->
<img src="https://boost.paylode.com/outreach/campaign/9b2c1e40-7a3d-4c88-9f21-2a1b6c5d4e30/tracking-pixel/reward?journeyId=7c9a1e40-3b2d-4f88-9a21-6d5b2c1e4f30"
     width="1" height="1" alt="" style="display:none" />

Each pixel request returns a 1×1 transparent PNG, so it renders as nothing.

4. Send it​

Send the message through your own channel. Boost is only counting — it never sends on your behalf.

Test without polluting your numbers​

Every outreach URL accepts disableTracking=true. Add it while you're building and testing so the clicks and views you generate yourself don't land in your statistics:

https://boost.paylode.com/outreach/click?token=sk_example_rwurl_a1b2c3d4&disableTracking=true

Once you're live​

Clicks and views flow into your campaign's engagement data. Read the totals through Boost performance.

Troubleshooting​

caution

Pixel views are rate-limited. To keep repeated loads from inflating counts, Paylode records at most one tracked view per second per campaign from a given IP address — and the teaser and reward pixels share that budget, so two pixel loads from the same recipient in the same second count once. Over the limit, the pixel still returns its image so your message renders fine — the extra view just isn't counted. This is fixed platform behaviour, not a setting.

note

Clicks aren't deduplicated for outreach. Unlike the on-site reward flow, outreach clicks don't dedupe per journey automatically — that's why you control the journeyId. Use a stable, unique id per recipient if you want one customer's repeated clicks grouped together.

caution

Use the current host. Generate every URL fresh from the API and send customers to boost.paylode.com. Don't hand-build outreach URLs against older hostnames.

For the outreach operations (generateRewardUrl, registerOutreachClick, trackOutreachTeaserView, trackOutreachRewardView), see the API reference.