Skip to main content

Destination

Nexla's bi-directional connectors allow data to flow both to and from any location, making it simple to create a FlexFlow, DB-CDC, Spark ETL, or Replication data flow that sends data to an Outbrain Amplify location.
outbrain_amplify_api.png

Outbrain Amplify

Create an Outbrain Amplify Destination​

  1. Click the + icon on the Nexset that will be sent to the Outbrain Amplify destination, and select the Send to Destination option from the menu.

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

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

    Outbrain Amplify destinations can also be configured manually, allowing you to send data to Outbrain Amplify endpoints not included in the pre-built templates or apply further customizations to exactly suit your needs.
    • To configure this destination manually, follow the instructions in Configure Manually.

Configure Using a Template​

Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Outbrain Amplify endpoints. Each template is designed specifically for the corresponding Outbrain Amplify endpoint, making destination setup easy and efficient.

  • To configure this destination using a template, select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.

    Create Conversion Events in Table

    This endpoint template creates conversion events for a marketer from records in a Nexset. Use this template when you need to create conversion events in Outbrain Amplify for tracking conversions, attributing conversions to campaigns, or other conversion tracking purposes. Please check the API documentation link for all required properties in the Nexset record.

    • Enter the marketer ID in the Marketer ID field. This should be the unique identifier of the marketer for which you want to create conversion events. The marketer ID determines which marketer will receive the conversion events. You can find the marketer ID by using the "Fetch Marketers" endpoint.

    This endpoint sends data as JSON in the request body to create conversion events for a marketer in your Outbrain Amplify account. Each record from your Nexset will be sent as a separate API request to create a new conversion event in Outbrain Amplify. The request body should contain the conversion event data in the format required by the Outbrain Amplify API.

    The conversion event structure must match the Outbrain Amplify API's expected format. Please check the API documentation link for all required properties in the Nexset record. For detailed information about conversion event creation, request body formats, available event properties, and required record structures, see the Outbrain Amplify API documentation.

Configure Manually​

Outbrain Amplify destinations can be manually configured to send data to any valid Outbrain Amplify API endpoint. Manual configuration provides maximum flexibility for accessing endpoints not covered by pre-built templates or when you need custom API configurations.

Using manual configuration, you can also configure Nexla to automatically send the response received from the Outbrain Amplify API after each call to a new Nexla webhook data source.

API Method​

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

  2. Select the API method that will be used for calls to the Outbrain Amplify API from the Method pulldown menu. Outbrain Amplify API typically uses POST method for creating resources.

Data Format​

  1. Select the format in which the Nexset data will be sent to the Outbrain Amplify API from the Content Format pulldown menu. Outbrain Amplify API expects JSON format for all requests.

API Endpoint URL​

  1. Enter the URL of the Outbrain Amplify API endpoint to which data will be sent in the URL field. This should be the complete URL including your API server URL (from your credential), the API path (e.g., /marketers/{marketer_id}/conversionEvents), and any required query parameters. Include any required path parameters in the URL.

Ensure the API endpoint URL is correct and accessible with your current credentials. The Outbrain Amplify API endpoint URL should point to the endpoint where you want to create resources. The endpoint URL should include your API server URL and the appropriate API path. You can test the endpoint using the Test button after configuring the URL.

Request Body​

  1. Configure the request body that will be sent to the Outbrain Amplify API. The request body should contain the resource data formatted as JSON, with field names matching the Outbrain Amplify API's expected structure. The request body format is typically {message.json} to send the entire Nexset data as JSON, or you can construct a custom JSON structure with specific field mappings.

The request body must be valid JSON and must match the Outbrain Amplify API's expected format for the specific endpoint you're using. Outbrain Amplify API uses specific structures for different endpoints (conversion events, etc.). For detailed information about request body formats, available endpoints, and resource structures, see the Outbrain Amplify API documentation.

Save the Destination​

  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 destination configuration for later use.