Skip to main content

LinkedIn Marketing Data Source

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 ingests data from a LinkedIn Marketing source.
limktg_api.png

LinkedIn Marketing

Follow the instructions below to create a new data flow that ingests data from a LinkedIn Marketing source in Nexla.

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 LinkedIn Marketing connector tile from the list of available connectors. Then, select the credential that will be used to connect to the LinkedIn Marketing account, and click Next; or, create a new LinkedIn Marketing credential for use in this flow.

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

    LinkedIn Marketing sources can also be configured manually, allowing you to ingest data from LinkedIn Marketing 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 LinkedIn Marketing endpoints. Each template is designed specifically for the corresponding LinkedIn Marketing 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 My Organization Info

    Fetch My Organization Info

    • Enter the Organization ID in the Organization ID field. This is the unique identifier for a specific organization in your LinkedIn account. The default value is "7957867". You can obtain Organization IDs from your LinkedIn account or by using other endpoints to search for organizations by vanity name or email domain.
    • The endpoint uses GET requests to https://api.linkedin.com/v2/organizations/{org_id} where {org_id} is the Organization ID you configured. The endpoint URL is automatically constructed based on your configuration.
    • The endpoint does not use pagination (iteration.type: static.url), so it will fetch a single organization record per execution. The response data path is $, which extracts the entire response object.
    • This endpoint uses the Organization Lookup API to find organizations that the authenticated user is an administrator of. Use other endpoints to search for organizations by vanity name or email domain.

    This endpoint retrieves information about a specific organization from your LinkedIn Marketing account. The endpoint requires OAuth2 authentication with an access token, which is handled automatically by your credential configuration. The access token is sent in the Authorization: Bearer {access_token} header for all API requests. The Organization ID identifies which organization to retrieve. The authenticated user must be an administrator of the organization to access its information. For detailed information about fetching organization information, see the LinkedIn Marketing API documentation.

    Fetch Organization By Email

    Fetch Organization By Email

    • Enter the Organization Email Domain in the Organization Email Domain field. This is the email domain associated with the organization you want to find. The default value is "nexla.com". This endpoint returns an array of organizations that match the specified email domain.
    • The endpoint uses GET requests to https://api.linkedin.com/v2/organizations?q=emailDomain&emailDomain={email_domain} where {email_domain} is the Organization Email Domain you configured. The endpoint URL is automatically constructed based on your configuration.
    • The endpoint does not use pagination (iteration.type: static.url), so it will fetch all matching organizations in a single request. The response data path is $.elements[*], which extracts all organization objects from the elements array in the API response.
    • This endpoint uses the Organization Lookup API to find organizations by Email Domain. Use other endpoints to search for organizations by vanity name.

    This endpoint retrieves a list of organizations that match the specified email domain from your LinkedIn Marketing account. The endpoint requires OAuth2 authentication with an access token, which is handled automatically by your credential configuration. The access token is sent in the Authorization: Bearer {access_token} header for all API requests. The email domain is used to search for matching organizations. For detailed information about fetching organizations by email domain, see the LinkedIn Marketing API documentation.

    Get Organization Share Statistics: Time Range

    Get Organization Share Statistics: Time Range

    • Enter the Organization ID in the Organization ID field. This is the unique identifier for a specific organization in your LinkedIn account. The default value is "7957867". You can obtain Organization IDs from your LinkedIn account or by using other endpoints to search for organizations.
    • Select the granularity of the statistics from the Granularity of the statistics pulldown menu. Available options are "DAY" or "MONTH". The default value is "DAY". This determines whether statistics are aggregated by day or by month.
    • Enter the start timestamp in the Start Timestamp (ms since epoch) field. This is the exclusive starting timestamp of when the query should begin. The timestamp must be in milliseconds since epoch format. You can also use Nexla macros like `{now}`, `{now-1}`, etc. The default value is `{now-1}`.
    • Enter the end timestamp in the End Timestamp (ms since epoch) field. This is the inclusive ending timestamp of when the query should end. The timestamp must be in milliseconds since epoch format. You can also use Nexla macros like `{now}`, `{now-1}`, etc. The default value is `{now}`.
    • The endpoint uses GET requests to https://api.linkedin.com/v2/organizationalEntityShareStatistics?q=organizationalEntity&organizationalEntity=urn:li:organization:{org_id}&timeIntervals.timeGranularityType={granularity}&timeIntervals.timeRange.start={start}&timeIntervals.timeRange.end={end} where {org_id}, {granularity}, {start}, and {end} are the values you configured. The endpoint URL is automatically constructed based on your configuration.
    • The endpoint does not use pagination (iteration.type: static.url), so it will fetch all statistics for the specified time range in a single request. The response data path is $.elements[*], which extracts all statistics objects from the elements array in the API response.
    • The date format is eeee with a time unit of dd (days), which is used for incremental data extraction based on record dates.

    This endpoint retrieves an organization's organic share statistics for a specified time range from your LinkedIn Marketing account. The endpoint requires OAuth2 authentication with an access token, which is handled automatically by your credential configuration. The access token is sent in the Authorization: Bearer {access_token} header for all API requests. The API returns aggregate share stats within all of the days or months in between the selected date range based on the specified granularity. The timestamps must be in milliseconds since epoch format, and you can use Nexla macros like `{now}` or `{now-1}` for dynamic date ranges. For detailed information about fetching share statistics, see the LinkedIn Marketing API documentation.

    Get Organization Page Statistics: Time Range

    Get Organization Page Statistics: Time Range

    • Enter the Organization ID in the Organization ID field. This is the unique identifier for a specific organization in your LinkedIn account. The default value is "7957867". You can obtain Organization IDs from your LinkedIn account or by using other endpoints to search for organizations.
    • Select the granularity of the statistics from the Granularity of the statistics pulldown menu. Available options are "DAY" or "MONTH". The default value is "DAY". This determines whether statistics are aggregated by day or by month.
    • Enter the start timestamp in the Start Timestamp (ms since epoch) field. This is the exclusive starting timestamp of when the query should begin. The timestamp must be in milliseconds since epoch format. You can also use Nexla macros like `{now}`, `{now-1}`, etc. The default value is `{now-1}`.
    • Enter the end timestamp in the End Timestamp (ms since epoch) field. This is the inclusive ending timestamp of when the query should end. The timestamp must be in milliseconds since epoch format. You can also use Nexla macros like `{now}`, `{now-1}`, etc. The default value is `{now}`.
    • The endpoint uses GET requests to https://api.linkedin.com/v2/organizationPageStatistics?q=organization&organization=urn:li:organization:{org_id}&timeIntervals.timeGranularityType={granularity}&timeIntervals.timeRange.start={start}&timeIntervals.timeRange.end={end} where {org_id}, {granularity}, {start}, and {end} are the values you configured. The endpoint URL is automatically constructed based on your configuration.
    • The endpoint does not use pagination (iteration.type: static.url), so it will fetch all statistics for the specified time range in a single request. The response data path is $.elements[*], which extracts all statistics objects from the elements array in the API response.
    • The date format is eeee with a time unit of dd (days), which is used for incremental data extraction based on record dates.

    This endpoint retrieves statistics on views and clicks of an organization's page for a specified time range from your LinkedIn Marketing account. The endpoint requires OAuth2 authentication with an access token, which is handled automatically by your credential configuration. The access token is sent in the Authorization: Bearer {access_token} header for all API requests. The API returns aggregate stats within all of the days or months in between the selected date range based on the specified granularity. The timestamps must be in milliseconds since epoch format, and you can use Nexla macros like `{now}` or `{now-1}` for dynamic date ranges. For detailed information about fetching page statistics, see the LinkedIn Marketing API documentation.

Configure Manually​

LinkedIn Marketing data sources can be manually configured to ingest data from any valid LinkedIn Marketing 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 LinkedIn Marketing sources, such as sources that use custom query parameters, different HTTP methods, or custom data transformations.

Content Format​

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

API Endpoint URL​

  1. Enter the URL of the LinkedIn Marketing 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. LinkedIn Marketing API endpoints typically follow the pattern https://api.linkedin.com/v2/{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 OAuth2 authentication with an access token, which is handled automatically by your credential configuration. The access token is sent in the Authorization: Bearer {access_token} header for all API requests. For detailed information about LinkedIn Marketing API endpoints, authentication, and available APIs, see the LinkedIn Marketing API documentation.