Offers IFrame Integration Guide

Embed the PrimeEarn Games & Offers wall directly into your app or website using an IFrame or WebView. This guide walks you through the full setup in six steps.

Step 1 — Get Your URL

Your dedicated offers/games wall URL is:

https://monetize.primeearn.com/offers?app=XXXXXXXX&uuid=Test123

Replace XXXXXXXX with your Publisher App ID and Test123 with your user’s unique identifier (see Step 3).

Need the combined wall (Surveys + Games)? Use https://monetize.primeearn.com/featured?app=XXXXXXXX&uuid=Test123 instead.

Step 2 — Implement in Your App or Website

Choose the integration method that fits your platform:

WebView (Mobile Apps)

Load the URL inside a native WebView component. Make sure the WebView has:

JavaScript enabled
DOM storage enabled
Redirect/navigation handling so external links open in a browser

IFrame (Web)

<iframe
  src="https://monetize.primeearn.com/offers?app=XXXXXXXX&uuid=Test123"
  width="100%"
  height="700"
  frameborder="0"
  allow="clipboard-write"
  title="PrimeEarn Offers Wall"
></iframe>

New Browser Tab

If an IFrame is not suitable, open the URL in a new tab:

window.open(
  'https://monetize.primeearn.com/offers?app=XXXXXXXX&uuid=Test123',
  '_blank',
  'noopener,noreferrer'
);

Step 3 — Pass Parameters

Replace the uuid placeholder with a unique, stable identifier for the current user. This ties offer completions to the correct account.

Parameter	Required	Description
`app`	Yes	Your Publisher App ID (provided in your dashboard)
`uuid`	Yes	A unique, persistent ID for the end user
`maid`	If available	Mobile Advertising ID — IDFA on iOS or GAID on Android. Must be provided when available; significantly improves performance.
`age`	No	User age for offer targeting (`0–150`).
`birthday`	No	Date of birth in `YYYY-MM-DD` format. Preferred over `age` when both are available.
`gender`	No	User gender: `m` (Male) or `f` (Female).
`zip`	No	Postal / ZIP code for geo-targeted offer matching.

Age vs. birthday: If you have both, prefer passing birthday — it is more precise and provides better targeting than age alone.

Example with a real user ID:

https://monetize.primeearn.com/offers?app=myApp1234&uuid=user_abc_987

Never reuse uuid values across different users. Each user must have a stable, unique ID to ensure rewards are attributed correctly.

Step 4 — Customize Design

The offers wall supports several design parameters you can append to the URL.

Parameter	Values	Description
`theme`	`light` / `dark`	Sets the color scheme
`color`	Hex code (e.g. `3498db`)	Primary accent color (no `#`)
`logo`	URL-encoded image URL	Your brand logo displayed at top

Example:

https://monetize.primeearn.com/offers?app=XXXXXXXX&uuid=Test123&theme=dark&color=3498db

Match the theme parameter to your app’s current color mode for a seamless user experience.

Step 5 — Handle Rewards via Postback

When a user completes an offer or game milestone, PrimeEarn fires a server-to-server postback to your configured callback URL.

Postback URL Format

Configure your callback URL in the dashboard. PrimeEarn will substitute the placeholders at the time of the event:

https://your-server.com/reward?user={user_id}&amount={reward}&type={type}&tx={tx_id}

Postback Parameters

Parameter	Type	Description
`{reward}`	Integer	Amount of in-app currency to award to the user
`{payout}`	Integer/Float	Publisher payout in USD
`{type}`	Integer	Event type (see table below)
`{user}`	String	The unique user ID you passed as `uuid`
`{tx_id}`	String	Unique transaction ID for deduplication

Games/Offers Event Types (`{type}`)

Value	Event	Description
`7`	Completed	Offer/game task fully completed and credited
`9`	Reconciled	Transaction reconciled after review. `tx_id` starts with `R-`
`11`	Pending	Initial postback during a Credit Delay 7 offer

Understanding Credit Delay 7

Credit Delay 7 ExplainedSome game offers operate on a 7-day credit delay:

Immediately when the user completes the task, you receive a PENDING postback (type=11).
After 7 days, one of the following is sent:
- COMPLETED (type=7) — task was verified and credit is confirmed.
- RECONCILED (type=9) — transaction was reconciled. The tx_id for reconciled events will begin with R-.

Do not grant the reward to the user until you receive the COMPLETED (type=7) or RECONCILED (type=9) postback.

The Earning Jar

The Earning Jar is a threshold mechanic built into the PrimeEarn wall. A user must accumulate enough reward value across a campaign’s tasks to “fill” the jar before any rewards can be redeemed in your app. This feature is currently rolling out across campaigns and will eventually apply to all.

If all reward events in a campaign fall below the Credit Delay 7 threshold, the jar fills and rewards are released immediately. If any single reward exceeds that threshold, the entire jar is held until our team confirms the user is not fraudulent.

Scenario A — Jar fills normally (no Credit Delay 7)

Campaign requires 10,000 points to fill the jar.

Task	Points	Value
Level 1	2,000 pts	$2
Level 2	3,000 pts	$3
Level 3	5,000 pts	$5

The jar fills and the user can redeem immediately. You receive 3 separate postbacks, each with a unique tx_id, one per task.

Scenario B — Jar held due to Credit Delay 7

Campaign requires 10,000 points to fill the jar, but one task exceeds the Credit Delay 7 threshold.

Task	Points	Value
Level 1	2,000 pts	$2
Level 2	3,000 pts	$3
Level 10	10,000 pts	$10 ← triggers hold

The jar fills, but the high-value task triggers Credit Delay 7 — so no rewards are released yet.

User confirmed legitimate
User confirmed fraudulent

Once our team verifies the user is not fraudulent, you receive all 3 postbacks at the same time, each with a unique tx_id. Receiving multiple postbacks simultaneously is expected behavior in this scenario — treat them as normal confirmed postbacks and credit the user for each.

In Scenario B, do not credit the user for any of the tasks until you receive the simultaneous batch of postbacks. The delayed delivery is intentional and confirms all rewards passed fraud review.

Whitelisting IPs

Ensure your server accepts postback requests from these PrimeEarn IPs:

119.57.82
12.33.196
13.14.251

Reject any postback requests that do not originate from these IPs to prevent reward fraud.

Step 6 — Go Live

Before enabling for all users, run through this checklist:

Replace XXXXXXXX with your real Publisher App ID
Replace Test123 / uuid with your real user ID logic
Configure your postback URL in the PrimeEarn dashboard
Whitelist the PrimeEarn IP addresses on your server
Test a full offer completion in a staging environment and verify your postback receives the correct parameters
Handle PENDING (type=11) postbacks without immediately granting rewards
Verify deduplication logic using {tx_id}, noting R- prefix for reconciled events

Once all checks pass, deploy and start earning!

Documentation Index

​Offers IFrame Integration Guide

​Step 1 — Get Your URL

​Step 2 — Implement in Your App or Website

​WebView (Mobile Apps)

​IFrame (Web)

​New Browser Tab

​Step 3 — Pass Parameters

​Step 4 — Customize Design

​Step 5 — Handle Rewards via Postback

​Postback URL Format

​Postback Parameters

​Games/Offers Event Types ({type})

​Understanding Credit Delay 7

​The Earning Jar

​Scenario A — Jar fills normally (no Credit Delay 7)

​Scenario B — Jar held due to Credit Delay 7

​Whitelisting IPs

​Step 6 — Go Live

Offers IFrame Integration Guide

Step 1 — Get Your URL

Step 2 — Implement in Your App or Website

WebView (Mobile Apps)

IFrame (Web)

New Browser Tab

Step 3 — Pass Parameters

Step 4 — Customize Design

Step 5 — Handle Rewards via Postback

Postback URL Format

Postback Parameters

Games/Offers Event Types (`{type}`)

Understanding Credit Delay 7

The Earning Jar

Scenario A — Jar fills normally (no Credit Delay 7)

Scenario B — Jar held due to Credit Delay 7

Whitelisting IPs

Step 6 — Go Live