Subscribing to a Campaign Monitor list using AJAX

ajaxsubscribe.html

<!-- 1. Take your Campaign Monitor subscribe form as generated from within your account: -->

<form action="http://myaccount.createsend.com/t/r/s/aljhk/" method="post" id="subForm">
    <div>
        <label for="name">Name:</label><br /><input type="text" name="cm-name" id="name" /><br />
        <label for="aljhk-aljhk">Email:</label><br /><input type="text" name="cm-aljhk-aljhk" id="aljhk-aljhk" /><br />
        <input type="submit" value="Subscribe" />
    </div>
</form>

<!-- 2. Add some JavaScript -->

<script type="text/javascript" src="https://ajax.googleapis.com/ajax/libs/jquery/1.6.2/jquery.min.js"></script> 
<script type="text/javascript">
    $(function () {
        $('#subForm').submit(function (e) {
            e.preventDefault();
            $.getJSON(
            this.action + "?callback=?",
            $(this).serialize(),
            function (data) {
                if (data.Status === 400) {
                    alert("Error: " + data.Message);
                } else { // 200
                    alert("Success: " + data.Message);
                }
            });
        });
    });
</script>

<!-- 3. You have an AJAX subscribe form! -->

LICENSE

The MIT License (MIT)

Copyright (c) James Dennes

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.

@jamesmusgrave Thanks, used yours for an Angular 5/6 version
https://gist.github.com/arrenv/fd99e1b0a8ea323152746d915f11d1f4

Hi, do we have any update here?

I implemented a JS signup form using the /getsecuresubscribelink approach yesterday and sure enough it worked initially, but subsequent requests all returned a web page with a reCAPTCHA step. For anyone reading this and considering whether it’s worth at least trying this approach first, don’t bother, save yourself the time.

Having emailed CM it appears that captchas are likely to show up whenever multiple signups are received from the same IP (so as devs in testing we’re most likely to trigger it) and there is no way to switch this off at the account level. Since there is no clean way of incorporating these captchas into a JS signup workflow and you can never guarantee that captchas won’t be enabled for a given request you can’t use this workflow and expect it to be reliable.

The only clean solution is to build your own server-side component using the CM API, then to have your frontend app POST to that, rather than directly to CM.

WARNING WARNING! I just got bitten by the getsecuresubscribelink ajax hack.

Yes as reported by @domstubbs above, the form submission will ask the user to complete a recaptcha. This does not work in ajax request mode. You have to direct the user to that page in a normal form submit. Use their included library otherwise you will find people cannot subscribe (even though it looks like the ajax request is working).

Updated version using Vue
https://gist.github.com/jamesmusgrave/4b860422c4cb34cf9d38c12f89d8401c

As mentioned this doesn't work if the recaptcha is triggered

@Macaroons glad to help :)

Hi @dawidnawrot , it tried you script and it did work initially ~~~~~!! But also like what some of the comments above say, campaign monitor started to ask for non-robot confirmation after a several times. So I was wondering if you have the same issue but also a solution to that. Would be highly appreciated!