RudderStack is a warehouse-native customer data platform that helps businesses collect, transform, and route event data from apps, websites, servers, and databases to various tools, including data warehouses and APIs.

The RudderStack + PassKit integration allows you to trigger the creation, update, or removal of digital passes in Apple Wallet and Google Wallet using event data collected by RudderStack. You can connect customer actions like sign-ups, purchases, or membership changes directly to pass delivery using real-time or batch data flows.

This integration is useful for teams that already track events across systems and want to automatically send or update wallet passes without building custom tracking pipelines from scratch.

Setting Up The Integration

To connect RudderStack with PassKit:

  1. In PassKit, create and publish your pass project (e.g., loyalty, membership, or coupon).
  2. Go to Settings > Developer Tools in PassKit to find your API region, SDK host, and API prefix.
  3. Generate your API credentials for secure access to the PassKit API.
  4. In RudderStack, define the events you want to track (such as membership_signed_up, purchase_completed, or tier_upgraded).
  5. Set up a webhook destination in RudderStack that points to your middleware or directly to the PassKit API endpoint.
  6. Map the relevant fields from RudderStack events to your PassKit pass template (e.g., name, email, tier, voucher code).
  7. Optionally, use PassKit webhooks to track when passes are installed, updated, or deleted, and route that data back into your warehouse or product stack using RudderStack.

RudderStack gives you the flexibility to use event data from multiple sources including your website, backend, and data warehouse and send it to PassKit in a format that matches your pass requirements.

Common Use Cases

RudderStack allows you to connect data from your websites, apps, and warehouse to PassKit, so that wallet passes reflect real customer activity in real time or based on historical trends. This gives you flexible ways to issue, update, or remove passes based on how customers engage with your business.

Here are some of the most common ways businesses use this integration:

  • Send a digital wallet pass when a customer joins a loyalty program or signs up for a membership
  • Trigger pass updates when a customer reaches a new tier or earns a reward
  • Issue a coupon pass after a qualifying purchase or marketing event
  • Revoke or update a pass when a customer becomes inactive or unsubscribes
  • Use warehouse data to run batch pass updates for segments or campaigns

These use cases help reduce manual effort and ensure that customers always have an up-to-date pass on their device.

Industries That Benefit Most

This integration is well suited to companies that already track customer actions and events, and want to link that data directly to a mobile wallet experience. It works for both simple use cases like sending a one-time coupon, and more advanced cases like syncing loyalty tiers or membership levels.

Industries that benefit the most include:

  • Retail & Ecommerce Businesses
  • Subscription Services and Membership Programs
  • CPG and DTC Brands
  • Travel and Events
  • Marketing Teams Using Real-Time Segments

Whether you’re working with one-time promotions or long-term loyalty programs, this integration can help connect your data with something your customers can use immediately.

Requirements

To use this integration, you’ll need:

  • A PassKit account with a published pass project
  • A RudderStack account with access to event tracking and destination setup
  • API credentials from PassKit Developer Tools
  • A webhook destination or middleware to receive RudderStack data and call PassKit
  • Field mappings between RudderStack events and your PassKit pass template

You can use basic event tracking and pass delivery flows without custom code. More advanced setups, like warehouse-driven audience updates or large-scale syncs, may require developer support.

Support & Documentation

Helpful resources:

SDK and API Configuration Settings

Subscribe to PassKit Webhooks

Using Long-Lived API Tokens

These guides will help you set up your connection, manage authentication, and handle pass events correctly.

Frequently Asked Questions

Can I Send A Pass When Someone Signs Up Or Makes A Purchase?

Yes. With the RudderStack and PassKit integration, you can automatically create and send a digital wallet pass when a tracked event occurs, such as a new customer signing up or completing a purchase. You can set up RudderStack to collect these events from your website, app, or backend.

Once collected, the event data can be sent to a webhook or processing service that calls the PassKit API to create a new pass. This lets customers receive their pass quickly without needing any manual steps from your team.

Can I Map Custom Fields From RudderStack To My Wallet Pass?

Yes. RudderStack allows you to send a wide range of customer data as part of your event payloads. This data can include things like customer email, membership tier, loyalty points, promotion codes, and other custom fields. You can configure your workflow to pass this information into the corresponding fields on your PassKit template.

When the data in RudderStack changes, you can also send an update to PassKit so the pass reflects the latest information. This is useful for keeping things like tier levels or expiration dates current without having to update them manually.

What Happens If A Customer Cancels Or No Longer Qualifies For A Pass?

If a customer becomes inactive, cancels a subscription, or no longer meets the criteria for a pass, the integration can be used to automatically update or remove the pass from their Apple or Google Wallet. For example, RudderStack can track cancellation or downgrade events and forward them to a webhook that calls the PassKit API.

You can choose to show a message on the pass, change its appearance, or remove it entirely, depending on how you want to handle changes in eligibility. This helps you make sure that only current, qualified users have valid passes.

Do I Need A Developer To Use The RudderStack And PassKit Integration?

You might not need a developer for basic use cases. If you are only triggering simple events, such as sending a pass after a purchase or membership signup, and using tools like RudderStack’s webhook destination, you may be able to manage the setup yourself or with light technical help.

However, if you want to include logic based on customer attributes, run data transformations, or connect to your data warehouse, developer support will be helpful. More advanced implementations often involve writing middleware that can process the incoming event and make calls to the PassKit API with the correct format and security.