Set up the Openflow Connector for LinkedIn Ads¶

Prerequisites¶

1. Ensure that you have reviewed About Openflow Connector for LinkedIn Ads.

2. Ensure that you have set up Openflow.

Get the credentials¶

1. As a LinkedIn Ads user, perform the following tasks:

   1. Optional: If you don’t have an ad account to run and manage campaigns, create one.

   2. Ensure that the user account has at least a VIEWER role on the ad account.

   3. Use the user account to apply for Advertising API access. For more information, see the Microsoft quick start.

   4. Obtain a refresh token. Use 3-legged oAuth and the r_ads_reporting scope.

   5. Obtain the client ID, client secret from the LinkedIn Developer Portal. These credentials are available in the in the Auth tab in App Details.

Set up Snowflake account¶

As a Snowflake account administrator, perform the following tasks:

1. Create a new role or use an existing role.

2. Create a new Snowflake service user with the type as SERVICE.

3. Grant the Snowflake service user the role you created in the previous steps.

4. Configure with key-pair auth for the Snowflake SERVICE user from step 2.

5. Snowflake strongly recommends this step. Configure a secrets manager supported by Openflow, for example, AWS, Azure, and Hashicorp, and store the public and private keys in the secret store.

   Note

   If for any reason, you do not wish to use a secrets manager, then you are responsible for safeguarding the public key and private key files used for key-pair authentication according to the security policies of your organization.

6. Once the secrets manager is configured, determine how you will authenticate to it. On AWS, it’s recommended that you the EC2 instance role associated with Openflow as this way no other secrets have to be persisted.

7. In Openflow, configure a Parameter Provider associated with this Secrets Manager, from the hamburger menu in the upper right. Navigate to Controller Settings » Parameter Provider and then fetch your parameter values.

8. At this point all credentials can be referenced with the associated parameter paths and no sensitive values need to be persisted within Openflow.

9. If any other Snowflake users require access to the raw ingested documents and tables ingested by the connector (for example, for custom processing in Snowflake), then grant those users the role created in step 1.

10. Create a database and schema in Snowflake for the connector to store ingested data. Grant required Database privileges to the role created in the first step. Substitute the role placeholder with the actual value and use the following sql commands:

    CREATE DATABASE linkedin_destination_db;
    CREATE SCHEMA linkedin_destination_db.linkedin_destination_schema;
    GRANT USAGE ON DATABASE linkedin_destination_db TO ROLE <linkedin_connector_role>;
    GRANT USAGE ON SCHEMA linkedin_destination_db.linkedin_destination_schema TO ROLE <linkedin_connector_role>;
    GRANT CREATE TABLE ON SCHEMA linkedin_destination_db.linkedin_destination_schema TO ROLE <linkedin_connector_role>;
    

    Copy

11. Create a warehouse that will be used by the connector or use an existing one. Start with the smallest warehouse size, then experiment with size depending on the number of tables being replicated, and the amount of data transferred. Large table numbers typically scale better with multi-cluster warehouses, rather than larger warehouse sizes.

12. Ensure that the user with role used by the connector has the required privileges to use the warehouse. If that’s not the case then grant the required privileges to the role.

    CREATE WAREHOUSE linkedin_connector_warehouse WITH WAREHOUSE_SIZE = 'X-Small';
    GRANT USAGE ON WAREHOUSE linkedin_connector_warehouse TO ROLE <linkedin_connector_role>;
    

    Copy

Set up the connector¶

As a data engineer, perform the following tasks to install and configure the connector:

Run the flow¶

1. Right-click on the plane and select Enable all Controller Services.

2. Right-click on the imported process group and select Start.

   The connector starts the data ingestion.