Skip to main content

Perk Pages

Give your customers a branded page of perks — on your site or hosted by Paylode — that you can restock and re-rank without a deploy.

A perk page is where your perks program actually meets your customers: a page that looks like part of your product, filled with the deals you've curated. You choose and arrange the perks in the Paylode app; the live page updates on its next load. Your engineers touch it once — or not at all.

Two concepts make up the page. A perk collection is the curated, ranked set of perks — what's on the page. A perks center is the productized page around it — your colors, fonts, and logo, plus search, category filters, and sections, at a stable web address. Configure both once and they stay live.

What you can do with it​

  • Embed the page on your own site — paste a small loader and a container; the branded page renders inside, sized to fit. See Embed a perks page.
  • Or just link to it — every perks center has its own hosted address, for newsletters, QR codes, or a CMS that blocks scripts. See Use a hosted perks page.
  • Reward customers right after they convert — put the embed on your order confirmation screen and pass the order context along. See the confirmation-page section of the embed guide.
  • Make it look like yours — colors, fonts, logotype, background, and which sections appear, all set in the app. See Customize your perks center.
  • Decide what shows, and in what order — pick the perks and put your strongest offer on top. See Choose and rank perks.
  • Carry your attribution through — forward utm_* and custom attributes from your page into your conversion reports. See cmeta for perk pages.
  • Speak your customer's language — serve the page's perks in Spanish or French. See Localize your perks.
  • Hand each customer their own single-use code — for coupon perks, allocate a fresh code on demand at the moment of redemption. See Coupon.
  • Feed your own systems instead of a page — pull a collection into your CMS on a schedule, or expose it as an RSS feed your marketing tools already read. See Sync perks to a CMS and Syndicate perks as RSS.
  • Or render perks yourself — call the API and compose perks into screens you fully own. See Build a custom perk page.

How it works​

The collection's membership and ordering live on the server, not in your code. When you add, pull, or re-rank a perk in the app — or a perk expires — the live page reflects it on the next load. Your integration renders whatever comes back; it never has to know the collection changed.

The perks center wraps that collection with branding, layout, and a domain. A center can show up to four kinds of perk section — general perks, themed groups, local perks near the customer, and short-term perks that expire soon — each rank-ordered. The embed and the hosted page are the same underlying surface, so one configuration serves both.

Integration paths​

PathChoose it whenEffort
EmbedYou can add HTML to a page you own.Paste a few lines once.
HostedScripts are blocked, or you just want a link to share.None — link or QR code.
APIYou want your own layout, filtering, or redemption flow.A real integration; you render everything.

For the full decision table — including what a product manager can self-serve without an engineer — see Integration options.

Go deeper​