Quick Fixes for Alchemer Community Survey Errors

This guide outlines how to resolve common issues when importing Alchemer surveys into the Fuel Cycle platform.

Survey Import Errors

Symptom

You receive an “Import Failed” message when importing a survey.

Common Causes

• Redirect links are:
  • Missing
  • Incorrect
  • Insecure (http instead of https)

How to Fix It

• Use the correct redirect link.
• Always include required survey programming.
• Ensure the redirect uses https.

Refer to Create a Recruitment/Screener Survey in Alchemer for setup instructions.

Required Redirect Configuration

Qualified Responses

At the end of your survey, include this redirect link:

https://util.fuelcyclecore.com/util/surveyGizmo/redirectProxy

For UK and Canadian surveys, use .uk or .ca instead of .com.

Verify:

• Action logic is applied on the final page.
• The URL is secure (https).
• Fields to pass:
  • redirect_url
  • qualified: true

Disqualified Responses

Use the same redirect link for disqualified logic. Ensure:

• Skip/disqualify logic is set on screening questions.
• Redirect and field-passing match the qualified setup.
• Variables passed include redirect_url and qualified: false (if needed).

Missing Member P2 Data

Symptom

The expected P2 data is not appearing in your survey results.

Troubleshooting Steps

1. Is the P2 point configured to push to Alchemer?
2. Are all question sources present and linked?
3. Did you push the P2 point before launching the survey?
4. Is each question set up with the correct type?
   • Radio/Multi-select → Quantitative
   • Open text → Qualitative
   • Grid questions → Grid

Best Practices

• Test all surveys after attaching them to a community activity using a test account.
• QC any new P2 points before launching.
• Always start with a copy of the base survey to retain proper configuration.

Getting Help

For additional support, contact Fuel Cycle Customer Solutions:

1. Open the Help widget from your community moderator dashboard.
2. Submit a “Feature not working as expected” ticket.
3. Attach relevant screen recordings, screenshots, or files.