Is there an existing feature request for this?
Describe the Feature
Create the ability to create custom conversion columns that persist in the downstream models. The columns would be defined based on the action_type field in the stg_facebook_ads__basic_ad_actions.
Example
Custom Conversion of lead
sql definition
Select
action_type,
sum(conversions) as leads
FROM `inq-warehouse.analytics.stg_facebook_ads__basic_ad_actions`
where action_type = 'lead'
group by 1
How would you implement this feature?
The implementation could be similar to the other vars: variable setup in the package. Custom leads are defined by vars with name, alias, and sql criteria.
Describe alternatives you've considered
custom sql models
Are you interested in contributing this feature?
Anything else?
discussion with Jamie Rodriguez from Fivetran in the dbt slack
Is there an existing feature request for this?
Describe the Feature
Create the ability to create custom conversion columns that persist in the downstream models. The columns would be defined based on the action_type field in the
stg_facebook_ads__basic_ad_actions.Example
Custom Conversion of
leadsql definition
How would you implement this feature?
The implementation could be similar to the other vars: variable setup in the package. Custom leads are defined by vars with name, alias, and sql criteria.
Describe alternatives you've considered
custom sql models
Are you interested in contributing this feature?
Anything else?
discussion with Jamie Rodriguez from Fivetran in the dbt slack