Source evidence

Broken List Management

Constant Contact Forms · review · 2023-06-08T11:26:00+00:00

Constant Contact Forms plugin evidence original source source API

complaintsentiment

highseverity

0.85relevance

1replies

Evidence linked to opportunitycommercial context

Proof Health

Open evidence

Commercial opportunities need traceable source links before they are treated as build-worthy.

6 / 36 rows with source links

16.7% of this page's analysis has direct source links.

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

30 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

review · 1 stars

markparolisi unresolved

The 2.0.1 version lost all of our lists. They cannot be re-synced. And we cannot create new lists from within WordPress. Without connections to lists, this plugin is fatally broken. Reverting back to v1 Hi @markparolisi Yes, reverting back to 1.14.x is the correct thing to do at the moment while we tackle reported issues with this considerably large upgrade that changes API versions. We are actively aware of this issue and are working on getting it resolved as soon as we can so that we can continue to get people upgraded without issue.

Commercial Context

Opportunity

lead capture reliability

Newsletter lead-capture reliability for protecting form submissions and lead routing

Buyer: marketing teams, agencies, and lead-generation site owners

Wedge: monitor newsletter submissions, notification delivery, spam, and CRM handoffs

Proof Blocked card complete market

Analysis

heuristic-v1

Summary: Broken List Management: users show bugs, support pain that may indicate a product gap.

Evidence quote: Broken List Management The 2.0.1 version lost all of our lists.

Affected feature: api

bugs support support api

Plugin

API

Constant Contact Forms

20.0K active installs · 2.7M downloads · rating 54.0

constant contact constant contact official contacts marketing newsletter

Comments

1 shown

Constant Contact 2023-06-08T13:34:00+00:00

Hi @markparolisi Yes, reverting back to 1.14.x is the correct thing to do at the moment while we tackle reported issues with this considerably large upgrade that changes API versions. We are actively aware of this issue and are working on getting it resolved as soon as we can so that we can continue to get people upgraded without issue.