...
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 |
String |
yes | Unique |
session ID | respondentId=TestSessionId |
memberId |
String |
yes | Persistent member ID | memberId=TestMemberId | ||
respondentLocalization | String | yes | respondent localization (reference) | en_US |
profile data |
String |
no | The information stored in your system related to the respondent profile. See “Passing in Demographics” | 211=111&212=111&229=90403 | ||
ipAddress | String | no | respondent IP address | ipAddress=187.112.108.180 |
userAgent | String | no | respondent user agent |
maxNumberOfSurveysReturned
Query String Parameter
userAgent=Mozilla%2F5.0%20(X11%3B%20Linux%20x86_64)%20AppleWebKit%2F537.36%20(KHTML%2C%20like%20Gecko)%20Chrome%2F126.0.0.0%20Safari%2F537.36 | ||||
maxNumberOfSurveysReturned | Integer | no | Set the max number of surveys to return in the response, sorted by internal score (defaults to 12) | maxNumberOfSurveysReturned=10 |
hashed_id | String | no | Provide a hashed email ID to further deduplication efforts | hashed_id=f20f15cd0d600687ec66007f69adeb5ce4fa0d5a4335209d8ba6b5df01de379f |
Code Block |
---|
GET https://fusionapi.spectrumsurveys.com/surveys/fusionMatch?memberId=FusionTestMemberIdTestMemberId&respondentId=FusionTestSessionIdTestSessionId&respondentLocalization=en_US&211=111&212=28&215=114&maxNumberOfSurveysReturned=10&ipAddress=187.112.108.180&userAgent=Mozilla%2F5.0%20(X11%3B%20Linux%20x86_64)%20AppleWebKit%2F537.36%20(KHTML%2C%20like%20Gecko)%20Chrome%2F126.0.0.0%20Safari%2F537.36&hashed_id=f20f15cd0d600687ec66007f69adeb5ce4fa0d5a4335209d8ba6b5df01de379f Host: fusionapi.spectrumsurveys.com access-token: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx |
...
Code Block | ||
---|---|---|
| ||
{ "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 ensessiontoken=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 en5sessiontoken=FusionTestSessionId&memberid=FusionTestMemberRespondentId&surveyId=450501" } ] } |
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. |
...
Basic Workflow
Identify a user interested in taking a survey
Hit the API endpoint with that specific user's information (their member ID, unique session ID, profile data, etc.)
The URLs returned in the API response are specific to that user, therefore you can choose to send that user to one of the options
If the respondent enters our system via any one of the entry links returned, that API response should no longer be used and a new response should be generated should that respondent want to take another survey.
...
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. Most partners average around 30 per minute. Note: our system has allows a maximum in place of 300 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.
respondentId - Passing in a value for “respondentId” is a requirement so that we can properly generate an entry link to Fusion, however the value of this is determined on your end. If you would like to be able to track specific transactions on your end, you will want to ensure this value is unique before providing the entry link to the respondent.
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.
...
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.
ipAddress and userAgent fields - To improve the identification of respondents' Research Defender (RD) device IDs, especially for new participants who have not previously been routed into Fusion, it is recommended to pass these values for all respondents. Providing these values, we can enhance the accuracy of deduplication and perform standard Research Defender checks more effectively. Note: in order for us to make this check, both fields are required to be passed in.
...
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.
...