Skip to content
Developer

Production Checklist

Production Launch Checklist

Best Practices

Important!

Use the production version of the list-attributes endpoint to map against the most commonly used attributes. The results from the QA version of list-attributes are sorted arbitrarily.

  1. Focus on strict matching, until the integration has been fully optimized..
    • Only send respondents that fully match targeting for an opportunity.
    • Do not send respondents into opportunities with partial matches, or where the attributes have not been mapped,
  2. On the respondent’s first entry pass in birth_date, gender and postal_code in the inbound URL or register the respondent using the put-respondent endpoint.
  3. Maintain the opportunity notification queue, to ensure the most up-to-date information.
    • Acknowledge opportunity notifications immediately after processing, and acknowledge all opportunity notifications until all have been processed.
    • Call the /receive-notifications endpoint every 3-5 seconds after you’ve exhausted all opportunity notifications from the queue.
    • A maximum of 50 opportunities can be retrieved at one time through the /receive-notifications endpoint.
    • Find more information about the receive-notifications endpoint here.
  4. Focus on high IR opportunities to increase qualification rate.
  5. Use the get-attribute-info endpoint to map any unknown attributes.
  6. Respect the opportunity status; only send to opportunities that are OPEN and not to those that are CLOSED or PAUSED. If a project is OPEN, and quotas are PAUSED, do not send to the project.
  7. Be open to sending in moderate volumes to a small set of studies to ensure enough data is gathered to analyze performance and address any improvements before fully launching.
  8. Considering filters when sending traffic. learn more.
  9. Some opportunities may have targeting that may not be represent in the quotas or filters.