If you have had challenges getting DAP=>AWeber integration to work in the recent weeks, it’s because AWeber has made a few changes on their side that has impacted the ‘Email Based Subscription’ to AWeber by 3rd party systems like DAP.
Please review the following list if your DAP users are not getting added to your AWeber list:
1) Enable DigitalAccessPass parser for your list in AWeber.
2) Make a note of your Aweber List ID (instead of list name).
Login to AWeber and select the right list. Then, under List Options > List Settings, under “Basic Information” section, you’ll see “List Name” and right below that, you’ll see “Unique List ID“.
For older lists, both name and id will be the same. But for the lists recently created, these may not be the same.
You will have to use the AWeber list Id (and not the list name) for the DAP=>AWeber integration.
Make a note of the AWeber list Id and use firstname.lastname@example.org (instead of email@example.com) in the DAP Products => Notifications tab => 3rd party Ids text box.
3) Do NOT use a ‘role based’ email address in DAP Admin => Setup => Config => From/Admin Email section.
For ex: firstname.lastname@example.org
Email addresses using info, support, admin, etc, are blocked in AWeber and cannot be used when creating a parser.
You can change it to say email@example.com or say firstname.lastname@example.org and that will work fine.
4) If the users still do not get subscribed to the AWeber list, then it’s most like a ‘Reverse IP’ lookup issue between AWeber and your webhost.
You can see this document on how to send out authenticated email from your server to improve deliverability.
If it still does not help, please open a ticket with AWeber support and have them tell you why the email is being rejected. It will likely be a reverse DNS or SPF issue that your webhost can easily fix.
Hope this helps!