...
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 Parameters (in Query String)
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 |
| Code Block |
|---|
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 |
...
| Info |
|---|
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 rwqyests 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 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.
...