Skip to main content

Auto-Register Paid Users in AEvent After Stripe Checkout (Webhook Setup Guide)

Updated this week

Want to automatically register someone into an AEvent campaign as soon as they complete a Stripe payment? This guide shows you how to send buyer data to AEvent via a webhook and auto-assign them to the right audience.


🔗 Step 1: Create a Webhook Audience in AEvent

  1. Go to the campaign where you want to add buyers

  2. On the left menu, click Audience

  3. Click Create New Audience

  4. Name it something like “Stripe Buyers”

  5. Set your qualifier logic (e.g., Tag = Buyer)

  6. Select Inbound Webhook as the method

  7. Click the Copy Endpoint button

You’ll get a URL like:

https://TENANTID.aevent.online/setpixel?page=webhook&wtl=XXXXX&value=Buyer&email=

✳️ Replace email= with the buyer’s actual email address dynamically in the next step.


⚙️ Step 2: Add the Webhook to Stripe

In your Stripe Dashboard:

  1. Go to Developers > Webhooks

  2. Click + Add Endpoint

  3. Paste your AEvent webhook URL (with the right email= value)

  4. Under Events to send, choose:

    • checkout.session.completed (recommended for most setups)

    • Optionally: charge.succeeded (if using direct charges)

  5. Save the webhook


🧩 Step 3: Format the Payload

When the Stripe webhook triggers, send AEvent the correct format using a tool like Zapier, Make, or your backend code.

Here’s an example of how your outgoing call should look:

POST https://tenant_id.aevent.online/setpixel?page=webhook&wtl=XXXXX&value=Buyer&[email protected]
  • wtl= is from your copied AEvent URL

  • value= is the tag you want to apply (e.g., “Buyer”)

  • email= is the buyer’s email from Stripe

For full parameter guidance, see:
👉 Audience Segmentation via Inbound API/Webhook


✅ Step 4: Test the Flow

  1. Use Stripe Test Mode

  2. Complete a test purchase

  3. Verify that the registrant appears in the right AEvent audience


🚀 Step 5: Go Live

  • Activate the webhook with your Live Stripe key

  • Send a real payment and verify registration behavior

  • Monitor AEvent audience activity to confirm

Did this answer your question?