AWeber Integration

Click AWeber in the LeadSync destination list and authorise the OAuth connection from your AWeber account. AWeber uses OAuth 1.0a (the older OAuth spec) which involves a request token plus access token plus access secret -- LeadSync handles the entire flow so you just need to click authorise.

Yes. If a Facebook lead arrives with a custom question that does not match an existing custom field in your AWeber list, LeadSync creates the field on the fly using the field name from your lead form. No manual setup required in AWeber.

Yes. AWeber campaigns trigger on list subscription, so when LeadSync adds the contact to your list, the campaign begins running immediately. Your welcome email and follow-up sequence start within seconds of the lead form submission.

AWeber uses a single name field rather than separate first and last name fields. LeadSync handles the conversion automatically -- if your lead form provides first_name and last_name separately, they are concatenated into the name field for AWeber.

AWeber de-duplicates by email within a list, so a repeat submission updates the existing subscriber rather than creating a duplicate. Your list count stays accurate.

Yes. Create one LeadSync connection per AWeber list, and route different lead sources (different Facebook Pages, different ad platforms) to different lists. Each connection has its own field mapping and campaign attribution.

Yes. LeadSync supports AWeber as a destination for lead forms from Facebook, Instagram, Google Ads lead form extensions, LinkedIn Lead Gen Forms, and TikTok Lead Generation. Each source becomes its own connection.

Yes. AWeber campaigns are list-scoped, meaning each list has its own assigned campaign that fires on subscription. Route different ad sources to different lists via separate LeadSync connections, and each ad source triggers its own campaign with its own welcome and follow-up sequence.

A subscriber is a single person; a list is the container they belong to. The same person can be a subscriber on multiple lists -- AWeber treats each list-subscription as separate, with its own confirmed status, custom field values, and campaign attribution. LeadSync subscribes to one list per connection.

AWeber's tag assignment requires a different API surface than the lightweight subscriber-create endpoint LeadSync uses. The cleanest workflow is to map your tag value to a custom field on the subscriber, then use AWeber's automation rules to apply tags based on that custom field value when the subscriber is added.

Each LeadSync connection adds the subscriber to one AWeber list. To land them in multiple lists simultaneously, create multiple connections for the same lead form, each pointing at a different list -- they all fire in parallel for each new lead with no delay between them.

Yes. The API access LeadSync uses is available on all AWeber plans including the free tier. AWeber's free plan has a 500-subscriber cap -- once you hit it, AWeber rejects new subscribers and LeadSync logs the failure. Upgrade your AWeber plan to lift the cap if you expect to exceed it.