Skip to main content
Dub

Swift

How to add the Dub iOS SDK to your Swift project
1 min read

Prerequisites#

Before you get started, make sure you have the following:

  1. Obtain your publishable key (DUB_PUBLISHABLE_KEY) from your workspace's Tracking settings page.
  2. You would also want to have your custom domain (DUB_DOMAIN) handy as well.
  3. (Optional) If you plan to track conversions, make sure to enable conversion tracking for your links.

Quickstart#

This quick start guide will show you how to get started with Dub iOS SDK in your Swift project.

Install the Dub iOS SDK#

Before installing, ensure your environment meets these minimum requirements:

Build Tools:

  • Xcode 16+
  • Swift 4.0+

Platforms:

  • iOS 16.0+
  • macOS 10.13 (Ventura)+

The Dub iOS SDK can be installed using the Swift Package Manager.

In Xcode, select File > Add Package Dependencies and add https://github.com/dubinc/dub-ios as the repository URL. Select the latest version of the SDK from the release page.

Initialize the SDK#

You must call Dub.setup with your publishable key and domain prior to being able to use the dub instance.

Call trackOpen on the dub instance to track deep link and deferred deep link open events. The trackOpen function should be called once without a deepLink parameter on first launch, and then again with the deepLink parameter whenever the app is opened from a deep link.

Warning

UIKit apps: If your AppDelegate has multiple URL handlers chained with || (e.g., Facebook/Meta SDK alongside Dub), the short-circuit evaluation may prevent handleDeepLink and trackOpen from being called. Make sure all handlers execute independently. See the troubleshooting guide for details and a fix.

Track lead events (optional)#

To track lead events, call trackLead on the dub instance with your customer's external ID, name, and email.

Lead event attributes

Here are the properties you can include when sending a lead event:

PropertyRequiredDescription
clickIdYesThe unique ID of the click that the lead conversion event is attributed to. You can read this value from dub_id cookie. If an empty string is provided (i.e. if you're using tracking a deferred lead event), Dub will try to find an existing customer with the provided customerExternalId and use the clickId from the customer if found.
eventNameYesThe name of the lead event to track. Can also be used as a unique identifier to associate a given lead event for a customer for a subsequent sale event (via the leadEventName prop in /track/sale).
customerExternalIdYesThe unique ID of the customer in your system. Will be used to identify and attribute all future events to this customer.
customerNameNoThe name of the customer. If not passed, a random name will be generated (e.g. "Big Red Caribou").
customerEmailNoThe email address of the customer.
customerAvatarNoThe avatar URL of the customer.
modeNoThe mode to use for tracking the lead event. async will not block the request; wait will block the request until the lead event is fully recorded in Dub; deferred will defer the lead event creation to a subsequent request.
metadataNoAdditional metadata to be stored with the lead event. Max 10,000 characters.

Track sale events (optional)#

To track sale events, call trackSale on the dub instance with your customer's user ID and purchase information.

Sale event attributes

Here are the properties you can include when sending a sale event:

PropertyRequiredDescription
customerExternalIdYesThe unique ID of the customer in your system. Will be used to identify and attribute all future events to this customer.
amountYesThe amount of the sale in cents.
paymentProcessorNoThe payment processor that processed the sale (e.g. Stripe, Shopify). Defaults to "custom".
eventNameNoThe name of the event. Defaults to "Purchase".
invoiceIdNoThe invoice ID of the sale. Can be used as a idempotency key – only one sale event can be recorded for a given invoice ID.
currencyNoThe currency of the sale. Defaults to "usd".
metadataNoAn object containing additional information about the sale.
clickIdNo[For direct sale tracking]: The unique ID of the click that the sale conversion event is attributed to. You can read this value from dub_id cookie.
customerNameNo[For direct sale tracking]: The name of the customer. If not passed, a random name will be generated.
customerEmailNo[For direct sale tracking]: The email address of the customer.
customerAvatarNo[For direct sale tracking]: The avatar URL of the customer.

Examples#

Here are some open-source code examples that you can reference: