offerwall app install not attributed

Where Did the Install Stop Belonging to the Offerwall?

An app can be present on the phone and still not belong to the offerwall in the advertiser’s attribution system. The install must normally begin from the tracked offer, qualify as a new installation, remain on the eligible device and country, survive privacy and identifier limits, and produce an install event that reaches the provider. Reinstalling after one of those links breaks usually does not recreate a valid first install.

Most faucet rewards are tiny. FaucetPay can help you collect small payouts from supported faucets, PTC sites and reward platforms in one microwallet before withdrawing later.

Set up FaucetPay to collect small rewards →

Use the Install Attribution Chain of Custody

Record every custody handoff.

  • Link 1 — offerwall click tied to the host account
  • Link 2 — tracked redirect to the correct app-store listing
  • Link 3 — genuinely new installation on an eligible device
  • Link 4 — device advertising or attribution signal
  • Link 5 — first open from the installed app
  • Link 6 — advertiser or measurement-provider attribution decision
  • Link 7 — install postback and offerwall activity record

The app icon is not proof of attribution

Installation proves only that the operating system added the app. It does not prove which advertising source receives credit. Tapjoy’s current support material explains that the advertiser or its measurement provider decides whether the install belongs to the offerwall.

Link 1 — the click must start inside the correct host account

Open the offerwall through the reward site or app where the virtual currency should be credited. RevU and similar providers use a personalized wall supplied through the host. A copied offer URL or another logged-in host account can break the user-to-offer mapping.

Save the pre-install record

Before tapping Install, capture the offer name, provider, host, reward, country, device, deadline, new-user requirement and activity ID. This is the only point where the original terms can be preserved without later ambiguity.

Link 2 — follow the tracked redirect

The store page must be reached through the offer button. Searching the app store manually, opening another advertisement, using a coupon link or clicking the same app through another offerwall can assign the install to a different source.

Do not browse competing ads after the offer click

Mobile attribution often follows a last eligible click or provider-specific model. Another ad for the same app can replace the offerwall’s claim before installation. Keep one offer, one device and one acquisition path.

Link 3 — new-user status is binary

Torox states that a previously installed app is not eligible as a new installation. Deleting the app does not erase the advertiser’s device, account or installation history. A reinstall should not be presented to support as a first install.

Check the whole device history

The app may have been installed months ago, preloaded, used under another store account or restored from a backup. Search the purchase or download history before accepting a high-value install offer.

Match country, operating system and device type

Offer campaigns can target one country, Android or iOS version and device class. Torox prohibits proxies and emulators, while AdGem identifies incorrect geo or device targeting as common eligibility failures.

Do not move the install between devices

Clicking on desktop and later searching the store on a phone can lose the tracked handoff unless the provider supplies an explicit QR or email-to-device method. When such a method exists, use that exact handoff rather than recreating the search manually.

Link 4 — understand the device identifier

Android provides a user-resettable advertising ID for advertising use cases. AdGem documents GAID and IDFA as deterministic signals that can connect the click to the install when they are available and handled correctly.

iOS tracking permission can change the evidence

Apple’s App Tracking Transparency prevents access to IDFA when the user chooses Ask App Not to Track. AdGem states that without ATT authorization, attribution can fall back to less reliable fingerprint or SKAdNetwork paths.

Privacy choice and reward eligibility are separate decisions

The user has the right to refuse cross-app tracking. The practical consequence is that some incentivized install offers may become harder or impossible to attribute deterministically. Do not grant tracking without reading the offer and app privacy disclosures.

Resetting the advertising ID can break continuity

Android’s advertising identifier is resettable. Changing or clearing it between the offer click and first open can remove the stable value expected by an attribution chain. Do not modify privacy identifiers mid-offer merely to troubleshoot.

Link 5 — first open completes the installation event

Open the app immediately from the store page or home screen after the tracked installation. Complete only the explicitly required onboarding step. An installed but never opened app may not generate the conversion event expected by the campaign.

Keep the same app account

If the offer requires a new account, create it during the tracked first session and preserve its advertiser-side user ID. Signing into an old account can invalidate the new-user condition even when the device install is new.

Link 6 — the advertiser owns the attribution decision

Tapjoy states that the advertiser or mobile measurement provider decides which ad network receives credit. The offerwall can submit evidence but cannot always override an attribution record assigned elsewhere.

Link 7 — look for the install activity record

A provider or host can expose Clicked, Installed or In Progress status. AdGem recommends install postbacks so the host can confirm that the user is eligible to continue. Absence of an install record is different from a later milestone being pending.

Do not continue a high-effort milestone blindly

When the offer requires reaching level 30 but the install itself never appears in activity, stop before spending days or money. Ask the provider whether the initial installation was attributed and preserve the answer.

Use the Salvageability Verdict

Classify the failure before taking another action.

  • Salvageable — provider sees the install but the host UI is delayed
  • Disputable — tracked click and new install exist, but attribution was assigned incorrectly
  • Usually irreversible — app was installed before the offer or directly from the store
  • Unsafe to repeat — eligibility is uncertain and a reinstall could create duplicate behavior
  • Stop immediately — the offer asks for a purchase before install attribution is confirmed

A reinstall rarely repairs lost attribution

The first install has already changed the device and advertiser history. Removing the app and trying the same link can turn a missing attribution case into a clear non-new-user case.

Do not switch offerwalls for the same app

Starting the same campaign through another provider can create competing clicks and duplicate claims. Close the original case before considering another offer, and assume the device may no longer qualify as new.

Build the attribution dispute packet

Include the host and provider, offer ID, click time, store arrival screenshot, installation and first-open time, device and OS, country, advertiser account ID, activity status and confirmation that the app had never been installed. Do not reset identifiers or delete the app while the case is open.

Worked direct-store failure

The user sees an offer, closes the wall and searches the app store by name. The app installs successfully but no offer activity appears. Tapjoy’s stated attribution rule makes the direct-store path normally ineligible.

Worked prior-install failure

The app was downloaded on the same device six months earlier and later deleted. A new offer now requires a first installation. Reinstalling cannot restore new-user status, so the user stops before completing paid milestones.

Worked iOS uncertainty

The user follows the offer link on iPhone but denies cross-app tracking. The provider shows the click but no deterministic install record. The user preserves the privacy choice, asks whether an alternative attribution route exists and does not spend money to force the offer.

Worked host-display delay

The offerwall activity contains an install event, but the reward host still shows Not Started. The attribution link reached the provider, so the issue belongs to the provider-to-host synchronization rather than a reinstall.

The install verdict

Continue only when the provider records the install or confirms eligibility. Dispute once when the tracked path and new-user evidence are intact. Stop when the app existed before the offer, the store was opened outside the tracked redirect or a second attempt would destroy the remaining evidence.

Attribution sources checked on July 30, 2026

Provider and operating-system documentation directly supports the click, identifier, new-user and attribution branches.

  • Tapjoy install-not-attributed denial explanation: https://tapjoy.helpshift.com/hc/en/3-offerwall/faq/17-my-reward-was-denied-because-this-app-install-was-not-attributed-to-tapjoy-what-does-this-mean/
  • Torox offer eligibility and new-install rules: https://www.torox.io/ifr/show/21659/5457a07d-1a94-4bfe-b202-996715dcc219/8634
  • Apple App Tracking Transparency: https://support.apple.com/en-us/102420
  • Android Advertising ID documentation: https://developer.android.com/identity/ad-id
  • AdGem web attribution and IDFA/GAID explanation: https://docs.adgem.com/docs/integrate/offer-delivery/pre-built/web-offerwall
  • AdGem install and reward postbacks: https://docs.adgem.com/docs/integrate/reward-mechanism/postbacks-v3
  • AdGem iOS ATT behavior: https://docs.adgem.com/docs/integrate/offer-delivery/pre-built/ios-sdk
Scam-aware reminder

Be careful with websites that promise unrealistic rewards, ask for deposits before withdrawal, or require suspicious wallet connections. Small reward sites should never need your seed phrase.

FAQ

Why was my app install not attributed to the offerwall?

The install may have started outside the tracked link, existed previously, used an ineligible device or lacked the attribution signal expected by the advertiser.

Can reinstalling the app fix attribution?

Usually no. The first installation has already changed new-user status and advertiser history.

Does denying iPhone tracking always invalidate the offer?

Not always, but it can remove deterministic IDFA matching and make some install campaigns harder to attribute.

Should I continue playing when the install is not listed?

No. Confirm the install record before investing time or money in later milestones.

Who decides which source gets the install?

The advertiser or its mobile measurement provider normally makes the attribution decision.

Can I try the same app through another offerwall?

Doing so creates competing attribution and usually does not restore new-user eligibility.

What evidence matters most in a dispute?

The original offer record, tracked click time, direct store handoff, first-install status, first-open time and advertiser account ID.