The Fusion Offerwall gives you all of the benefits of the Fusion match API, without the hassle of integrating an API. If you can support variable payouts, and can send respondents to a link, the Fusion Offerwall is a great fit for you.
Respondents are presented with up to 12 options to choose from, at varying price points and survey lengths. The options are custom tailored for the respondent, so that they aren’t presented options they don’t qualify for, or have already attempted.
Reasons to use the Fusion Match API:
All the benefits of the Fusion Match API
Respondents can choose the right survey opportunity for them
Pages are translated for the respondent’s appropriate localization
No need to integrate an API
Getting Started
To use the Fusion Offerwall, you must have the feature enabled for your account.
Redirects
The Fusion Offerwall can be configured, such that a respondent is redirected back to the Offerwall, or back to a URL of your choosing. We can offer a different configuration for Completes, and non-Completes.
For example, if someone completes a survey, we can redirect them back to a URL of your choosing, but if they do not complete, we will redirect them back to the Offerwall.
If you choose to redirect the respondent back to the offerwall, they are presented with an appropriate message.
In case of complete, they will see a localized translation of: You completed the survey and will be credited! Would you like to try another?
In case of non-complete, they will see a localized translation of: This survey wasn't a good fit! Would you like to try another?
Postbacks and Registering Completes
In order to support the Fusion Offerwall, you must accept a Server to Server postback. Documentation may be found here: Fusion: S2S Postbacks
You must support dynamic payouts, as respondents may take surveys with different payouts.
Entry Links
Entry links are comprised of a publisher ID, country code, currency name, conversion rate, unique session ID, device/member ID.
Here is an example entry link: https://offerwall.spectrumsurveys.com/publisher_offers?publisherId=0&countryCode=en_US&respondentId=TestSession&memberId=TestMember¤cy=Gems&conversion=500
Parameter | Data Type | Required | Description | Example |
|---|---|---|---|---|
conversion | Query String Parameter | No | The conversion rate can be specified dynamically. If none is specified, the system uses your account default. | conversion=500 |
currency | Query String Parameter | No | The currency name can be specified dynamically. If none is specified, the system uses your account default. | currency=Gems |
publisherId | Query String Parameter | Yes | The publisherId is your unique publisher ID. | publisherId=1 |
countryCode | Query String Parameter | Yes | The country code is the localization of the respondent. 2 letter iso language code, followed by 2 letter iso country code | countryCode=en_US |
respondentId | Query String Parameter | yes | Unique respondent ID | respondentId=FusionTestSessionId |
memberId | Query String Parameter | no | Persistent member ID | memberId=FusionTestMemberId |
profile data | Query String Parameter | no | The information stored in your system related to the respondent profile. See “Passing in Demographics” | 211=111&212=111&229=90403 |
Passing in Demographics
To maximize the quality of matches for a respondent, we recommend passing in as many demographic variables as possible. At a minimum, please refer to Fusion: Appending Qualifications
We highly encourage passing in a memberId of the respondent in the Request Params. Doing so allows us to retrieve the respondent profile, and remove any attempted surveys from the response.