Skip to main content

Jampp

Jampp is a mobile marketing platform that leverages machine learning and predictive algorithms to deliver programmatic advertising solutions, helping app businesses grow through intelligent user acquisition, retargeting, and performance optimization across mobile channels.

Jampp icon

Power end-to-end data operations for your Jampp API with Nexla. Our bi-directional Jampp connector is purpose-built for Jampp, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Jampp or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Jampp workflows fast, secure, and fully governed.

Features

Type: API

SourceDestination

  • Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
  • Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
  • API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
  • Request optimization with intelligent batching, retry, and caching to minimize API calls and costs

Prerequisites​

Before creating a Jampp credential, you need to obtain OAuth2 credentials (Client ID and Client Secret) from your Jampp account. The OAuth2 credentials are required for 2-legged OAuth2 authentication with the Jampp Reporting API.

To obtain your OAuth2 credentials, you need to have a Jampp account and access to the Jampp developer portal or account settings. Once you have access, you can create an application or obtain OAuth2 credentials from your account settings. The Client ID and Client Secret are used for 2-legged OAuth2 authentication, which uses the client credentials flow to obtain an access token. This authentication method is suitable for server-to-server communication where user interaction is not required. The access token is then sent in the Authorization header with the Bearer prefix for all API requests to the Jampp Reporting API. The Jampp Reporting API provides access to advertising performance data, campaign metrics, and reporting information. For detailed information about OAuth2 credential setup, authentication flows, and available API endpoints, refer to the Jampp Reporting API documentation.

Authenticate​

Credentials required​

FieldRequiredSecretDescription
Client IDYesNoJampp Client ID
Client SecretYesYesJampp Client Secret

Create a credential in Nexla​

  1. After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.

New Credential Overlay – Jampp

JamppCred.png
  1. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

Jampp uses 2-legged OAuth2 authentication with the client credentials flow. This authentication method is designed for server-to-server communication where user interaction is not required. The Client ID and Client Secret are used to obtain an access token, which is then used to authenticate API requests to the Jampp Reporting API.

  1. Enter your Jampp Client ID in the Client ID field. This is the Client ID you obtained from your Jampp account settings or developer portal. The Client ID is a unique identifier for your application and is used along with the Client Secret to obtain an access token for API authentication. The Client ID is not sensitive and can be shared, but it should be kept secure to prevent unauthorized use.

  2. Enter your Jampp Client Secret in the Client Secret field. This is the Client Secret you obtained from your Jampp account settings or developer portal. The Client Secret is used along with the Client ID to obtain an access token for API authentication. The Client Secret is sensitive information and must be kept confidential.

    Keep your Client Secret secure and do not share it publicly. The Client Secret provides access to your Jampp account data and should be treated as sensitive information. If your Client Secret is compromised, you should immediately regenerate it in your Jampp account settings. Your Jampp Client Secret can be found in your Jampp account settings or developer portal where you manage your application credentials. The Client Secret is used along with the Client ID to obtain an access token using the 2-legged OAuth2 client credentials flow. Nexla automatically obtains and refreshes the access token as needed. The access token does not expire automatically, but you can regenerate credentials if needed. For detailed information about finding your Client Secret, setting up OAuth2 credentials, and managing access tokens, see the Jampp Reporting API documentation.

  3. Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.

Use as a data source​

To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Jampp connector tile, then select the credential that will be used to connect to the Jampp account, and click Next; or, create a new Jampp credential for use in this flow.

Endpoint templates​

Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Jampp endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.

Fetch reports by Query

Fetch reports of metrics grouped by the dimensions the user is interested in.

  • Enter the GraphQL query in the GraphQL Query field. This should be a valid GraphQL query that defines the metrics and dimensions you want to retrieve from the Jampp Reporting API. The GraphQL query determines what data will be fetched and how it will be structured in the response.
  • The endpoint uses POST requests to https://reporting-api.jampp.com/v1/graphql to execute GraphQL queries. The endpoint URL is automatically constructed based on the Jampp Reporting API base URL.
  • The request body contains the GraphQL query in JSON format: {"query": "{your_graphql_query}"}. The query is sent as a string value in the JSON body.
  • The endpoint does not use pagination (iteration.type: static.url) and returns a single response. The response data path is $.results[*], which extracts all results from the results array in the API response.
  • The date format is yyyy-MM-dd with a time unit of dd (days), which is used for incremental data extraction based on record dates.

This endpoint retrieves advertising performance reports from the Jampp Reporting API using GraphQL queries. The endpoint requires 2-legged OAuth2 authentication via the Authorization: Bearer {token} header, which is handled automatically by your credential configuration. The access token is obtained using the OAuth2 client credentials flow with your Client ID and Client Secret. GraphQL queries allow you to specify exactly what metrics and dimensions you want to retrieve, making it a flexible way to query advertising data. The query syntax follows GraphQL standards and allows you to filter, group, and aggregate data as needed. For detailed information about GraphQL query syntax, available metrics and dimensions, and API response formats, see the Jampp Reporting API documentation.

Manual configuration​

Jampp data sources can be manually configured to ingest data from any valid Jampp Reporting API endpoint. Manual configuration provides maximum flexibility for accessing endpoints not covered by pre-built templates or when you need custom API configurations.

With manual configuration, you can also create more complex Jampp sources, such as sources that use custom GraphQL queries, different HTTP methods, or custom data transformations.

Content Format​

  1. Select the format in which the data from the Jampp Reporting API will be received from the Content Format pulldown menu. Nexla will automatically parse the data in the selected format. The Jampp Reporting API typically returns data in JSON format.

API Endpoint URL​

  1. Enter the URL of the Jampp Reporting API endpoint from which this source will fetch data in the Set API URL field. This should be the complete URL including the protocol (https://) and any required path parameters. Jampp Reporting API endpoints typically follow the pattern https://reporting-api.jampp.com/v1/{endpoint_path}.

Ensure the API endpoint URL is correct and accessible with your current credentials. You can test the endpoint using the Test button after configuring the URL. The endpoint requires 2-legged OAuth2 authentication via the Authorization: Bearer {token} header, which is handled automatically by your credential configuration. The access token is obtained using the OAuth2 client credentials flow with your Client ID and Client Secret. For detailed information about Jampp Reporting API endpoints, authentication, and available APIs, see the Jampp Reporting API documentation.