Fusion Offerwall

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.

The Fusion Offerwall is mobile responsive and fast to load.

Reasons to use the Fusion Offerwall:

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
You are redirecting respondents from a native app or mobile game

User Experience

The Publisher Offerwall will be displayed as below to a user. It can be presented as a new webpage, within an in-app browser, or in an iFrame.

Publishers define the reward conversion rate and currency name that is displayed to the respondent.

Rewards are converted from USD based on a conversion rate included in the link (see Entry Links). it is important to factor in your costs when determining your conversion rate.

Once a user selects the offer, they will be asked a few screening questions to determine the best survey fit and will then be sent to the best match survey offer where they are eligible

All completes are handled through S2S callbacks and not through redirects.

Getting Started

To use the Fusion Offerwall, you must have the feature enabled for your account.

In order to integrate the Fusion Offerwall, you must be able to:

Accept S2S postbacks (API calls)
Generate and store a unique transaction ID for each respondent transaction (session)
Accept multiple completion S2S callbacks for one transaction id

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: Security - S2S Postbacks

You must support dynamic payouts, as respondents may take surveys with different payouts.

We will send a postback for each completion, using a unique Survey ID (Completion ID).

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&currency=Gems&conversion=500

Parameter	Data Type	Required	Description	Example

Parameter	Data Type	Required	Description	Example
conversion	Query String Parameter	No	The conversion rate (multiplier) can be specified dynamically. If none is specified, the system uses 100 as a default.	conversion=500
currency	Query String Parameter	No	The currency name can be specified dynamically. If none is specified, the system uses Credits as a default.	currency=Gems
publisherId	Query String Parameter	Yes	The publisherId is your unique publisher ID.	publisherId=1
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
hashed_id	Query String Parameter	no	Provide a hashed email ID to further deduplication efforts	hashed_id=f20f15cd0d600687ec66007f69adeb5ce4fa0d5a4335209d8ba6b5df01de379f

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 Profiling - 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.

Self Service Setup

Setting up a Fusion account can be done in a matter of minutes if you have all of the required information. This section outlines what is needed to set up an account.

Portal Access

Once you have you credentials, you can begin setting up your account by logging into the portal.

SupplierRouterFrontend

Next Step

The rest of the documentation will take you through your account setup.

Userflow - Inbound and Outbound Parameters

Profiling - Appending Qualifications

Userflow - Respondent Redirects

Security - S2S Postbacks

Security - IP Whitelisting

Fusion Testing

Questions

If any questions come up during the account setup process, please reach out to globalsupply@purespectrum.com