1. Fetch Offers (Offer List)
Call the Get Offers endpoint to retrieve all available offers for the user.
Endpoint:
GET /offersInput:
pub_member_idPurpose: Populate the offerwall UI with eligible offers scoped to that pub_member_id
2. Return Personalized Offer List
The Offers API response returns a filtered and ranked list of offers based on the pub_member_id.
Filtering logic includes:
Conversion and completion history
Targeting rules (geo, device, campaign eligibility)
This ensures each user receives a dynamically personalized offer experience.
3. View Offer Details (Offer Impression)
When a user views or opens an offer card, call:
Endpoint:
GET /offer-details
This action:
Logs an impression event
Generates and returns a unique
viewIdReturns enriched offer details for UI rendering
4. Offer Click Tracking (Offer Link Request)
When a user clicks into an offer CTA, call:
Endpoint:
GET /offer-linkorGET /offer-link-redirectRequired:
viewId(from Step 3)
This action:
Registers a click event tied to the impression
Generates a tracking redirect URL
Ensures click is attributed to the correct
viewId&pub_member_id
5. Redirect User
After receiving the response from /offer-link:
Redirect the user to the returned tracking URL
This continues downstream attribution (MMP / advertiser tracking)
Key Details
For details on how to handle new fields in our API schema, please see our SDK API Schema Disclaimer.
Authentication: No bearer token or API key is required when using the Offerwall or PubMember SDK endpoints. These endpoints are tenant-scoped and rely on publisher query parameters (e.g.,
pub_member_id).