# Standard Placements

Standard placements are events that Superwall automatically manages. The following [Superwall Events](/docs/sdk/guides/3rd-party-analytics/tracking-analytics) are registered by the SDK and can be added as placements in campaigns to present paywalls:

* [`app_install`](#app_install)
* [`app_launch`](#app_launch)
* [`deepLink_open`](#deeplink_open)
* [`session_start`](#session_start)
* [`paywall_decline`](#paywall_decline)
* [`transaction_fail`](#transaction_fail)
* [`transaction_abandon`](#transaction_abandon)
* [`survey_response`](#survey_response)
* [`touches_began`](#touches_began)

`app_install` [#app_install]

Usage [#usage]

This is registered when the SDK is configured for the first time. Use it for first-launch onboarding flows or one-time offers.

Parameters [#parameters]

These parameters are always available:

<TypeTable
  propColumnWidth="50%"
  type="{
  app_session_id: {
    description: 'Identifier for the current app session.',
    type: 'string',
    required: true,
  },
  is_superwall: {
    description: 'Always true for Superwall events.',
    type: 'boolean',
    required: true,
  },
  using_purchase_controller: {
    description: 'True when a custom purchase controller is configured.',
    type: 'boolean',
    required: true,
  },
}"
/>

`app_launch` [#app_launch]

Usage [#usage-1]

This is registered when the app is launched from a cold start. Use it to present paywalls on fresh launches.

Parameters [#parameters-1]

Same as `app_install`:

<TypeTable
  propColumnWidth="50%"
  type="{
  app_session_id: {
    description: 'Identifier for the current app session.',
    type: 'string',
    required: true,
  },
  is_superwall: {
    description: 'Always true for Superwall events.',
    type: 'boolean',
    required: true,
  },
  using_purchase_controller: {
    description: 'True when a custom purchase controller is configured.',
    type: 'boolean',
    required: true,
  },
}"
/>

`deepLink_open` [#deeplink_open]

Usage [#usage-2]

This is registered when a user opens the app via a deep link. First, you need to make sure to [tell Superwall when a deep link has been opened](/docs/sdk/quickstart/in-app-paywall-previews).

You can use the URL parameters of the deep link within your rules. This works for both URL schemes and universal links.

For example, you could make three conditions to match this deep link: `myapp://paywall?offer=July20`. Here's how:

1. Add a rule to see if the event is `deepLink_open`. See the `paywall_decline` example below for how to add a standard placement.
2. Add `params.offer` is equal to whatever you've made, like `July20` for a timeboxed offer you made in that month.
3. Then, you'd also add `params.path` is equal to the text of a path you setup, like `paywall`.

Parameters [#parameters-2]

After the app has emitted the first `deepLink_open` event for a given URL, these fields become available to audience filters:

<TypeTable
  propColumnWidth="50%"
  type="{
  'params.url': {
    description: 'Full deep link URL.',
    type: 'string',
    required: true,
  },
  'params.path': {
    description: 'Path portion of the URL.',
    type: 'string',
    required: true,
  },
  'params.host': {
    description: 'Host portion of the URL.',
    type: 'string',
    required: true,
  },
  'params.query': {
    description: 'Full query string.',
    type: 'string',
    required: true,
  },
  'params.pathExtension': {
    description: 'Path extension of the URL.',
    type: 'string',
    required: true,
  },
  'params.lastPathComponent': {
    description: 'Last path component of the URL.',
    type: 'string',
    required: true,
  },
  'params.fragment': {
    description: 'Fragment portion of the URL.',
    type: 'string',
    required: true,
  },
  'params.<query_param>': {
    description:
      'Optional. Any query string parameter (for example, `params.offer` for `?offer=July20`).',
    type: 'string',
  },
}"
/>

`session_start` [#session_start]

Usage [#usage-3]

This is registered when the app is opened after at least 60 minutes since the last `app_close`.

Parameters [#parameters-3]

Same as `app_install`:

<TypeTable
  propColumnWidth="50%"
  type="{
  app_session_id: {
    description: 'Identifier for the current app session.',
    type: 'string',
    required: true,
  },
  is_superwall: {
    description: 'Always true for Superwall events.',
    type: 'boolean',
    required: true,
  },
  using_purchase_controller: {
    description: 'True when a custom purchase controller is configured.',
    type: 'boolean',
    required: true,
  },
}"
/>

`paywall_decline` [#paywall_decline]

Usage [#usage-4]

This is registered when a user manually dismisses any paywall. You can combine this with rules to show a paywall when a user closes a specific paywall. First, [add](/docs/dashboard/dashboard-campaigns/campaigns-placements#adding-a-placement) the standard placement to a campaign:

<img src="__img0" />

Then, create a filter in the audience using it:

<img src="__img1" />

Here, when a user closes the paywall named `PaywallA`, a new paywall will show.

Note that you can't reference parameters that you've passed in to your original register call in your rules for `paywall_decline`.

Parameters [#parameters-4]

Audience filters for `paywall_decline` placements can use the following parameters (empty values mean the field isn't applicable):

<TypeTable
  propColumnWidth="50%"
  type="{
  paywall_id: {
    description: 'The paywall ID where the decline occurred.',
    type: 'string',
    required: true,
  },
  paywall_name: {
    description: 'The paywall name shown in the dashboard.',
    type: 'string',
    required: true,
  },
  presented_by_event_name: {
    description:
      'The placement name that originally presented the paywall (for example, `onboarding`). Empty if the paywall was presented programmatically.',
    type: 'string',
    required: true,
  },
  presented_by: {
    description: 'How the paywall was presented (`placement` or `programmatically`).',
    type: 'string',
    required: true,
  },
  paywall_product_ids: {
    description: 'Comma-separated product identifiers attached to the paywall.',
    type: 'string',
    required: true,
  },
  primary_product_id: {
    description: 'The first product on the paywall, or empty if none.',
    type: 'string',
    required: true,
  },
  secondary_product_id: {
    description: 'The second product on the paywall, or empty if none.',
    type: 'string',
    required: true,
  },
  tertiary_product_id: {
    description: 'The third product on the paywall, or empty if none.',
    type: 'string',
    required: true,
  },
  '<product_name>_product_id': {
    description:
      'Product identifier keyed by the product name (for example, `annual_product_id`).',
    type: 'string',
    required: true,
  },
  is_free_trial_available: {
    description:
      'True when any introductory offer is available (including both free and paid trials).',
    type: 'boolean',
    required: true,
  },
  feature_gating: {
    description: 'Feature gating behavior for the paywall.',
    type: 'string',
    required: true,
  },
}"
/>

`transaction_fail` [#transaction_fail]

Usage [#usage-5]

This is registered when the payment sheet fails to complete a transaction (this does not include user cancellation). Use it to show an exit offer after a failed attempt.

Parameters [#parameters-5]

Audience filters for `transaction_fail` placements can use the following parameters (empty values mean the field isn't applicable):

<TypeTable
  propColumnWidth="50%"
  type="{
  paywall_id: {
    description: 'The paywall ID where the failure occurred.',
    type: 'string',
    required: true,
  },
  paywall_name: {
    description: 'The paywall name shown in the dashboard.',
    type: 'string',
    required: true,
  },
  presented_by_event_name: {
    description:
      'The placement name that originally presented the paywall (for example, `onboarding`). Empty if the paywall was presented programmatically.',
    type: 'string',
    required: true,
  },
  presented_by: {
    description: 'How the paywall was presented (`placement` or `programmatically`).',
    type: 'string',
    required: true,
  },
  paywall_product_ids: {
    description: 'Comma-separated product identifiers attached to the paywall.',
    type: 'string',
    required: true,
  },
  primary_product_id: {
    description: 'The first product on the paywall, or empty if none.',
    type: 'string',
    required: true,
  },
  secondary_product_id: {
    description: 'The second product on the paywall, or empty if none.',
    type: 'string',
    required: true,
  },
  tertiary_product_id: {
    description: 'The third product on the paywall, or empty if none.',
    type: 'string',
    required: true,
  },
  '<product_name>_product_id': {
    description:
      'Product identifier keyed by the product name (for example, `annual_product_id`).',
    type: 'string',
    required: true,
  },
  is_free_trial_available: {
    description:
      'True when any introductory offer is available (including both free and paid trials).',
    type: 'boolean',
    required: true,
  },
  feature_gating: {
    description: 'Feature gating behavior for the paywall.',
    type: 'string',
    required: true,
  },
}"
/>

The event payload also includes a failure `message`; see [Superwall Events](/docs/sdk/guides/3rd-party-analytics/tracking-analytics) for full details.

`transaction_abandon` [#transaction_abandon]

Usage [#usage-6]

This is registered when a user dismisses the store purchase sheet before the transaction completes. If a transaction-abandon paywall matches, Superwall immediately closes the current paywall and presents the new one.

Parameters [#parameters-6]

Audience filters for `transaction_abandon` placements can use the following parameters (empty values mean the field isn't applicable):

<TypeTable
  propColumnWidth="50%"
  type="{
  paywall_id: {
    description: 'The paywall ID where the transaction was started.',
    type: 'string',
    required: true,
  },
  paywall_name: {
    description: 'The paywall name shown in the dashboard.',
    type: 'string',
    required: true,
  },
  presented_by_event_name: {
    description:
      'The placement name that originally presented the paywall (for example, `onboarding`). Empty if the paywall was presented programmatically.',
    type: 'string',
    required: true,
  },
  presented_by: {
    description: 'How the paywall was presented (`placement` or `programmatically`).',
    type: 'string',
    required: true,
  },
  abandoned_product_id: {
    description: 'The product identifier the user attempted to purchase before canceling.',
    type: 'string',
    required: true,
  },
  paywall_product_ids: {
    description: 'Comma-separated product identifiers attached to the paywall.',
    type: 'string',
    required: true,
  },
  primary_product_id: {
    description: 'The first product on the paywall, or empty if none.',
    type: 'string',
    required: true,
  },
  secondary_product_id: {
    description: 'The second product on the paywall, or empty if none.',
    type: 'string',
    required: true,
  },
  tertiary_product_id: {
    description: 'The third product on the paywall, or empty if none.',
    type: 'string',
    required: true,
  },
  '<product_name>_product_id': {
    description:
      'Product identifier keyed by the product name (for example, `annual_product_id`).',
    type: 'string',
    required: true,
  },
  is_free_trial_available: {
    description:
      'True when any introductory offer is available (including both free and paid trials).',
    type: 'boolean',
    required: true,
  },
  feature_gating: {
    description: 'Feature gating behavior for the paywall.',
    type: 'string',
    required: true,
  },
}"
/>

For example, to show a transaction-abandon paywall only for onboarding paywalls, add a `transaction_abandon` placement and set `presented_by_event_name` to `onboarding`. To limit it to a single paywall, add `paywall_id` as an additional condition.

`survey_response` [#survey_response]

Usage [#usage-7]

This is registered when a response to a paywall survey has been recorded. First, you need to make sure your paywall [has a survey attached](/docs/dashboard/surveys).

You can combine this with rules to show a paywall whenever a survey response is recorded or when the user gives a specific response. Again, [add](/docs/dashboard/dashboard-campaigns/campaigns-placements#adding-a-placement) the standard placement `survey_response` to a campaign. Then, add another condition using `survey_selected_option_title` that's equal to the text of a particular response.

For example, if the user selected a survey option named `Too Expensive`, you could present another paywall with a discounted option. This is a great opportunity to show a discounted paywall to improve your conversion rate.

Parameters [#parameters-7]

Audience filters for `survey_response` placements can use the following parameters (empty values mean the field isn't applicable):

<TypeTable
  propColumnWidth="50%"
  type="{
  survey_selected_option_title: {
    description: 'The text of the selected survey option.',
    type: 'string',
    required: true,
  },
  survey_selected_option_id: {
    description: 'The ID of the selected survey option.',
    type: 'string',
    required: true,
  },
  survey_custom_response: {
    description: 'Optional. Custom response text when the user provides their own answer.',
    type: 'string',
  },
  survey_id: {
    description: 'The survey ID.',
    type: 'string',
    required: true,
  },
  survey_assignment_key: {
    description: 'The survey assignment key.',
    type: 'string',
    required: true,
  },
}"
/>

`touches_began` [#touches_began]

Usage [#usage-8]

This is registered when the user touches the app's UIWindow for the first time. It is only tracked if there is an active `touches_began` placement in a campaign.

Parameters [#parameters-8]

Same as `app_install`:

<TypeTable
  propColumnWidth="50%"
  type="{
  app_session_id: {
    description: 'Identifier for the current app session.',
    type: 'string',
    required: true,
  },
  is_superwall: {
    description: 'Always true for Superwall events.',
    type: 'boolean',
    required: true,
  },
  using_purchase_controller: {
    description: 'True when a custom purchase controller is configured.',
    type: 'boolean',
    required: true,
  },
}"
/>