Session content:
– How to combine minimum and maximum quotas.
– Quota evaluation.
– Using multi codes quota.
– Quota frame evaluation.

ISO 27001 is an international standard for managing information security, and a must-have for any organization that is entrusted with large amounts of user data, as we are here at NIPO.

Following an intensive 5-day audit which scrutinized both our Amsterdam and Madrid offices, we are pleased to share the news that NIPO’s ISO 27001:2013 certification has once again been extended. Performed by SGS, this audit was fully focused on NIPO’s ISMS.

NIPO has been certified to ISO 27001:2013 since 2016. We have retained this by undergoing re-certification audits every three years, along with two additional annual surveillance audits in between.

Continuous improvement is at the heart of both the ISO 27001 certification and NIPO. In line with this, we are now working on all the measures necessary to conform to the latest iteration, ISO 27001:2022, before October 2025.

Alongside ISO certification, we also implement many additional security measures to ensure every Nfield customer can use our market research platform with confidence. To learn about these, see Your data is secure with Nfield: here’s how.

ISO certificate

We recorded an additional session on quota, as an extension to the session wherein we explained the basics. In this webinar we explain the new feature of the *QUOTA command that can be used in ODIN survey scripts, allowing the quota in the Nfield Manager to be created automatically once the script is uploaded.

Session content:
– How to set up quota.
– How to check quota in the survey script.
– Handling quota overshoot.
– Changing quota targets during fieldwork.
– Changing quota structure during fieldwork.

Integrating Nfield with your own system(s) can significantly enhance your organization’s market research capabilities, and the Nfield API enables this to be a seamless experience. Here is everything developers need to know about Nfield integration via the Nfield API.

Essential preparation

Before diving into the integration process, let us start with a few basics that underpin successful integration.

1. Understand REST API technology:
   REST (Representational State Transfer) is an architectural style that uses HTTP requests for communication. The Nfield API is built on this technology, so understanding how REST APIs work is crucial. Check out this introduction to REST APIs to get up to speed.
   
2. Learn how your researchers are using Nfield Manager:
   Nfield Manager is the interface through which researchers instruct the Nfield platform. To provide the integration capability these people need, you need to get to know how they work with Nfield Manager. Observing and discussing their workflow will provide you with essential insights into the tasks you need to automate and the endpoints you need to connect.
   
3. Check out the Nfield API help page:
   Region-specific Nfield API help pages provide detailed documentation on endpoints, authentication methods, request formats, and more. Be sure to refer to the correct help page for your region:

Your region	Nfield API help page
Asia Pacific	https://apiap.nfieldmr.com
America	https://apiam.nfieldmr.com
China	https://apicn.nfieldcn.com
Europe	https://api.nfieldmr.com

Starting the integration process

Here’s how to initiate your Nfield API integration process by setting up authentication and understanding key endpoints.

1. Authentication:
   There are two main methods for achieving this with the Nfield API:
   
   Basic Token:
   The easier, and more straightforward method is to use a basic token, which authenticates API requests by being included in the HTTP headers. You can also see a practical example in our video of automating quota progress reports with the Nfield API using Microsoft Power Automate.
   
   Bearer Token:
   The second method involves using OAuth 2.0 for authentication. This method is more complex but offers enhanced security features. You will need to obtain an access token through an OAuth flow, which will then be required in the header of your API requests. For more information, see What is Bearer Token and How it Works?
   
2. Endpoints:
   The Nfield API is extensive and covers all the manual actions that can be performed in Nfield Manager. These include creating, updating, and managing surveys, managing respondent data, data collection processes, managing user accounts, and monitoring survey progress. Essentially, any task that can be done manually in Nfield Manager can be automated using the Nfield API. This comprehensive coverage enables full integration and automation of your organization’s market research processes.
   
   For detailed specifications and a full list of available API endpoints, refer to the Nfield Help Page for your region, as shown in table above.
   
3. Making API calls:
   Use HTTP methods such as GET, POST, PUT, PATCH and DELETE to interact with endpoints. Make sure your requests include the necessary headers – such as the Authorization header – with your access token and Content-Type header for JSON data.
   

Figure 1: An example in Postman for getting surveys from Europe region.

4. Handling Responses:
   The API will mostly return responses in JSON format, so you need to make sure your application is able to parse these. (A small percentage of endpoints will return responses as binary files.) Pay attention to the status codes to ensure both errors and successes are managed effectively.

Best practices for integration

Adhering to best practices will help make your integration more efficient and reliable.

1. Start small:
   Begin with basic API calls to familiarize yourself with endpoints and responses. For example, start by retrieving a list of surveys before moving on to more complex operations like creating or updating surveys.
   
2. Error handling:
   Implement robust error handling in your integration to manage scenarios like expired tokens, invalid requests, or server errors. This will ensure your integration is resilient and can recover gracefully from any issues.
   
3. Testing:
   Thoroughly test your integration in a development environment before deploying it to production. Use test surveys and respondents to ensure your API calls are functioning as expected without affecting live data.
   
4. Optimized data retrieval:
   When downloading survey data, avoid downloading the entire dataset each time. Instead, implement logic to download only the differences (incremental updates) since the last download. This practice reduces the load on both your system and the Nfield API, ensuring efficient data transfer.
   
5. Respect API limits:
   Avoid making unnecessary frequent API calls to prevent overloading the system. Follow Nfield’s acceptable use policy, which provides guidelines on optimal API usage and rate limiting. Adhering to these guidelines ensures fair usage and system stability for all users.

Documentation and support

To stay updated and efficiently resolve issues, make effective use of available documentation and support resources.

1. Regular updates:         
   Make sure you stay informed about system updates, new features, and changes to the Nfield API. Ask your domain administrator to set up an email auto-forward from Nfield’s update notifications. This will keep you up to date on the latest developments and ensure you do not miss any essential information.
   
2. Keep the Nfield API help page to hand:
   Regularly refer to the Nfield API help page for updates and clarifications. It is a vital resource for understanding the endpoints, request formats, and best practices.
   
3. Utilize support resources:
   Take advantage of the various support resources provided by Nfield, such as reach out to technical support and view Academy session recordings. These resources provide valuable assistance and insights from other developers and Nfield experts. Also an Nfield SDK has been created by Nfield users on Github.

Conclusion

Integrating Nfield with your system via the Nfield API can streamline your market research operations and provide valuable data insights.

By preparing adequately, understanding the API’s fundamentals, and following best practices, you can ensure your integration is a success.

Make the most of Nfield’s capabilities by leveraging all available resources, such as Nfield API manuals and your own researchers’ expertise.

Enhance your integration’s efficiency and performance by adopting optimized data retrieval methods and respecting API usage policies.

Stay up to date on system changes to continue getting the absolute best out of Nfield.

NIPO is pleased to announce the introduction of its survey-level data retention policy feature. Designed to simplify the management of long-running trackers, or waves, this feature can be set to automatically clean out Online survey data after a specified number of days.

• Never (default): no survey data will be automatically deleted.
• 30 days: automatically deletes any survey data that’s more than 30 days old.
• 60 days: automatically deletes any survey data that’s more than 60 days old.
• 90 days: automatically deletes any survey data that’s more than 90 days old.

These settings are in the Nfield Manager under the Setup survey/Retention tab. They can be configured separately for each survey, so storage practices can be tailored to specific project needs.

Benefits of implementing a survey-level data retention policy

Setting and adhering to data retention periods aids compliance and data governance, while also simplifying long-running trackers and mitigating risks associated with prolonged data storage and privacy breaches.

• Compliance: Adhering to regulatory requirements such as GDPR (General Data Protection Regulation) is crucial in today’s data-driven landscape. Establishing and enforcing appropriate data retention periods ensures compliance with these regulations, thereby mitigating legal risks.

• Data governance: Effective data governance practices demand clear policies around data retention. By defining specific retention periods, organizations can maintain data integrity, optimize storage resources, and streamline data lifecycle management processes.
  
• Risk management: Implementing proper data retention practices is essential for mitigating risks associated with prolonged data storage and potential privacy breaches. By automatically removing outdated data, organizations can reduce the likelihood of security vulnerabilities and maintain compliance with data protection laws.
  
• Simplifying long-running trackers: Seamlessly managed trackers clean-up eliminates the effort and hassle of manually removing outdated information. Long-running trackers can stay dedicated to a single survey, while long-running surveys remain organized, focused, clutter-free and up-to-date, without manual intervention.

Which data is automatically removed?

Based on the selected retention period, the following data will be removed automatically:

• Interview data (e.g. .dat, o-file, paradata, audit log) that has not changed for the specified number of days.
• Sample data for this interview (untouched sample data is not deleted).
• Survey packages (script, media files, settings) that have been superseded by a newer package for more than the specified number of days (the latest package is never deleted).
• Quota frames that have been superseded by a newer quota frame for more than the specified number of days.

Important notes

1. The default setting is NEVER. Nfield users are always in control. Data will never be automatically removed unless a specific retention period has been set.
2. Once data has been removed, it is permanently deleted along with its associated artifacts (scripts, data, quotas, media files, etc.), and cannot be restored.
3. This feature is currently only available for Nfield Online surveys.

Elevate your research game with Nfield

Survey-level data retention policy is just one of the many tools Nfield equips you with to take your market research to the next level. Say hello to streamlined processes, enhanced efficiency, and control over your data retention policies.

In one of the previous “scripting problem of the month” sessions we looked at how surveys end. In this NIPO Academy we will look at how surveys start. How you maximize the number of real respondents and keep bots out.

Already for some time you can limit the access to different surveys to one or more groups of users on your Nfield domain. But until recently the configuration of this feature was only possible through the API. Now that the configuration is available through the Nfield Manager as well, it is time for a proper introduction of the survey access options.

The new feature, the *REQUEST command, is an extension and replacement of the GETDATA command and meant to connect with external API’s. For instance, to connect with a database.

Most online market research surveys begin with an email invitation to participate. If these emails don’t reach their intended recipients and attract their attention, your survey is going to suffer. Successful delivery, which means landing in each recipient’s inbox, not their spam folder, is never guaranteed. And being recognized by them as a legitimate message, which should be opened, is essential to avoid being clicked straight into the trash.

It may sound a bit like a game of chance, but you can take steps to tip the odds firmly in your favor.

To protect ordinary people from being bombarded with huge amounts of unsolicited and undesirable emails which flood the internet every day, email service providers and email apps implement a range of checks on each item before allowing it to reach an inbox. The best practices outlined in this article will help your emails to pass these checks.

1. Create and authenticate custom email domains

The domain your survey invitation emails come from matters. Recipients are more likely to open emails sent from a domain they recognize and feel they can trust. Nfield can easily be configured to send from custom domains as necessary. (Of course, you need to send from a domain you are legitimately entitled to use and have the credentials for – you can’t just borrow any domain you feel like using!)  

To ensure each custom domain passes relevant delivery checks, you should set up email authentication protocols such as DMARC (Domain-based Message Authentication, Reporting, and Conformance), DKIM (DomainKeys Identified Mail), and SPF (Sender Policy Framework). This is something for your email administrator to take care of.

These protocols authenticate emails to confirm they are legitimately being sent from the domain they appear to be from, effectively removing one of the reasons that emails get flagged as spam.

Once these protocols have been set for a custom email domain, please contact our support to connect this domain to Nfield.

2. Obtain consent from respondents

Obtaining consent to email the people you want to invite to your online survey is important for various reasons. For a start, your emails won’t come as a surprise, so they’re less likely to be suspicious and bin them without opening, or report them as spam. Either of these actions will be unhelpful to both your survey response rate and your domain reputation.  

Aside from this, obtaining recipient consent to include them in a distribution list is both a best practice and a legal requirement under the General Data Protection Regulation (GDPR). Compliance with GDPR demonstrates your commitment to respecting individuals’ privacy rights and strengthens trust between your organization and the survey respondents you rely upon. By securing explicit consent, you not only uphold ethical standards but also mitigate the risk of non-compliance penalties. Prioritizing consent as part of your email outreach strategy aligns with GDPR’s principles of transparency and accountability, which fosters a positive relationship with your audience.

Read more about EU GDPR specifications.

3. Validate email addresses

Sending survey invitation emails to addresses that don’t exist results in hard bounces that reduce your delivery rate and damage your email reputation. Even when you think you’ve done everything right, invalid addresses can still get into your system through people accidentally mistyping or deliberately providing false information.

You can flush out bad email addresses by using validation tools (such as Emailable or ListWise). Maintaining a clean and validated distribution list will return higher delivery rates and keep your reputation intact.

4. Enable easy opt-out

Even if recipients have consented to being on your distribution list, they have the right to change their minds. It is important that every email contains an unsubscribe link through which recipients can easily manage their preferences. Any requests to opt-out need to be honored promptly to avoid reputational damage caused by unwilling recipients failing to open emails, and possibly reporting them as spam. If you continue to contact people who’ve opted out, they will also develop negative feelings towards the brand being represented.    

Enabling easy opt-out demonstrates respect for recipients’ choices and helps preserve your email sender reputation. Nfield supports customizable unsubscribe options, allowing you to tailor the process to align with your branding and compliance requirements.

Alongside this, Nfield provides a blacklist facility where you can keep track of email addresses which have unsubscribed, had delivery problems, been flagged as fake or should not be contacted for any other reason. These blacklists are compiled at domain-level, as another tool for helping you protect your email reputation.

5. Assess your spam score before sending

The content and formatting of emails is another factor that can easily trigger spam flags if you’re not careful. Before sending out your email invites, you should evaluate them by using a spam score checker (such as mail-tester) that analyzes subject lines, content, formatting and other attributes that may be scrutinized by the “spam police”. This will help you avoid another deliverability pitfall, while resulting in emails which appear more genuine to the people you need to participate in your survey.

Helping your online surveys succeed

Following best practices for sending invitation emails is essential for online survey success, and Nfield has a number of in-built features to help you do this. For more advice on building a robust email reputation, and to find out why this matters, check out our related articles

• How email reputation impacts market research success
• How to build a good email reputation and deliver more survey invitations

This session is an extension on NIPO Academy #24 (fieldwork report) and #35 (custom reporting) wherein we will show you how to create your own BI report.

This session concentrates on the different scripting debugging techniques and processes Nfield offers, by introducing a new feature called Simulate Interviews. This feature is a replacement and important enhancement on the generate dummy data option in the NIPO ODIN Developer.

Why spend valuable time on routine tasks that can easily be automated? If you’re using Nfield for Online and CAPI surveys, you can reduce manual workload by hooking up with Microsoft Power Automate. Nfield’s API enables seamless integration with this user-friendly automation tool, without the need for any coding.

Integrating Microsoft Power Automate with Nfield can speed up your operations, reduce errors and omissions, and keep communications flowing, while freeing your people to focus on applying their expertise.  

Here are five examples of what Nfield and Microsoft Power Automate can achieve together.

1. Keeping clients informed with scheduled quota progress reports

Providing regular updates on project progress is good for client relationships, and demonstrates commitment to transparency and timely communication. But doing this takes time out of your day and can easily be forgotten.

With Microsoft Power Automate, you can schedule automated delivery of Nfield quota progress tables to clients, as often as you choose.

Watch our video demonstration of how to set up automated Quota Progress Reports using Microsoft Power Automate

2. Nurturing respondent relationships

Survey respondents are the lifeblood of market research, so keeping them onside is crucial. Simple things like sending thank you notes for completing surveys goes a long way to building loyalty.  

Microsoft Power Automate allows you to automate this. Reminding your respondents that their contribution is valued, and encouraging them to continue participating, without any members of your team having to disrupt their schedule.

3. Efficiently assigning addresses to interviewers

For CAPI surveys, assigning addresses to interviewers is an essential routine task. But it takes time that can be spent on other things.

Microsoft Power Automate can take care of this work by automatically assigning new addresses to each of your Nfield CAPI interviewers as required, ensuring fair distribution of workload and optimizing how each field worker is used.

4. Keeping your research team updated in real time

The faster your research team are informed, the faster they can get on with the next stage of their work.

Microsoft Power Automate can be hooked up with Nfield to notify them immediately when a survey quota target is met.

5. Ensuring survey data is immediately backed up

Everyone knows the importance of back-ups, which is why these should never be left to chance. 

Microsoft Power Automate can initiate backup processes the moment fieldwork is complete. Ensuring this crucial task doesn’t get forgotten, while lessening your team’s post-fieldwork workload, so they can focus their attention on analysis.

Integrating Nfield with Microsoft Power Automate, via the Nfield API, enables you to optimize your market research operations in many different ways. From enhancing various communications to automating routine tasks, this powerful combination allows you to focus on what matters most – extracting meaningful insights from your data.

Automation of routine tasks is a great way to improve efficiency in any line of work. For market research companies conducting Nfield Online and CAPI surveys, this is easily achieved through integration with codeless tools such as Microsoft Power Automate and Zapier.

The beauty of no-code automation tools is they don’t require specialist expertise to set them up. All that’s necessary is an amount of familiarization with the tool and how it integrates with Nfield Manager via Nfield’s API. For the purpose of this demonstration, we’re showing how sending reports to clients can be automated using Microsoft Power Automate. This task is one of the Five ways no-code automation can improve efficiency in market research operations. 

Essential preparation

Here’s what’s necessary for integrating Microsoft Power Automate with Nfield:

• Microsoft Power Automate Premium Subscription: this provides access to advanced features such as HTTP connections.
• Basic understanding of Microsoft Power Automate: see Get started with Power Automate – Power Automate | Microsoft Learn or A Beginner’s Guide to Automation Using Power Automate
• Familiarity with Nfield Manager: in order to understand specific tasks and endpoints involved in the integration process.
• Access to the appropriate Nfield API help manual: refer to the manual for your region
  

Your region	Nfield API Manual
Asia Pacific	https://apiap.nfieldmr.com
America	https://apiam.nfieldmr.com
China	https://apicn.nfieldcn.com
Europe	https://api.nfieldmr.com

A practical example: automated sending of quota progress reports

Our video follows every step of the process of setting up automated sending of quota progress reports from Nfield Manager using Microsoft Power Automate:

1. Log in to Power Automate (0:00 to 0:25)

2. Create a new flow with a schedule trigger* (0:25 to 1:05)

3. Create an HTTP connection for Nfield API authentication (1:05 to 2:54)

4. Extract and store authentication token (2:54 to 4:09)

5. Create another HTTP connection to retrieve the quota table (4:09 to 7:11)

6. Send an email with the quota table (7:11 to 8:12)

_{*In this example, reports are being scheduled to go out daily at 9am.}

A common problem in online surveys is that respondents close their browser before the interview status is set, resulting in faulty interview counts and quota overshoot. In this NIPO Academy session we will talk about how to prevent this and how the new *ENDPAGE can help with this.