dbt_linkedin 0.5.0

PR #21 includes the following changes:

🚨 Breaking Changes 🚨

• ALL models and ALL variables now have the prefix linkedin_ads_*. They previously were prepended with linkedin_*. This includes the required schema and database variables. We made this change to better discern between Linkedin Ads and Linkedin Pages.
• The following models have been renamed:
  • linkedin__account_ad_report -> linkedin_ads__account_report
  • linkedin__campaign_ad_report -> linkedin_ads__campaign_report
  • linkedin__campaign_group_ad_report -> linkedin_ads__campaign_group_report
• The linkedin__ad_adapter model has been renamed and refactored into two separate models:
  • linkedin_ads__url_report: Each record in this table represents the daily performance at the url level.
  • linkedin_ads__creative_report: Each record in this table represents the daily performance at the creative level.
• The declaration of passthrough variables within your root dbt_project.yml has changed. To allow for more flexibility and better tracking of passthrough columns, you will now want to define passthrough columns in the following format:

vars:
  linkedin_ads__campaign_passthrough_metrics: # this will pass through fields to the account, campaign, and campaign group report models. it pulls from `ad_analytics_by_campaign`
    - name: "my_field_to_include" # Required: Name of the field within the source.
      alias: "field_alias" # Optional: If you wish to alias the field within the staging model.
  linkedin_ads__creative_passthrough_metrics: # this will pass through fields to the creative and url report models.  it pulls from `ad_analytics_by_creative`
    - name: "my_field_to_include"
      alias: "field_alias"

• Staging models are now by default written within a schema titled (<target_schema> + _linkedin_ads_source) in your destination. Previously, this was titled (<target_schema> + _stg_linkedin).

🎉 Feature Enhancements 🎉

• README updates for easier navigation and use of the package.
• Addition of identifier variables for each of the source tables to allow for further flexibility in source table direction within the dbt project.
• Addition of new columns to _report models.
• More complete table and column documentation.
• More robust schema tests.