Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 12 Next »

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 country, respondent demographics, member ID, and psid (if available). In the response, you will receive a list of full-match and partial-match surveys that the respondent qualifies for.

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.

Parameter

Data Type

Required

Description

Example

access-token

Header

yes

Token used to identify the authenticity of the publisher requesting survey list

"access-token": "$accessToken"

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

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.

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.

  • No labels