Fusion Match API is a deeper integration with PureSpectrum surveys than the Fusion Link system. It utilizes the Fusion engine to return respondent-specific survey opportunities.
In the Request of the API, you will specify the locale, respondent demographics, session ID and member ID. In the response, you will receive a list of full-match and/or partial-match surveys for which the respondent qualifies.
The surveys will include fully formed “Fusion Entry Links”, specifically tailored with the correct CPI and maxLOI to target these survey opportunities. If the respondent fails to qualify, they will be sent to other relevant opportunities.
Reasons to use the Fusion Match API:
Know before you send - have clear visibility into whether there are opportunities for this respondent before sending them to PureSpectrum
Higher conversion, more accurate payouts - you will know exactly which price and LOI combination to expect for the respondent. Market prices fluctuate, so sometimes you are missing opportunities, and other times sending at prices that may be too low. No more guesswork!
Give the respondent a choice - you can give them a wide range of low loi or higher priced opportunities. They can choose based on their preferences.
Skip the screener - sending to surveys where the respondent is a full match allows us to skip the screening process in some cases
The Fusion Match API is reserved for top performing publisher partners. To use the Fusion Match API, you will need to request an Access-Token from our Supply Team, and must qualify based on reputation and expected send.
HEADER Parameters
Parameter | Type | Required | Description | Example |
|---|---|---|---|---|
access-token | string | Yes | Token used to identify the authenticity of the user. | "access-token": "$accessToken" |
REQUEST Query String Parameters
Parameter | Data Type | Required | Description | Example |
|---|---|---|---|---|
respondentId | Query String Parameter | yes | Unique respondent ID | respondentId=TestSessionId |
memberId | Query String Parameter | no | Persistent member ID | memberId=TestMemberId |
respondentLocalization | respondent localization (reference) | en_US | ||
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 |
maxNumberOfSurveysReturned | Query String Parameter | no - defaults to 12 | Set the max number of surveys to return in the response, sorted by internal score | maxNumberOfSurveysReturned=10 |
GET https://fusionapi.spectrumsurveys.com/surveys/fusionMatch?memberId=FusionTestMemberId&respondentId=FusionTestSessionId&respondentLocalization=en_US&211=111&212=28&215=114 Host: fusionapi.spectrumsurveys.com access-token: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Response:
HTTP 200 OK
{
"respondentId": "FusionTestSessionId",
"memberId":"FusionTestMemberRespondentId"
"surveys": [
{
"surveyId": 470381,
"cpi": 1.35,
"estimatedLoi": 1,
"ir":47,
"fullOrPartialMatch": "full",
"entryLink":
"https://fusion.spectrumsurveys.com//start-session/1US0135?maxLoi=4&sessiontok
en=FusionTestSessionId&memberid=FusionTestMemberRespondentId&surveyId=470381"
},
{
"surveyId": 450501,
"cpi": 9.38,
"estimatedLoi": 2,
"ir": 33,
"fullOrPartialMatch": "full",
"entryLink":
"https://fusion.spectrumsurveys.com//start-session/1US0938?maxLoi=5sessiontok
en=FusionTestSessionId&memberid=FusionTestMemberRespondentId&surveyId=450501"
}
]
}
We will return a value “ir” which is the PureSpectrum after targeting Incidence (Conversion) Rate. This is either a measured statistic, or based off of a buyer’s prior performance in a country.
Best Practices
API Request Frequency - The expected frequency of API requests should correlate to the available respondents you have at a given time e.g. if there are 20 respondents interested in taking a survey, 20 requests (one for each respondent) should occur. Note: our system has a maximum in place of 500 requests per minute.
memberId - Passing in a value for “memberId” in the Request Params is recommended as it allows us to retrieve the respondent profile if it exists in our system, and remove any attempted surveys from the response.
One-time Entry Links - given the links in the API response are generated to provide a specific respondent an opportunity, they should be treated as a one-time use entry link.
Utilize S2S Postbacks - Given the payouts will likely be variable, it’s best to implement S2S postbacks to confirm the value of Completes as they occur in real time.
Passing in Profiling Demographics - To maximize the quality of matches for a respondent, we recommend passing in as many demographic variables as possible. At a minimum, we expect age, gender and zipcode. Please refer to Profiling - Appending Qualifications for further details.
Time Difference between API request and session start - The delay between the API request being made and the session beginning should be at a minimum (less than 5 seconds). The longer the delay between the API response providing the entry link and the respondent receiving the entry link to enter Fusion, the more likely the opportunity is to be no longer available for them.
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.
In order to get started, you will need to get login credentials from the PureSpectrum team.
Portal Access
Once you have you credentials, you can begin setting up your account by logging into the portal.
https://fusionadmin.spectrumsurveys.com/dashboard/redirect-settings
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
Questions
If any questions come up during the account setup process, please reach out to globalsupply@purespectrum.com