feature/add-action-result

CHANGELOG.md

@@ -1,3 +1,16 @@
+# dbt_marketo_source v0.12.0
+[PR #38](https://github.com/fivetran/dbt_marketo_source/pull/38) includes the following updates:
+
+## Feature
+- Added the `action_result` field to the `stg_marketo__activity_send_email` model to capture the result of email actions and enable filtering in downstream models.
+
+## Documentation update
+- Update dbt docs with `action_result`
+
+## Under the hood
+- Updated seed data with `action_result`
+- Updated macro `marketo_activity_send_email_data` with `action_result`
+
 # dbt_marketo_source v0.11.0
 [PR #35](https://github.com/fivetran/dbt_marketo_source/pull/35) includes the following updates:
 

README.md

@@ -43,7 +43,7 @@ If you  are **not** using the [Marketo transformation package](https://github.co
 ```yml
 packages:
   - package: fivetran/marketo_source
-    version: [">=0.11.0", "<0.12.0"]
+    version: [">=0.12.0", "<0.13.0"]
 ```
 
 ### Step 3: Define database and schema variables

dbt_project.yml

@@ -1,5 +1,5 @@
 name: 'marketo_source'
-version: '0.11.0'
+version: '0.12.0'
 config-version: 2
 require-dbt-version: [">=1.3.0", "<2.0.0"]
 models:

integration_tests/dbt_project.yml

@@ -1,5 +1,5 @@
 name: 'marketo_source_integration_tests'
-version: '0.11.0'
+version: '0.12.0'
 profile: 'integration_tests'
 config-version: 2
 vars:

macros/get_activity_send_email_columns.sql

@@ -2,6 +2,7 @@
 
 {% set columns = [
     {"name": "_fivetran_synced", "datatype": dbt.type_timestamp()},
+    {"name": "action_result", "datatype": dbt.type_string()},
     {"name": "activity_date", "datatype": dbt.type_timestamp()},
     {"name": "activity_type_id", "datatype": dbt.type_int()},
     {"name": "campaign_id", "datatype": dbt.type_int()},