Skip to main content Skip to complementary content

Apple Store Connect 

Apple Store Connect allows users to follow the purchase and download of their apps.

Supported update methods

For more information, see An overview of target update methods.

  • Change data capture (CDC)

  • Reload and compare

  • Change data capture (CDC) using Change Tables

  • Full load

  • Change data capture (CDC)

  • Reload

Preparing for authentication

To access your Apple Store Connect data, you need to authenticate the connection with your account credentials.

To generate a key ID:

  1. In App Store Connect, navigate to Users and Access > API Keys.
  2. Click Generate an API.
  3. Copy the key ID and download the private key.
Information noteMake sure that the account you use has read access to the tables you want to fetch.

Creating the connection

For more information, see Connecting to SaaS applications.

  1. Fill in the required connection properties.
  2. Provide a name for the connection in Connection name.

  3. Select Open connection metadata to define metadata for the connection when it has been created.

  4. Click Create.

Connection settings
Setting Description
Data gateway

Select a Data Movement gateway if required by your use case.

Information note

This field is not available with the Qlik Talend Cloud Starter subscription, as it does not support Data Movement gateway. If you have another subscription tier and do not want to use Data Movement gateway, select None.

For information on the benefits of Data Movement gateway and use cases that require it, see Qlik Data Gateway - Data Movement.

Key ID Key ID.
Private Key Private key.
Issuer ID

Issuer ID.

In App Store Connect, navigate to Users and Access > API Keys.

Vendor Number Vendor number starting with an 8.
Regions

Regions in uppercase separated by a space.

Example: AU BR CA US.

Start Month

Start month of the finance reports in the format YYYY-MM.

Example: 2024-05.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!