Allowing ETL access to my data on Linkedin ETL can access your LinkedIn data. This article details creating the LinkedIn connection and the process of building a data pipeline to read LinkedIn data in ETL. There are also pre-built templates to read data from LinkedIn. Please see Create a package from a template for instructions on using a template.

To create a LinkedIn connection in ETL:

    1. Click the Connections icon (lightning bolt) on the top left menu.
    2. To create a connection, click New connection. thumbnail image
    3. Choose LinkedIn.
    4. If required, sign in to LinkedIn.
    5. Click Connect to authorize ETL access to your LinkedIn account.
    6. In the new LinkedIn connection window, name the connection and click Create LinkedIn connection.

To modify LinkedIn connections in ETL:

    1. Click the Connections icon (lightning bolt) on the top left menu.
    2. Click a connection to open it and re-connect if your password has changed or the token has expired. Make any necessary changes, then click Reconnect, and Save changes. To exit the LinkedIn connection window without changes, click Back to connections (grey tab on the left side) on the LinkedIn connection window.
    3. To delete a LinkedIn connection, click on the three vertical dots on the far right of the connection listing and select the Delete connection option.

To build a data pipeline to read LinkedIn campaign data in ETL:thumbnail image

REST API Component: get_campaigns

  • Authentication - Click Connection and then select your LinkedIn connection. If you haven't created your LinkedIn connection yet, click + New and follow the instructions found above. thumbnail image
  • URL - Enter the URL for the Campaigns endpoint of the LinkedIn API: Make sure the method is set to GET.thumbnail image
  • Response - Make sure the JSON response type.  Edit the Base record JSONPath Expression field like this: $.elements[*].thumbnail image
  • Input fields - Click Select all to move all the Available fields over to the Selected fields or pick and choose which fields you would like by clicking on the + icon next to the field name in the Available Fields column. Then click Save.thumbnail image

Select Component: extract_campaign_meta

  • Click Autofill to bring in all the fields from the source component. Parse the nested fields inside the five Map fields (totalBudget, locale, runSchedule, changeAuditStamps, and unitCost) using this syntax: field_name#'key' For example, totalBudget#'amount'. For more information on parsing JSON data see this article. Click Save. thumbnail image

Destination Component: campaigns

  • The template shows a Redshift destination component; however, if you'd prefer to use a different destination, delete the Redshift component and select a destination component of your choice. thumbnail image
  • Choose target connection - Select your target connection. If you haven't created your connection yet, click + New.thumbnail image
  • Destination properties - Fill in the values for target schema and table, select an operation type, pre or post-action SQL, and advanced options.
  • Schema mapping - Click Auto-fill to bring in all of the fields. If you've selected a Merge operation type, click the Key box next to the merge key field(s). Click Save. thumbnail image