Perkswall Implementation Checklist

use this checklist to confirm your perkswall api integration meets all functional, tracking, and performance requirements follow the steps in order to ensure a smooth deployment parse and extract offer data retrieve the offers array from the api response importance each object contains the attributes required to construct and display an offer extract essential attributes for display title main offer headline use short headline for smaller placements to avoid truncation advertiser name advertiser name description detailed copy (≤ 220 characters) use short description in compact layouts click url destination url use exactly as returned and do not modify query parameters image primary offer image pixel impression beacon url for tracking construct and display offers render terms and conditions as html when present importance preserves formatting for legal or promotional terms if missing, no special terms apply display offers in sequence render the first offer in your placement area trigger its pixel immediately after the offer is visible to the user move to subsequent offers in order, ensuring each impression is recorded avoid preloading multiple offers in the viewport unless you will fire all corresponding pixels immediately implement impression tracking fire a get request to offers\[] pixel whenever an offer becomes visible importance records impressions in momentscience reporting for ctr, ecpm, and cr if offers\[] adv pixel url is present, fire a get request to it at the same time importance satisfies advertiser tracking and third‑party verification do not cache or debounce impression beacons beyond viewability logic importance prevents undercounting and data latency use and optimize creatives select the primary creative from creatives\[] where is primary true if missing, use the image attribute on the offer importance ensures consistent visual presentation supported creative types offer image standard image; size based on your layout hero image featured banner (1000×280 px ±10%) icon image square logo or icon (250×250 px ±10%) when using a proxy server pass the end user’s ip address as the ip parameter in the request payload importance used for geo‑targeting and validating eligible offers pass the user‑agent string as the ua parameter in the request payload importance used for device and platform targeting when implementing loyaltyboost (rewarded offers) only implement loyaltyboost if you can identify your users to reward them with your loyalty currency request loyaltyboost offers by passing the loyaltyboost query parameter with values 1 or 2 1 include loyaltyboost offers 2 return only loyaltyboost offers importance ensures the response matches your rewarded experience requirements set up a postback url with momentscience see handling postback events importance receives server‑to‑server notifications when users convert, including payout amount (usd), so you can credit loyalty rewards accurately include a stable user fingerprint in the payload as adpx fp importance prevents showing a loyaltyboost offer to a user who has already converted on it include a custom key‑value in the payload that identifies where to credit the reward (for example, loyaltyid=12345566 ) importance this value is returned in postbacks with the payout amount, allowing you to map the conversion to the correct account and calculate reward amounts need assistance? contact our support team at help\@momentscience com mailto\ help\@momentscience com