Merge pull request #1 from fivetran/jr_working

Jr working

.circleci/config.yml

@@ -16,12 +16,24 @@ jobs:
       - run:
           name: "Setup dbt"
           command: |
+            sudo apt install libsasl2-dev
             python3 -m venv venv
             . venv/bin/activate
             pip install --upgrade pip setuptools
             pip install -r integration_tests/requirements.txt
             mkdir -p ~/.dbt
             cp integration_tests/ci/sample.profiles.yml ~/.dbt/profiles.yml
+      # - run:
+      #     name: "Run Tests - Spark"
+      #     command: |
+      #       . venv/bin/activate
+      #       echo `pwd`
+      #       cd integration_tests
+      #       dbt deps
+      #       dbt seed --target spark --full-refresh
+      #       dbt run --target spark --full-refresh
+      #       dbt test --target spark
+      #     no_output_timeout: 10m
       - run:
           name: "Run Tests - Redshift"
           command: |

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,62 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: BUG - [your bug title here]
+labels: bug
+assignees: ''
+
+---
+
+**Are you a current Fivetran customer?** 
+<!--- Please tell us your name, title and company -->
+
+
+**Describe the bug**
+<!--- A clear and concise description of what the bug is. -->
+
+**Steps to reproduce**
+1. Go to '...'
+2. Click on '....'
+3. Scroll down to '....'
+4. See error
+
+**Expected behavior**
+<!--- A clear and concise description of what you expected to happen. -->
+
+**Project variables configuration**
+<!--- Copy and paste the contents of your `dbt_project.yml` file below. -->
+```yml
+copy dbt_project.yml here
+```
+
+**Package Version**
+<!---Copy and paste the contents of your `packages.yml` file below.-->
+```yml
+copy packages.yml here
+```
+
+**Warehouse**
+<!--- Which warehouse you are running dbt and this package against. -->
+<!--- To check a warehouse remove the space and insert an x in the box (eg. [x] Bigquery). --> 
+- [ ] BigQuery
+- [ ] Redshift
+- [ ] Snowflake
+- [ ] Postgres
+- [ ] Databricks
+- [ ] Other (provide details below)
+
+**Additional context**
+<!--- Add any other context about the problem here.  --> 
+
+**Screenshots**
+<!--- If applicable, add screenshots to help explain your problem.  -->
+
+**Please indicate the level of urgency** 
+<!--- Is this impacting your reporting of a critical dashboard? Are you just testing this for the first time? Provide us context so that we can prioritize accordingly. -->
+
+**Are you interested in contributing to this package?** 
+<!--- Our packages are all open-source and we welcome contributions from the community! Are you interested in helping us fix this bug? -->
+- [ ] Yes, I can do this and open a PR for your review.
+- [ ] Possibly, but I'm not quite sure how to do this. I'd be happy to do a live coding session with someone to get this fixed. 
+- [ ] No, I'd prefer if someone else fixed this.  I don't have the time and/or don't know what the root cause of the problem is.
+

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,32 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+title: FEATURE - [your feature request title here]
+labels: enhancement
+assignees: ''
+
+---
+
+**Are you a Fivetran customer?** 
+<!--- Please tell us your name, title and company -->
+
+**Is your feature request related to a problem? Please describe.**
+<!--- A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] --> 
+
+**Describe the solution you'd like**
+<!--- A clear and concise description of what you want to happen. --> 
+
+**Describe alternatives you've considered**
+<!--- A clear and concise description of any alternative solutions or features you've considered. --> 
+
+**Additional context**
+<!--- Add any other context or screenshots about the feature request here. -->
+
+**Please indicate the level of urgency and business impact of this request** 
+<!--- Is this impacting your reporting of a critical dashboard? What problem would implementing this feature request solve? Provide us context so that we can prioritize accordingly. -->
+
+**Are you interested in contributing to this package?** 
+<!--- Our packages are all open-source and we welcome contributions from the community! Are you interested in helping us implement this feature? -->
+- [ ] Yes, I can do this and open a PR for your review.
+- [ ] Possibly, but I'm not quite sure how to do this. I'd be happy to do a live coding session with someone to get this work implemented. 
+- [ ] No, I'd prefer if someone else did this.  I don't have the time and/or don't know how to incorporate the changes necessary.

.github/ISSUE_TEMPLATE/question.md

@@ -0,0 +1,20 @@
+---
+name: Question
+about: Confused about how to use the package? Ask us a question
+title: QUESTION - [your question title here]
+labels: question
+assignees: ''
+
+---
+
+**Are you a Fivetran customer?** 
+<!--- Please tell us your name, title and company -->
+
+**Your Question**
+<!--- What is the question you would like to ask us about the package --> 
+
+**Additional context**
+<!--- Add any other context or screenshots about the feature request here. -->
+
+**Please indicate the level of urgency and business impact of this request** 
+<!--- Is this question blocking you from completing urgent work? Give us more context to help us prioritize this question. -->

.github/pull_request_template.md

@@ -0,0 +1,40 @@
+**Are you a current Fivetran customer?** 
+<!--- Please tell us your name, title and company -->
+
+**What change(s) does this PR introduce?** 
+<!--- Describe what changes your PR introduces to the package -->
+
+**Does this PR introduce a breaking change?**
+<!--- Does this PR introduce changes that -->
+<!--- Mark yes or no (eg. [x] Yes). If yes, link the issue. -->
+- [ ] Yes (please provide breaking change details below.)
+- [ ] No  (please provide explanation how the change is non breaking below.)
+
+**Is this PR in response to a previously created Issue**
+<!--- If an Issue was created it is helpful to track the progress by linking it in the PR. -->
+<!--- Mark yes or no (eg. [x] Yes). If yes, link the issue. -->
+- [ ] Yes, Issue [link issue number here]
+- [ ] No 
+
+**How did you test the PR changes?** 
+<!--- Proof of testing is required in order for the PR to be approved. -->
+<!--- To check a box, remove the space and insert an x in the box (eg. [x] CircleCi). --> 
+- [ ] CircleCi <!--- CircleCi testing is only applicable to Fivetran employees. --> 
+- [ ] Other (please provide additional testing details below)
+
+**Select which warehouse(s) were used to test the PR**
+<!--- To check a warehouse remove the space and insert an x in the box (eg. [x] Bigquery). --> 
+- [ ] BigQuery
+- [ ] Redshift
+- [ ] Snowflake
+- [ ] Postgres
+- [ ] Databricks
+- [ ] Other (provide details below)
+
+**Provide an emoji that best describes your current mood**
+<!--- For a complete list of markdown compatible emojis check our this git repo (https://gist.github.com/rxaviers/7360908)  --> 
+:dancer:
+
+**Feedback**
+
+We are so excited you decided to contribute to the Fivetran community dbt package! We continue to work to improve the packages and would greatly appreciate your [feedback](https://www.surveymonkey.com/r/DQ7K7WW) on our existing dbt packages or what you'd like to see next.

dbt_project.yml

@@ -12,15 +12,47 @@ vars:
     integration: "{{ ref( 'stg_klaviyo__integration') }}" 
     person: "{{ ref( 'stg_klaviyo__person') }}" 
     metric: "{{ ref( 'stg_klaviyo__metric') }}" 
-
+
+    klaviyo__email_attribution_lookback: 120 # in hours - 5 days -> https://help.klaviyo.com/hc/en-us/articles/115005248128#conversion-tracking1
+    klaviyo__sms_attribution_lookback: 24 # in hours -> https://help.klaviyo.com/hc/en-us/articles/115005248128#sms-conversion-tracking7
+
+    klaviyo__eligible_attribution_events: # default in klaviyo -> https://help.klaviyo.com/hc/en-us/articles/115005248128 
+      - 'opened email'
+      - 'clicked email'
+      - 'clicked sms'
+
+    klaviyo__count_metrics: 
+      - 'Active on Site' # default API metrics
+      - 'Viewed Product'
+      - 'Ordered Product' # some default Shopify metrics
+      - 'Placed Order' # there are X 'ordered product' events for every `placed order` purchase event of X products
+      - 'Refunded Order' # note: klaviyo only tracks FULL refunds (not partial)
+      - 'Received Email' # default email and sms conversion metrics in Klaviyo
+      - 'Clicked Email'
+      - 'Opened Email'
+      - 'Marked Email as Spam'
+      - 'Unsubscribed'
+      - 'Received SMS'
+      - 'Clicked SMS'
+      - 'Sent SMS'
+      - 'Unsubscribed from SMS'
+
+    klaviyo__sum_revenue_metrics:
+      - 'Refunded Order'
+      - 'Placed Order'
+      - 'Ordered Product'
+      - 'checkout started'
+      - 'cancelled order'
+
   klaviyo_source:
     klaviyo__event_pass_through_columns: []
     klaviyo__person_pass_through_columns: []
+
 
-# models: 
-#   klaviyo_source:
-#     tmp:
-#       +materialized: view
-#     +materialized: table
-
-profile: klaviyo
+models: 
+  klaviyo:
+    intermediate:
+      +schema: int_klaviyo
+      +materialized: view # note: int_klaviyo__event_attribution is configured as incremental
+    +materialized: table # note: klaviyo__events is configured as incremental
+    +schema: klaviyo