Blocked Requests

🛑 Handling Blocked Requests

To prevent losing responses when requests are blocked (e.g., by ad blockers or browser settings), the Quality Tools wrapper detects these blocked requests. It then assigns a default low score and marks the participant with a generic participantId of Request-Blocked.

• This helps maintain data integrity when external factors block requests.
• It prevents the loss of responses by assigning a default score.
• Ensures that blocked requests do not interfere with overall scoring and analytics.

If a request is blocked, the Quality Tools will:

• Assign Request-Blocked to string attributes.
• Return a device score of 0 for all device numeric metrics.
• Return true for the isDuplicate property.
• Return No Data for survey history metrics (e.g., manualISQRate) and lastSurveyTaken.
• Return 0 for quality checks (e.g., brandFamiliarity).

Response Example

{
  "participantId": "Request-Blocked",
  "deviceScore": 0,
  "country": "Request-Blocked",
  "subdivision": "Request-Blocked",
  "lastSurveyTaken": "No data",
  "isDuplicate": true,
  "surveyId": "Request-Blocked",
  "averageDeviceScore": 0,
  "lowestDeviceScore": 0,
  "totalSurveys": 0,
  "deviceFailures": [
    "Request-Blocked"
  ],
  "completionRate": "No data",
  "duplicationRate": "No data",
  "failureRate": "No data",
  "qualificationRate": "No data",
  "manualISQRate": "No data",
  "automatedISQRate": "No data",
  "osqRate": "No data",
  "brandFamiliarity": 0,
  "openEnd": 0,
  "speeding": 0,
  "honeyPot": 0,
  "straightlining": 0,
  "distinctSupplierCount": 0
}