About Openflow Connector for LinkedIn Ads¶

Note

The connector is subject to the Connector Terms.

This topic describes the basic concepts, workflow, and limitations of Openflow Connector for LinkedIn Ads.

The Openflow Connector for LinkedIn Ads enables you to ingest LinkedIn Ads metrics into Snowflake. This connector uses the Reporting API to fetch data. The connector persists data in a table dedicated to a given report. Each report can be configured to contain metrics, pivots, and facets chosen by the user. The connector creates the destination table in the database and the schema provided in the configuration.

Workflow¶

  1. A LinkedIn Ads user obtains credentials required to connect to LinkedIn Ads API.

  2. A Snowflake account administrator performs the following tasks:

    1. Downloads and imports the connector definition into the Snowflake Openflow canvas.

    2. Configures the connector with the required parameters.

    3. Runs the connector. The following happens when the connector is run in Openflow:

      1. Retrieves the data based on the specified configuration.

        If the Time Granularity parameter is set to DAILY, then the connector downloads only the data for a calculated timeframe. In other cases, the connector downloads all the data from the start date to the current time.

      2. Creates a temporary table and inserts the downloaded data into it.

      3. Recreates or updates the destination table to reflect the schema of data from LinkedIn Ads. If you change the schema, the connector drops the destination table and recreates it with a new schema. If DAILY time granularity is chosen in the Time Granularity parameter, then outdated data is deleted from the destination table.

      4. Inserts the data into the destination table with an additional insertion timestamp.

      5. Drops the temporary table.

Limitations¶

  • All metrics of type BigDecimal are saved as Strings. Conversion functions allow you to convert values manually to numeric types with chosen scale and precision.

  • Some metrics and pivots return values that are IDs. The connector does not use the URN resolution.