Offerwall Reward Not Credited: Why Points Go Missing & How to Fix It

How offerwall tracking connects the click to a reward

An offer opened from FreeGiftZone passes through three separate systems: FreeGiftZone, the offerwall aggregator such as Torox, AdGate Media, or RevU, and the advertiser’s mobile measurement partner (MMP), such as AppsFlyer or Adjust. The offer needs a matching record at each step before a milestone can appear in the reward ledger.

1. When you open an offer in the tasks hub, FreeGiftZone creates a unique cryptographic click identifier and associates it with your user account.
2. FreeGiftZone passes that identifier to the offerwall network. The network adds its campaign token and redirects the device to Google Play or the Apple App Store.
3. After the first launch, the app’s analytics software development kit (SDK) asks the mobile measurement partner (MMP) where the install came from. The partner compares the device advertising identifier with recent clicks recorded during the previous 24 hours.
4. When the advertiser’s game server receives a qualifying milestone, it sends a server to server (S2S) postback to the offerwall. The postback carries the original click identifier, a timestamp, and a hash based message authentication code (HMAC) to sign the conversion.
5. The offerwall validates the signature and sends an incoming webhook to FreeGiftZone. The FreeGiftZone system then updates the user’s ledger balance.

This is a five step relay across the three systems. If one link fails to communicate, the reward can disappear from the status screens. Comparing the offerwall record with the game’s record helps identify which system needs to investigate.

The four points states and their review windows

Completed offers do not all become spendable points at once. In this reward system, the points lifecycle has four states designed to protect users and advertising partners from billing fraud.

The complete security hold schedule and reversal procedures appear in the Reward Rules and Refunds Guide. A pending status means the reward is still in the verification stage; it does not mean the reward has been lost.

Start with the offer you accepted

Open the original offer details before reinstalling a game or starting another task. Look for the qualifying country, whether the advertiser requires a new player, the exact goal, the deadline, and any purchase or account conditions. Save a screenshot of those terms while they are still visible, because an offer can disappear from the wall after you begin it.

Read the goal literally. An offer that asks for a particular town hall level may not count a nearby level, a player level, or a collection of in game points. If the reward is split across several milestones, each one may have its own condition and time limit. A success screen inside the game confirms that the game recorded your progress; it does not by itself confirm that the offer provider recorded the same event.

Timing is specific to the offer and provider. If the offer says that credit can take a stated amount of time, use that window as your guide. If it gives no timing information, check the provider's help screen before relying on advice written for a different offer wall. There is no single waiting period that applies to every game, survey, purchase, and reward network.

Compare the game with the offer wall status

A missing balance can describe several different situations. The game may show the goal as complete while the offer wall still shows no progress, or the wall may show that a reward is under review. Those screens point to different next steps, so note the wording you actually see instead of assuming that every provider uses the same status names.

These are common screen patterns, not a universal status system. Some providers use different labels or place help under an offer history menu. A game receipt, player profile, or achievement page can support your explanation, but only the offer provider can confirm what its own record shows.

Six recurring reasons offerwall credits go missing

When a reward does not even appear as pending, the cause is often a break in attribution. In our physical device testing lab, Lead Author Monu identified six recurring failure modes responsible for more than ninety percent of tracking drops.

1. Ad blockers and private domain name system filtering. AdGuard, Brave Shields, NextDNS, and Pi hole can intercept tracking requests. When the app tries to connect to domains such as app.appsflyer.com or tr.adgate.media, a local resolver can block the event before it reaches the advertiser.
2. Click identifier removal during private browsing or browser switching. Opening an offer in a private tab, or moving from the default browser to an in app browser during registration, can strip referral query parameters. Without the original click identifier, the advertiser cannot associate the conversion with the account.
3. Prior installs and device fingerprint collisions. Sponsored gaming and utility offers require a genuine first time install. An earlier download under the same Apple ID, Google account, or physical device serial number can cause MMP deduplication to classify the install as organic re engagement and disqualify the reward.
4. Network changes, mobile proxies, and virtual private networks. Switching from residential Wi Fi to mobile data changes the public Internet Protocol address. Many advertisers enforce address consistency during a session. For example, a click from Chicago followed by a registration event from a mobile carrier subnet in Dallas can cause the security filter to drop attribution. Commercial virtual private networks are blocked automatically by all major offerwall providers.
5. Advertiser batch synchronization delays. Casual game milestones often send postbacks within sixty minutes. Enterprise partners, including banking apps, credit score services, and streaming providers, can process conversions in daily or weekly batch files, so a high tier financial registration may not credit immediately.
6. Secondary milestone conditions that were not completed. A task may require both level 10 and email verification, or a castle upgrade to level 12 within fourteen days. Stopping at level 9 or passing the calendar deadline invalidates that claim.

Provider status windows and dispute routes

Offerwall providers maintain separate ticketing paths and postback schedules. The figures below are the support navigation and verification latencies documented for the providers integrated into digital reward platforms.

Submitting a support ticket before the mandatory grace period expires results in an automated rejection by provider compliance bots. Use the table to find the correct path and wait for the displayed grace period before opening a dispute.

Check eligibility without changing privacy settings

Before sending a claim, look for conditions that are easy to miss when an offer contains several screens of rules. These four checks often explain why a visible game achievement does not match the offer record:

Do not reset advertising identifiers, create another account, or use a location changing service to retry the same task. Those steps do not establish what happened during the original session and may conflict with the offer's terms. If a device or country rule seems unclear, ask the provider to explain the rule rather than trying to make the device appear eligible after completion.

Build the four piece evidence package

A missing reward claim depends on evidence that lets support find the offer and match it to the account. Blurry, cropped images and vague descriptions are often declined without investigation. Keep the original screenshots and assemble these four items before opening the ticket:

Keep passwords, one time login codes, full payment card details, and unused gift card codes out of screenshots and support messages. A legitimate review should not need your password. If a purchase was part of the offer, share a receipt only through the official support form and cover details that are not needed to identify the transaction.

Submit the dispute in five steps

Use the original offerwall session so the provider can locate the click token. This escalation order keeps the evidence with the team that can inspect the advertiser record.

1. Wait for the grace period. Allow at least 24 to 48 hours after reaching the milestone before taking action. Many advertiser postback queues run on asynchronous 24 hour batch schedules; the provider’s required window may be longer.
2. Open the dispute from the offerwall frame. Return to the specific provider inside the tasks directory, open its status menu, locate the offer, and choose Contact Support or Dispute. The provider holds the session token needed to query the advertiser.
3. Attach the four evidence items. Add uncropped screenshots and a concise account of when the task began and when its final condition was reached.
4. Follow the provider’s review service level. Standard offerwall ticket reviews require three to seven business days. Check email, including spam folders, for confirmation or a follow up request.
5. Escalate to FreeGiftZone support when needed. If the provider has not replied within seven business days or closes the ticket despite complete photographic evidence, send your FreeGiftZone account email, offerwall name, offer title, provider ticket number, and original proof images. The compliance team will audit the provider webhook log directly.

Provider menus differ. Tapjoy’s instructions, for example, direct users to return to the same app on the same device, open Reward Status, locate the offer under Ongoing, Rewarded, or Expired, then choose Contact Support and Missing Rewards. That route is specific to Tapjoy; use the support link shown in any other provider’s offerwall.

If the provider says it sent the reward but the host app balance did not change, contact the host platform with the provider’s response and case number. If it says the task did not qualify, ask which condition was missed and compare the answer with the offer copy you saved. For details about contested reversals and account audits, read the Reward Rules and Refunds policy and the Mobile Game Offers guide.