Appstack

In the Analytics section within Integrations, you can connect your Appstack account to Superwall:

Required Fields

Fill out the following fields and click the Enable Appstack button at the bottom right to save your changes:

• Access Token: Your Appstack API access token, used to authenticate requests.
• App ID: Your Appstack application ID, used to route events to the correct app.

Features

• Pass-Through Delivery: Raw Superwall webhook events are forwarded directly to Appstack without transformation
• Simple Configuration: Only an access token and app ID are required
• Credential Validation: Connection is verified before the integration goes live
• Production Events Only: Sandbox events are automatically filtered out

Configuration

Required Settings

Example Configuration

{
  "access_token": "your_appstack_access_token",
  "app_id": "your_appstack_app_id"
}

How It Works

Appstack is a pass-through integration. Unlike analytics integrations that map and transform events into platform-specific formats, the Appstack integration forwards the raw Superwall webhook event payload directly to Appstack.

When a subscription event occurs:

1. Superwall generates the webhook event.
2. The integration sends the complete, unmodified event payload to Appstack.
3. Appstack receives and processes the event on its end.

API Endpoint

Events are sent to:

POST https://api.event.appstack.tech/superwall/webhook/{app_id}

Request Headers

Content-Type: application/json
Authorization: <access_token>

The access_token is sent as the Authorization header value, and the app_id is included in the URL path.

Sandbox Handling

Sandbox events are automatically filtered out. Only production events are forwarded to Appstack. There is no option to include sandbox events or to configure a separate sandbox endpoint.

Testing the Integration

1. Validate Credentials

When you save the integration, Superwall sends a test event to the Appstack validation endpoint to confirm your credentials are correct:

POST https://api.event.appstack.tech/superwall/validate

If validation fails, double-check your access token and app ID.

2. Trigger a Production Event

Since sandbox events are filtered out, you will need a production transaction to verify end-to-end delivery:

• iOS: Use TestFlight with a sandbox Apple ID. StoreKit Configuration files do not generate App Store Server Notifications, so webhooks and downstream integrations will not fire.
• Google Play: Use license test accounts to perform sandbox purchases.
• Stripe: Use Stripe Test Mode to create sandbox transactions.

3. Verify in Appstack

Check your Appstack dashboard to confirm events are arriving and being processed correctly.

Troubleshooting

Events Not Appearing in Appstack

Possible causes:

• Invalid access token or app ID
• Events are from a sandbox environment (these are filtered out)
• Network or endpoint issues on the Appstack side

Solutions:

1. Re-save the integration to trigger credential validation
2. Confirm you are generating production (not sandbox) events
3. Verify your access token and app ID match what is shown in your Appstack dashboard
4. Contact Appstack support if credentials are correct but events are still not arriving

Credential Validation Failing

Possible causes:

• Incorrect access token
• Incorrect app ID
• Appstack service is temporarily unavailable

Solutions:

1. Copy the access token and app ID directly from your Appstack dashboard to avoid typos
2. Ensure your Appstack account is active and in good standing
3. Try again after a few minutes if the Appstack service may be experiencing downtime