Skip to main content

Data Source

Follow the instructions below to create a new data flow that ingests data from a Medallia Journey Analytics source in Nexla.
medallia_journey_api.png

Medallia Journey Analytics

Create a New Data Flow​

  1. To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Then, select the desired flow type from the list, and click the Create button.

  2. Select the Medallia Journey Analytics connector tile from the list of available connectors. Then, select the credential that will be used to connect to your Medallia Journey Analytics account, and click Next; or, create a new Medallia Journey Analytics credential for use in this flow.

  3. In Nexla, Medallia Journey Analytics data sources can be created using pre-built endpoint templates, which expedite source setup for common Medallia Journey Analytics endpoints. Each template is designed specifically for the corresponding Medallia Journey Analytics endpoint, making source configuration easy and efficient.
    • To configure this source using a template, follow the instructions in Configure Using a Template.

    Medallia Journey Analytics sources can also be configured manually, allowing you to ingest data from Medallia Journey Analytics endpoints not included in the pre-built templates or apply further customizations to exactly suit your needs.
    • To configure this source manually, follow the instructions in Configure Manually.

Configure Using a Template​

Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common Medallia Journey Analytics endpoints. Each template is designed specifically for the corresponding Medallia Journey Analytics endpoint, making data source setup easy and efficient.

Endpoint Settings​

  • 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. Click on an endpoint to see more information about it and how to configure your data source for this endpoint.

    Fetch Project Data using CQL Query

    This endpoint template fetches data for a project by submitting a CQL (Cooladata Query Language) query. Use this template when you need to retrieve specific data from a Medallia Journey Analytics project using a custom CQL query. This allows you to filter, aggregate, and transform data according to your specific requirements.

    • Enter the project ID in the Project ID field. This is the unique identifier for the Medallia Journey Analytics project from which you want to fetch data. You can find the project ID by using the "Get all Projects" endpoint or in your Medallia Journey Analytics account.
    • Enter your CQL query in the Query field. This should be a valid CQL query that retrieves the data you need from the specified project. The CQL query is sent in the request body as a tq parameter. CQL queries allow you to filter, aggregate, and transform data according to your specific requirements.

    CQL (Cooladata Query Language) is a powerful query language that allows you to filter, aggregate, and transform data from Medallia Journey Analytics projects. The query is sent as a POST request to the CQL endpoint with the query in the tq parameter. For detailed information about CQL syntax, query examples, and available functions, see the Medallia Journey Analytics Query API documentation.

    Project IDs are unique identifiers that can be obtained from the "Get all Projects" endpoint or from your Medallia Journey Analytics account. Ensure you have the correct Project ID before configuring this endpoint.

    Get all Projects

    This endpoint template retrieves a list of all projects that the authenticated user has permissions to access in your Medallia Journey Analytics account. Use this template when you need to discover available projects, retrieve project metadata, or identify project IDs for use with other endpoints.

    • This endpoint automatically retrieves all projects accessible to your API token. No additional configuration is required beyond selecting this endpoint template.

    This endpoint returns a list of all projects that the authenticated user has permissions to access, including project IDs, names, and metadata. Use this endpoint to discover available projects before configuring other endpoints that require a project ID. The endpoint returns project information including project structure and available data fields.

    For detailed information about project structure, available fields, and API endpoints, see the Medallia Journey Analytics Discovery API documentation.

Endpoint Testing​

Once the selected endpoint template has been configured, Nexla can retrieve a sample of the data that will be fetched according to the current settings. This allows users to verify that the source is configured correctly before saving.

  • To test the current endpoint configuration, click the Test button to the right of the endpoint selection menu. Sample data will be fetched & displayed in the Endpoint Test Result panel on the right.

  • If the sample data is not as expected, review the selected endpoint and associated settings, and make any necessary adjustments. Then, click the Test button again, and check the sample data to ensure that the correct information is displayed.

Configure Manually​

Medallia Journey Analytics data sources can be manually configured to ingest data from any valid Medallia Journey Analytics 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 Medallia Journey Analytics sources, such as sources that use chained API calls to fetch data from multiple endpoints or sources that require custom request headers or parameters.

API Method​

  1. To manually configure this source, select the Advanced tab at the top of the configuration screen.

  2. Select the API method that will be used for calls to the Medallia Journey Analytics API from the Method pulldown menu. Medallia Journey Analytics API uses GET method for retrieving project lists and POST method for executing CQL queries.

API Endpoint URL​

  1. Enter the URL of the Medallia Journey Analytics 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://), the API base URL (app.cooladata.com), the API version path (/api/v2/ or /api/v3/), and the endpoint path (e.g., https://app.cooladata.com/api/v3/projects for listing projects or https://app.cooladata.com/api/v2/projects/{project_id}/cql for CQL queries).

Ensure the API endpoint URL is correct and accessible with your current credentials. The Medallia Journey Analytics API uses different API versions (v2 and v3) for different endpoints. You can test the endpoint using the Test button after configuring the URL.

Request Body (if applicable)​

  1. If your endpoint requires a request body (such as CQL queries), configure the request body that will be sent to the Medallia Journey Analytics API. For CQL queries, the request body format is typically tq={your_cql_query} where the query is sent as a form parameter.

Response Data Path​

  1. Enter the JSONPath expression in the Response Data Path field to specify which part of the API response should be treated as the relevant data by Nexla. For Medallia Journey Analytics API responses, use $[*] to extract all items from a response array, or $ to extract the entire response object.

The JSONPath expression must correctly reference the structure of your Medallia Journey Analytics API response. Medallia Journey Analytics API responses may return data directly as an array or within nested objects. Ensure your JSONPath expression matches the structure returned by your specific endpoint. The JSONPath expression determines which data will be extracted and processed by Nexla.

Save the Data Source​

  1. Once all of the relevant steps in the above sections have been completed, click the Next button to proceed with the rest of the data flow configuration, or click Save to save the data source configuration for later use.