2022 Updates

2022 Updates

Here’s what changed in 2022.

---

Aug 17

📣 Atribute Question & Answer Endpoints Removed

The Opportunity Registry /get-attribute-questions and /get-attribute-answers endpoints have been removed.

Please use the Respondent Gateway /list-attributes and /get-attribute-info endpoints to map attribute questions and answers. Learn more here.

🎉 Notification Updates are live!

The Opportunity Registry changes to the /receive-notifications endpoint have been redeployed to production.

Aug 16

🔄 Notification Updates are live!

Updated 3:45PM EDT 2022-08-16

These changes have been rolled back and will be redeployed at a later time.

The Opportunity Registry changes to the /receive-notifications endpoint have been deployed to production.

Aug 03

📣 Opportunity Registry Update

🆕 New Endpoints

The /receive-notifications and /ack-notifications have been deployed.

Moving forward, partners should use these endpoints to consume and process opportunity notifications.

⬇️ Deprecated Endpoints

The /list-opportunities and /ack-opportunities have been deprecated.

These endpoints should no longer be used and could be removed at some point in the future.

Aug 02

🗓 Notification Updates

On August 16, the Opportunity Registry will be updating the response header and body for the /receive-notifications endpoint.

What’s Changing

Response Header

The header will include two additional properties, notification_count and notification_total.

property	description
notification_count	The number of opportunity notifications received in the current response from the /receive-notifications endpoint.
notification_total	The total number of unacknowledged opportunity notifications in the queue.

Response Body

In the body, each opportunity notification object will include a new notified property when available. This property describes when the opportunity notification was created.

Recommendations

1. Partner must make sure they can consume the new properties.
2. Both the notification_total and notification_count make it easier to understand where the consumer is in the notification queue.
3. The notified property is a good indicator of the age of a notification.
4. Use these properties in creative ways to optimize consumption and processing.

Jul 27

🎉 Answered Cell is LIVE!

The new ANSWERED cell has been deployed to production as of this morning, and is now live.

Jul 21

🗓 Answered Cell

Friendly reminder that the ANSWERED cell will be deployed to production on Wednesday, July 27.

Jul 12

New /list-attributes endpoint is live.

The new /list-attributes endpoint is live in the Respondent Gateway. This will not break previous integrations with the /get-attributes endpoint, as it will still remain functional, and return the same payload as /list-attributes, but we suggest using /list-attributes moving forward.

Updates

• More accurately determines the most commonly used attributes and sorts them in descending order from most to least used.
• Limit of 500 attributes.
• Still accepts pagination in the request but it’s now optional, and will default to 500 results if no value is provided.
• You may request less than 500 attributes if you want a smaller payload, but if you request over 500 attributes the response body will still be capped.

Jul 6

Deprecating /get-attributes-questions and /get-attribute-answers endpoints

Just a friendly announcement - we will be deprecating the /get-attribute-questions and /get-attribute-answers endpoints for the Opportunity Registry. Moving forward please use /list-attributes and /get-attribute-info endpoints in the Respondent Gateway. See here for more documentation about how attributes are used in our system. First we will be marking the old endpoints as deprecated in our documentation, then the code will be removed entirely soon after.

Jun 7

Answered Cell - Sandbox

The ANSWERED cell is now live in the sandbox environment.

Jun 6

Answered Cell

On July 27th, 2022 the ANSWERED cell type will be added to the Opportunity Registry.

The ANSWERED type describes a cell that requires the respondent to have any set value for the attribute. For example, an ANSWERED cell for attribute 1 (Gender) will accept repsondents that have provided an answer of either 1 (Male) or 2 (Female). These answers can be supplied via the entry URL query parameters, respondent registration endpoints, or custom contexts.

In rare situations the ANSWERED cell may be negated. This requires that the respondent does not have an existing answer for that attribute recorded in Dynata’s system.

This will allow partners to more accurately target some demographic requirements that could not be communicated previously.

// Respondent must contain a value for the attribute

{
  "tag": "cell-tag",
  "attribute_id": 54321,
  "negate": false,
  "kind": "ANSWERED"
}

// Respondent must not contain a value for the attribute

{
  "tag": "cell-tag",
  "attribute_id": 54321,
  "negate": true,
  "kind": "ANSWERED"
}

it’s recommended partners make the necessary adjustments to their system to support these changes before July 27th, 2022. 

Jun 02

Attribute Updates - Phase 2

In a continued effort to simplify opportunity targeting and improve the respondent experience, the Dynata team is making additional changes to our questions and answer attributes.

Here is a quick overview of the changes:

• Updating question names
• Updating question text
• Updating answer text
• Deactivating answers
• Adding new answers

The Phase 2 updates will launch on July 12th, 2022. Partners will receive the list of attribute updates in the next few days. The /get-attribute-info endpoint will reflect these changes upon release.

May 23

The REX PHP SDK is live!

Check it out here:

• Github repo
• Packagist

May 10

The REX Python SDK is live!

Check it out here:

• Github repo
• PyPI

May 06

Ineffable Cell & Operator Property

The Opportunity Registry Updates Were deployed on Thursday, May 05.

Changes

The Opportunity Registry now supports the INEFFABLE cell type and the operator property for LIST and COLLECTION cell types.

May 03

Opportunity Registry Update

The Opportunity Registry Updates has been rescheduled to Thursday, May 05, 2022, at 11:00AM ET. We apologize for any inconvenience, and thank you for your patience.

Apr 18

Disposition Statuses

The new disposition statuses have been deployed.

Status	Disposition	Status	Description
Incompatible Country	2	3	The respondent’s country did not match the opportunity’s targeting.
Incompatible Language	2	4	The respondent’s language did not match the opportunity’s targeting.
Incompatible Device	2	5	The respondent’s device did not match the opportunity’s targeting.
Filter Disqualification	2	6	The respondent was disqualified because they did not match the opportunity’s filtering criteria.
Quota Disqualification	2	7	The respondent was disqualified because they did not match the opportunity’s quota criteria.
Dynata Closed Quota	3	3	The respondent qualified for a quota that is CLOSED.

Upcoming Opportunity Registry Updates

On May 2nd, 2022 we will introduce the INEFFABLE cell type  and the operator property for LIST and COLLECTION cell types.

These changes are already live in our sandbox environment. 

Ineffable Cells

The INEFFABLE type will describe a cell that cannot be defined. This will give partners better visibility and allow them to decide how they will process opportunities that contain these cells.

Partners cannot account for this targeting. 

{
  "tag": "dd64b622-ed10-4a3b-e1h8-a4e63b59vha2",

  "attribute_id": 83,

  "negate": false,

  "kind": "INEFFABLE"
}

Operator Property

The operator property will affect the evaluation of an answer set.

• If set to AND and negate is false the respondent must match all values. 
• If set to AND and negate is true the respondent must not match any of the values.
• if OR it will use the default evaluation.

// Contains ALL collection values.

{
    "tag": "ff65b422-e810-4f3f-b1f8-f4e63b59ffa2",
    "attribute_id": 8,
    "negate": false,
    "operator": "AND",
    "kind": "COLLECTION",
    "collection": "2169733"
}

// Does not contain any of the collection values.

{
    "tag": "ff65b422-e810-4f3f-b1f8-f4e63b59ffa2",
    "attribute_id": 8,
    "negate": true,
    "operator": "AND",
    "kind": "COLLECTION",
    "collection": "2169733"
}

// Value is in the collection.

{
    "tag": "ff65b422-e810-4f3f-b1f8-f4e63b59ffa2",
    "attribute_id": 8,
    "negate": false,
    "operator": "OR",
    "kind": "COLLECTION",
    "collection": "2169733"
}

// Value is not in the collection.

{
    "tag": "ff65b422-e810-4f3f-b1f8-f4e63b59ffa2",
    "attribute_id": 8,
    "negate": true,
    "operator": "OR",
    "kind": "COLLECTION",
    "collection": "2169733"
}

We recommend that partners make the necessary adjustments to their system to support these changes before the deployment on May 2nd.  Learn more here.

---

Apr 12

New Interactive Signer

We’ve rolled out a new interactive signer for partners to test their signature hashes when integrating with REX. Test your signature payloads to make sure you’re following Dynata’s signing methodology here.

---

Apr 11

New Statuses Update

As a part of our effort to provide more granular reporting on respondent status, we will be deploying a new set of statuses on April 18th.

Status	Description
Incompatible Country	The respondent’s country did not match the opportunity’s targeting.
Incompatible Language	The respondent’s language did not match the opportunity’s targeting.
Incompatible Device	The respondent’s device did not match the opportunity’s targeting.
Filter Disqualification	The respondent was disqualified because they did not match the opportunity’s filtering criteria.
Quota Disqualification	The respondent was disqualified because they did not match the opportunity’s quota criteria.
Dynata Closed Quota	The respondent qualified for a quota that is CLOSED.

These statuses will flow through the outbound, sever-to-server callback, and theRespondent Event Broadcaster starting April 18th.

We recommend partners make any required adjustments to their system.

Learn more here.

---

Apr 7

New Attribute Endpoints Deployed

Today we released 2 new endpoints! Learn more here.

• /get-attributes
• /get-attribute-info

---

Apr 6

Attribute Updates - Phase 1 Launch

The Phase 1 update has been rolled out as of 3PM EST. Attributes in the /get-attribute-questions, and /get-attribute-answers .csv files have been updated to reflect these changes.

---

Mar 21

Attribute Updates - Phase 1

The Dynata team is making updates to our questions and answer attributes. The goal is to simplify targeting for partners and improve the respondent experience.

Here is a quick overview of the changes:

• Updating question names
• Updating question text
• Updating answer text
• Deactivating answers
• Adding new answers

Phase 1 of these updates will launch on April 6th, 2022. We will provide you with the list of attribute updates in the next few days. Before the update, we will send out a new version of attribute mapping. The get-attribute-question and get-attribute-answer endpoints will reflect these changes too.