Aweber Setup & Debugging

Setup

Aweber API ID

The first thing we need to do create an App ID, this allows you to send lead data to your Aweber Customer account. Signup at https://labs.aweber.com/ and create a new App. Be sure to set the App website to the website URL you are installing from.

 

Once you’ve created the App, copy your App ID and head to the Inbound Settings area.

Accessing Settings

Inbound Pro Users

If you are using our inbound pro component then you will find your extension settings by following these breadcrumbs:

wp-admin->Inbound Now->Settings->Extension Settings.

There you will find your Aweber setup settings.

Non Inbound Pro / Stand Alone Plugin Users

If you are not using our all in one component then you probably have one of our free plugins installed from the WordPress repository (landing pages, calls to action, or leads).

Head into any of Inbound Now plugin’s settings area and find the ‘Extensions’ tab. If you are using Landing Pages plugin then head into wp-admin->Landing Pages->Settings, and find the ‘Extensions’ tab. There you should find your Aweber setup data.

Authorizing

For Inbound Pro:

In order to send lead data to your Aweber account, you’ll need to authorize your website. To do this, enter you App ID into the “Aweber API ID” text field, and click the green “Authorize” button.

 

This will take you to the Inbound Aweber Authorization popup window, which will ask you to click on the “Get Authorization Code” link, and to enter the code in the text field below.

When you click on the link, you will be redirected to the Aweber Authorize App page. This page will authorize your website to send leads to your Aweber lists. You’ll need to sign in with your Aweber Customer name and password. After you’ve signed in, the window will display a long code of letters and symbols, copy the whole thing and go back to the Inbound Aweber Authorization popup window. Paste the code into the authorization code text field and click “Authorize.”

 

If there are no errors, Aweber will be authorized and you’ll be all set to start sending leads.

 

For standalone plugins:

The process for standalone plugins is a little different from Inbound Pro. In the settings screen, under “Extensions”, you’ll see a text field called “Aweber API ID”. Enter the Aweber App ID here, check the “OAuth reset” checkbox, and click “Save Settings”.

 

This will redirect you to the Inbound Aweber authorization page. Here you’ll be asked to click on the “Get Authorization Code” link. Once you click it, you’ll be taken to an Aweber page asking you to sign in to authorize your website to make changes to your Aweber account. For this you’ll need to use your Aweber Customer login name and password, not your developer name & password.

 

After you’ve singed in, you’ll be shown a long code of letters and symbols, copy the whole thing and go back to the Inbound Aweber authorization page. Paste the code into the text field and click “Authorize”.

 

If there are no errors, Aweber will be authorized and you’ll be all set to start sending leads.

Connecting Aweber to a form

 

Routing submissions into an Aweber list

Once the settings are in place and your Aweber account authorized an option will appear in your Inbound Form setup  area to connect a form to Aweber. It will also ask which Aweber list you would like to have subscriber information inputted into.

 

Mapping fields

For forms to know which fields contain what we need to map them. A successful connection to Aweber depends on it.

http://docs.inboundnow.com/guide/map-inbound-now-form-fields/

Debugging

Forms not sending data

Map your fields

Make sure you are always thorough with your Inbound Form’s creation by mapping fields to their appropriate location. This tells our systems what kind of data the field represents and is required by the Aweber Extension to operate

http://docs.inboundnow.com/guide/map-inbound-now-form-fields/

Check permalink settings

Currently our plugins require that permalinks are not using the default permalink structure shipped with WordPress. Use post name or something different and this often will solve Aweber communication issues. We are investigating support for numeric permalinks:

 

2014-11-04_1213