Tag Teachable buyers by course in AWeber

You sell three courses. You want to email the people who bought Course B, and only them, about a live cohort. This is the setup that gets a Course B buyer into AWeber the moment they pay, without you touching a spreadsheet.

Read off Teachable's and AWeber's own support articles and documentation on 9 September 2026. We have not clicked through the live setup ourselves; where a screen or a limit could not be confirmed from a vendor page, it is marked as such rather than assumed.

Route 1: the integration Teachable itself built

Teachable's own App Hub has a listed AWeber app. In your school admin, open the App Hub, click the AWeber icon, and select Install. That redirects you to AWeber's login, where you sign in and click Allow access.Source

Teachable's support article for the integration names the triggers directly: New sign-up,New sale, New enrollment (which includes one you add by hand as an admin), Course completed, and Subscription canceled. The only action available is Add Subscriber, which creates or updates a contact in a specific AWeber list. Each workflow can be scoped to the whole school or to a single course.Source

That course scoping is what makes this route work for the "which course" question. Build one workflow per course, each pointed at its own AWeber list: a New sale on Course B routes into a "Course B buyers" list, a New sale on Course C into "Course C buyers," and so on. You never leave Teachable's admin to do it.

What Teachable's own article confirms
DirectionOne way only. "AWeber triggers and actions are not available at this time"
ConsentStudents who have not opted in are not passed to AWeber
Builder planOne workflow
Growth plan and upUnlimited workflows
Starter planNot stated in Teachable's article. Not confirmed either way

Not confirmed: whether the App Hub AWeber app is available on Teachable's Starter plan at all. Check the App Hub in your own school before planning around this route on Starter.

Turning a list into a tag

A list membership is not automatically a tag, and AWeber treats the two as different objects. Once a course's buyers land in a dedicated list, build an AWeber workflow with the starter "someone joins this list," and give it one action: apply a tag, for example bought-course-b. AWeber's own tags article confirms a workflow can carry an "Apply Tag" action step, and that tags can be created ahead of time from a subscriber's profile or in bulk.Source

One real limit worth knowing before you build around it: AWeber's documentation on starting a workflow with a tag states that the workflow "will only start for subscribers who are tagged after the workflow is published." It does not fire retroactively on people who already carry that tag.Source

Set it up

The App Hub connection lives inside Teachable. The workflow that turns a list into a tag lives inside AWeber. Both accounts need to exist before either side of this works.

How we test.

Route 2: Zapier, if you want a tag directly instead of a list

Teachable's Zapier app exposes a New Saletrigger, documented as firing on self-enrollment, free or paid, but not on enrollments an admin adds by hand.Source

On the AWeber side, Zapier's available actions areCreate Subscriber and Update Subscriber. Create Subscriber carries a Tags field, so a new buyer can be created directly with the course's tag attached in one step. Whether Update Subscriber can also set a tag on someone who already exists is not something we could confirm from Zapier's own documentation, only that it does not carry custom fields the way Create Subscriber does. Test this on your own account before you build a Zap that depends on it.Source

One Zap per course, each hard-coding its own tag, is the straightforward version. It duplicates what the App Hub route already does, so most people should only reach for Zapier if they specifically want a tag rather than a list at the point of sale.

Route 3: the API, if you already write code

AWeber's documented pattern for tagging by API is to attempt to create the subscriber with the tag included, and catch the error AWeber returns when that email address already exists on the list. From there, look the subscriber up and send a PATCH request to update their record.Source

This is the same shape as the Zapier route underneath, so it is worth reaching for only if you are already comfortable scripting against an API, or if you sell through more courses than a one-Zap-per-course setup can reasonably manage.

Edge cases worth ten minutes

  • Refunds. Teachable's webhook and Zapier both expose a refund event. Route it to arefunded-course-name tag and exclude that tag from future sends about the course.
  • Admin-added enrollments. The App Hub's New enrollment trigger includes ones you add by hand, which the Zapier New Sale trigger does not. If you comp courses, decide which route you actually want on a per-workflow basis.
  • Course completion. The App Hub trigger list includes course completion as its own event, which is worth a workflow of its own, separate from purchase, if you run a completion-based offer or a certificate email.

Questions people ask

Does the App Hub integration apply a tag, or add someone to a list?
A list. Teachable's own article names the action as "Add Subscriber," described as creating or updating a contact in a specific AWeber list. If you want a tag on the record rather than list membership, scope one workflow per course and route each into its own list, then decide whether list membership alone is enough or whether you also want a tag for use in a workflow.
Can I use a tag as the trigger instead of a list?
The App Hub side hands you a list, not a tag. Once someone lands in that list, you can build an AWeber workflow that runs an action such as applying a tag to everyone who joins it, which gets you to the same place: a tagged record you can filter and automate against.
What if I need this to work retroactively, for people who bought last month?
It will not. AWeber's own documentation is specific that a workflow started by a tag "will only start for subscribers who are tagged after the workflow is published." The App Hub integration only fires on new Teachable events from the moment you connect it. Past buyers come in through the export in the migration guide, not through this integration.

Read next:the full migration guide for your existing list,recovering abandoned checkouts, or go back to the full corridor.