MatchAPI Testing and Validation Guide

Goal: Quickly validate redirects, S2S callbacks, and live traffic with minimal test noise.

1. Before You Begin

Proceed only when all items below are true:

Redirect URLs configured

1.1. All redirect URLs are entered (Complete, Terminate, Overquota, Quality, etc.).
1.2. Each redirect points to the correct environment (test vs. production).
1.3. Need help? See:
→ Redirect Setup Guide
https://purespectrum.atlassian.net/wiki/spaces/PID/pages/2506817611/Userflow+-+Respondent+Redirects#Reviewing-Our-Redirect-Links

Variable mappings validated

2.1. All incoming and outgoing variable mappings are configured.
2.2. Variable names match the entry link variables (unless intentionally different).
2.3. Need help? See:
→ Incoming & Outgoing Variable Mapping Guide
https://purespectrum.atlassian.net/wiki/x/FgB1lQ

Tracking / S2S behavior decided

3.1. S2S callback for completes is set up and points to the correct endpoint.
3.2. If using S2S for reconciliations, those callbacks are also set up.
3.3. Need help? See:
→ S2S Postback Setup Guide
https://purespectrum.atlassian.net/wiki/spaces/PID/pages/2507178031

2. Step 1: Generate Your Test Entry Link

Your testing location should match the country/localization in the API call

If you are testing a different market than your current location, use a Test Code with isTestRequest to bypass security.

Get your Test Code from Fusion Portal

1.1. Open the Fusion portal.
1.2. Locate the field “Fusion Match API test parameter”.
1.3. Copy the field value.
1.4. This value is your Test Code.

Build the Fusion Match API request

2.1. Prepare the following parameters:
- memberId = your member ID.
- respondentId = a test respondent ID.
- respondentLocalization = locale (e.g., en_US).
- isTestRequest = your Test Code from step 1.
2.2. Example request:

https://fusionapi.spectrumsurveys.com/surveys/fusionMatch?memberId=TestMembID040825&respondentId=TestRespID040825&respondentLocalization=en_US&isTestRequest=i3nfa68

isTestRequest is an input into the API call.
It should be set to the Test Code from the Fusion portal.

Call the API and capture the entry link

3.1. Send the API request.
3.2. In the API response, locate the returned entry link URL.
3.3. Confirm the URL includes:

Your memberId and respondentId .
A one-time isTestUrl parameter.

3.4. Copy one entry link from the response for testing.

isTestUrl is an output from the API.
It appears in the test entry link (for example: &isTestUrl=Ss6oDjuWj5).

Example test entry link
https://fusion.spectrumsurveys.com/start-session/123US0020?langIsoCode=en&surveyId=47931314&ts=1773229667606&sessiontoken=TestID1234&memberid=testmember123&matchApiId=6sO1ui7z5ti94ekvl_igS&isMatchApiPartial=1&sPlacement=2&surveySig=a188876647a40e45557d5abb0751be3c3ec9c3776de9931165a1bfd4cba0400f&isTestUrl=Ss6oDjuWj5
Repeat for each new test

5.1. For every new test start from your panel, call the Fusion Match API again.
5.2. Use the new entry link returned (with a new isTestUrl value).
5.3. When using a Test Code, you should see screener questions every time you test.

3. Step 2: Run the Test From Your Panel

In your panel management software, set the full test entry link from Step 2 as the survey start URL.
Launch a test respondent into the survey using that link.
Complete the screener questions.
In the test survey, select the outcome you want to validate:
4.1. Complete
4.2. Terminate
4.3. Overquota
4.4. Any other configured outcomes
Click the submit button to send the respondent to the redirect.

4. Step 3: Verify Results

For each outcome, verify both the redirect and (if applicable) the S2S callback.
1. Use the table below as your checklist:

Outcome selected in test survey	Expected redirect behavior	Expected S2S behavior

Outcome selected in test survey	Expected redirect behavior	Expected S2S behavior
Complete	Lands on Complete redirect URL	Complete S2S callback fires
Terminate	Lands on Terminate redirect URL	No S2S callback
Quality	Lands on Quality redirect URL	No S2S callback
NoSurveys	Lands on NoSurveys redirect URL	No S2S callback
Blacklist	Lands on Blacklist redirect URL	No S2S callback

For each outcome:
2.1. Check the browser lands on the correct destination page / URL.
2.2. If S2S is configured, confirm in your panel or tracking logs that the correct callback fired (or did not fire, based on your setup).
2.3. Repeat tests until all outcomes behave as expected.

5. Step 4: Soft Launch to Live Users

Configure live entry links using the same variable mapping that you validated in testing.
Ensure test-only parameters are removed from live links where appropriate (e.g. no isTestRequest, and only use isTestUrl when intentionally testing).
Soft launch to a small audience (recommended: 50–500 users).
Monitor early traffic:
4.1. Incidence and conversion.
4.2. Redirect URLs firing as expected.
4.3. S2S callbacks landing correctly.
4.4. Any blacklisting or unexpected behavior from non‑real respondents.

Adjust mappings, redirects, or S2S callbacks if issues appear, then expand to full traffic.

6. Support

If you need help reviewing your setup, test results, or initial traffic, contact:

Email: globalsupply@purespectrum.com
(mailto:globalsupply@purespectrum.com)