Skip to content
AppDues
Log in
Contact salesSign up

Build a Timeline Trial Paywall with Webhooks and Zapier

A trial paywall has two jobs: explain exactly what happens after signup, and make sure the user hears from you before the first charge. This guide covers both. You will lay out a timeline paywall that names the trial length and the billing date, then connect a subscription-start event to a delayed reminder email using subscription webhooks and Zapier — no backend service of your own.

Why a timeline beats a feature list for trial offers

Feature grids answer "what do I get?" A timeline answers "what happens to me, and when?" For a try-before-you-buy offer, the second question is the one that blocks the purchase. Three statements do most of the work:

  • The trial is free and no charge happens at signup.
  • A reminder will arrive a few days before the trial converts.
  • The exact end date and first billing date are visible on the paywall itself.

Together these remove the fear of an unexpected charge. The intended payoff is more trial starts, fewer billing-confusion support tickets, and stronger engagement with reminder messages. Treat those as goals to measure against your own baseline, not guaranteed results.

Putting the timeline on the paywall

In the paywall builder the element is called Timeline. You can drop it into an existing paywall or start from a sample that already includes it, then edit the copy so the dates match your own trial. The only content that must change is the timing language — the trial length and the day billing begins.

Before you build, confirm four things: the trial length your store products actually use, the day the reminder should land, the email address you will send from, and whether you want the reminder to go out on push as well. If any of those are undecided, the automation will encode a guess.

How the two tools split the work

The subscription platform emits a webhook whenever something changes in a subscription's lifecycle — a trial starting, a renewal, a cancellation. Zapier receives that event and runs the steps you define. Because Zapier handles the messaging, no server code is needed; access to the subscription dashboard and a Zapier account is enough.

Finish Zapier's onboarding first, then return to connect the two accounts.

The automation in plain terms

The Zap has four logical parts:

  1. Receive subscription-start events and keep only the ones that represent trials, not win-back or other subscription types. Filtering can happen on the subscription platform side or inside Zapier.
  2. Obtain the customer's email so the reminder reaches the right person. You can attach it during SDK initialization, or look it up in your own backend and match it to the subscription event.
  3. Wait, then send. A delay step holds the message until roughly two days before the trial converts.
  4. Respect cancellations. Someone who has already cancelled should not receive a "your trial is ending" nudge.

The third point is where most setups go wrong: the delay must be measured from the trial start, not from the moment the Zap is edited.

Step 1 — Catch the webhook and pull out the email

Create a new Zap and add a Webhooks by Zapier trigger with the event Catch Hook. In the trigger configuration, set the child key to:

event.subscriber_attributes.$email.value

That path tells Zapier to lift the email out of the subscriber attributes so later steps can use it directly.

Zapier then shows a webhook URL. In the subscription dashboard, open Integrations, choose New, and select Webhooks. Name the configuration something recognizable (for example, a trial-reminder label), paste the URL, and set the environment to Sandbox while you test. You can widen it to production later. You can also exclude specific apps from sending events before saving.

To verify the connection, open the webhook and use Send test event, then return to Zapier and run Find new records. A JSON body should appear. The sample payload in the accompanying technical module shows the shape: an event object with product_id, period_type, expiration_at_ms, environment, app_user_id, aliases, and a subscriber_attributes map holding $email, $displayName, $phoneNumber and any custom attributes. Fields such as store or country_code can drive conditional copy later. When the record looks right, choose Continue with selected record.

Step 2 — Add the delay

Add a step and pick Delay by Zapier. Set the action event to Delay for, then enter 5 with the unit set to Days. That places the message about two days ahead of a seven-day trial's conversion.

Adjust the number to match your own timeline. During testing, switch the unit to minutes so you do not have to wait days to see a result.

Step 3 — Compose the reminder

Zapier connects to many email providers. For a quick test, Email by Zapier sends a plain message such as "Your subscription will continue in 2 days." For production, a dedicated provider — Mailchimp, Postmark, SendGrid or Customer.io are examples — gives you better deliverability, branded templates and analytics.

If you add your own address to the CC field while testing, remove it before the Zap goes live.

Step 4 — Test, then publish

Change the delay from days to minutes. Trigger a subscription event either from your app or by firing the test event with your address in the CC field; The platform sends the test to a dummy address, so the CC is how you see it. An email should arrive within the test window. Switch the delay back to days and publish.

Use this checklist before you call it done:

  • The reminder arrives at the intended offset from trial start.
  • The recipient is the subscriber, not a placeholder address.
  • A cancelled trial produces no reminder.
  • The message names the correct billing date and price.
  • The CC test address has been removed.

Reading the webhook payload

The event object carries more than the email. A few fields are worth knowing when you build filters or personalize copy:

  • period_type distinguishes a normal period from other period kinds.
  • expiration_at_ms is the timestamp you can compare against to confirm trial timing.
  • environment tells you whether the event came from sandbox or production.
  • app_user_id and aliases identify the customer across identifiers.
  • store and country_code let you vary wording by platform or region.
  • subscriber_attributes holds the email plus any custom attributes you set.

A worked example: in the sample payload the email attribute holds a test address, the display name is set, and the store is the Play Store. If you wanted Android users to receive different copy, that store value is the switch.

Three different failures, three different fixes

A missing reminder is not one bug. Separate the cases:

  • No email at all. The webhook never fired, the Zap is off, or the delay is still counting. Check the webhook's test event and the Zap's task history.
  • Email to the wrong person. The child key did not resolve, so the email field was empty or defaulted. Confirm the subscriber attribute is actually set at SDK initialization.
  • Email after cancellation. There is no filter on cancellation events, so the delayed message still sends. Add a check that suppresses the send when the subscription has been cancelled.

Each of these maps to a different step in the Zap, which is why testing with a real subscription event beats testing with a manual email.

Where to take it next

Once the basic loop works, four extensions are worth considering:

  • Filter so reminders go only to new users on a seven-day trial. The payload already contains what you need.
  • A/B test the message, the timing, or the channel to learn what actually moves conversion.
  • Add push notifications alongside email, using Zapier or a service such as OneSignal or Firebase, if in-app engagement is strong.
  • Personalize by name, platform or acquisition channel, passing those attributes through the subscription platform.

Each extension is a small change to the same Zap, not a rebuild.

Frequently asked questions

Does the reminder depend on a seven-day trial?

The example uses a seven-day trial with a five-day delay, which lands the message about two days before conversion. Change both numbers together so the reminder still arrives before the charge.

Can this run without a backend?

Yes, for the messaging path. The subscription platform sends the event and Zapier handles the delay and email. You still need a way to associate an email with the customer — either by setting it as a subscriber attribute when the SDK initializes, or by matching the event to a record in your own system.

What stops a reminder from reaching someone who cancelled?

A filter on cancellation events. Without one, the delayed step still fires. Add the check before publishing, and test it with a cancelled trial.

How do I test without waiting days?

Set the delay unit to minutes, fire a subscription event, and confirm the email arrives. Then switch the unit back to days before publishing.

{
  "event": {
    "event_timestamp_ms": 1746471203817,
    "product_id": "test_product",
    "period_type": "NORMAL",
    "purchased_at_ms": 1746471203817,
    "expiration_at_ms": 1746478403817,
    "environment": "SANDBOX",
    "entitlement_id": null,
    "entitlement_ids": [],
    "presented_offering_id": null,
    "transaction_id": null,
    "original_transaction_id": null,
    "is_family_share": null,
    "country_code": "US",
    "app_user_id": "1bf2f016-d74e-43fc-b3fa-b61156a03799",
    "aliases": [
      "1bf2f016-d74e-43fc-b3fa-b61156a03799",
      "863ee341-6e5b-4dda-b279-f73b77070460"
    ],
    "original_app_user_id": "1bf2f016-d74e-43fc-b3fa-b61156a03799",
    "currency": null,
    "price": null,
    "price_in_purchased_currency": null,
    "subscriber_attributes": {
      "$email": {
        "value": "[email protected]",
        "updated_at_ms": 1746471203817
      },
      "$displayName": {
        "value": "Mister Mistoffelees",
        "updated_at_ms": 1746471203817
      },
      "$phoneNumber": {
        "value": "+19795551234",
        "updated_at_ms": 1746471203817
      },
      "my_custom_attribute_1": {
        "value": "catnip",
        "updated_at_ms": 1746471203817
      }
    },
    "store": "PLAY_STORE",
    "takehome_percentage": null,
    "offer_code": null,
    "tax_percentage": null,
    "commission_percentage": null,
    "metadata": null,
    "renewal_number": null,
    "type": "TEST",
    "id": "665CA53F-301D-46D3-A977-20C8A3EF336F",
    "app_id": "app54c5dea9ab",
    "api_version": "1.0",
    "querystring": null
  }
}