[Draft] Passthrough Variable

[DylanBaker]

Are you a current Fivetran customer?

Dylan, Fivetran

What change(s) does this PR introduce?

Allows additional metrics to be defined and added as pass-through metrics.

Does this PR introduce a breaking change?

• 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

• Yes, closes this issue
• No

How did you test the PR changes?

• CircleCi
• Other (please provide additional testing details below)

[fivetran-joemarkiewicz]

@DylanBaker I made an update to the passthrough variable that I would like to get your eyes on. It seemed that within the stg_pinterest_ads__pin_promotion_report model there may be instances where users would want to pass more than just a single field through (for example we have a default field coalesce(clickthrough_1,0) + coalesce(clickthrough_2,0) as clicks and I assume users may want to do something similar).

As such, I added a bit more configurability to the passthrough variable so users my do just that. Does this update align with your understanding of how users use their Pinterest data? Or would there never be an instance when a user would want this and we should just stick with single field passthrough variable ability?

[DylanBaker]

@fivetran-joemarkiewicz Given that they could always do the transformation at the other end of the package (given we just sum) I'd be inclined to leave it with the more simple implementation. They can always grab the ad adapter and add or divide things up at that point. Feels like the new syntax, while powerful, likely makes the implementation for the user a bit more complicated?

[fivetran-joemarkiewicz]

Yeah that makes sense that the user could just grab the ad adapter and add or divide from there on their own. Thanks for giving a glance at this. I'll revert these changes to keep with simplicity and not over complicating the package.

Thanks @DylanBaker!