Constant Contact subscription

[ss57]

I'm not able to make the newsletter fields of FaaS work. The documentation seems to be clear, and I think we've implemented it as described, but nothing comes out the other side. I tested with an "EasyPage" and it worked, so I know our Constant Contact account is linked correctly. Here is the form code:

<input name= "eNewsletterName1" type="hidden" value="ConstantContact">
<label id="SubscribeList1Label" for="SubscribeList1">
<input name="SubscribeList1" type="checkbox" checked="checked" id="SubscribeList1" value="General Interest"> Please sign me up for your newsletter
</label>

[CnP.Support]

Good day!

In FaaS you have to reference a WID - have you enabled this newsletter for that WID? The checkout page has a section for eNewlsetter and you need to enable Constant Contact for that WID.

May I have the WID or the link to the form so we can review your code?

[ss57]

The WID is 76417 and the URL is http://www.ywamsf.org/test-donation-page-1/

[CnP.Support]

Good day!

Please see below:



as stated earlier the eNewsletter should be enabled for this page. The WID you are using:

<input id="WID" type="hidden" name="WID" value="76417" />

This WID is for an advanced page (catalog page) and the eNewsletter option is not activated.

It is always easier to use an easypage as a reference page for a FaaS form but any form works.

Please activate it and let us know if you still have issues.

[ss57]

OK, that did it.

Why is an EasyPage better to use as a reference? I have never seen any documentation that tells which settings come from the Portal and which come from the FaaS fields. I didn't even understand where to get a WID from until we just decided to experiment with one of the portal-generated WIDs. I think there should be a section on the Portal just for FaaS. This is very confusing.

[CnP.Support]

Good day!

You may want to refer to: http://forums.clickandpledge.com/articles/api/faas

Certain attributes, as discussed in the above KB article, are used for a FaaS form. This minimizes the amount of data or information that needs to be included or exposed in an HTML form. For example the notification list includes the email address of internal people, in addition to those listed in the Account Info > Profile, to be notified when a form processes.

Thank you message, and other messages are lengthy text fields and posting them will take more network time to post so we try to minimize as much information as we can and use internal fields to compensate. This also gives you an added advantage where certain information may be used by a user without having to change the code by a developer.

In the next release, being worked on now, you will be able to create a FaaS reference page with only the information needed to be used in a form. Currently we use an existing form to simplify the process.

[ss57]

Thank you for the additional information. I had read that page, but it wouldn't have answered the original question. No matter, though, since I understand now. Thanks for your help. I look forward to the new release. Sounds like some good improvements are on the way!

[ss57]

I just discovered that the newsletter subscription stopped working again. It apparently worked while we had it at the test URL, but when we moved it into production something must have broken. The new URL is https://www.ywamsf.org/donate. I even tried it with advanced page 76417 and it doesn't work there either. I made sure my constant contact password is up to date in Account Info - 3rd Party - Newsletter. What am I missing? I don't see any log files or information on the Salesforce side to indicate what's happening. Even once it's working, how will I know who checked the "subscribe" button? It would be good to go back and subscribe those that checked the box while I thought it was working.

[ss57]

Does anyone have suggestions or questions for me?

[CnP.Support]

Good day!

We are researching this and will get back to you.

It is really best if you can start a new thread when the subject changes. It will help with the topics and indexing of questions.

I will keep you posted as to what we find out.

[ss57]

Should I start a new thread now, or open a help ticket? I hadn't done so before because I figured it was the same topic.

[CnP.Support]

Good day!

We have tested this a great deal and we have found is a bit confusing. Here is what we see as to the behavior of the Constant Contact API:

• The post will not work if the user being posted existed at one time and was deleted. It seems like the deleted users cannot be added again. Posting this user does not generate an error and reports success but it does not post either.
• Depending on the frequency of post, adding a user will report a successful post but the user may not be added. Repeated attempts will add the user.

We did a lot of tests as well as high frequency tests to determine what the issue may be. Our integration works per specs and all tests work fine but there appears to be scenarios where the API fails.

Have you posted a user that you had deleted before?

[ss57]

Thanks for the update and for testing the API. As for my personal test, the email I used had never been subscribed. Other than that, I have no way of knowing who has left the subscribe box checked since there is no reporting in the Click & Pledge system to log this activity. Since going "live" with Click & Pledge about two months ago, no new subscribers have come from the FaaS forms.