fivetran / fivetran/dbt_google_ads

Retain Campaign History for Joining to CRM Data

Open
#45 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
No language data
Stars
27
Forks
33
PR merge metrics
No merged PRs in 30d

Description

### Is there an existing feature request for this?

- [X] I have searched the existing issues

### Describe the Feature

In some of the models such as the campaign_report, the CTEs are filtered for `is_most_recent_record = True`. This means that each campaign name reflects the most up-to-date name, which may not match the name on a lead, contact, etc from a CRM like Salesforce. This makes it more difficult to calculate metrics like Cost per X, where X is some event that takes place in the Sales funnel.

Is it possible to update models to not filter for the most recent record, so we can get a full history of campaign performance?

### Describe alternatives you've considered

I've tried copy/pasting the code from this package into custom models to build reports that can relate spend to conversion events, but that seems duplicative. If we can do it all in this package, that would be much better =)

### Are you interested in contributing this feature?

- [X] Yes.
- [ ] Yes, but I will need assistance and will schedule time during your [office hours](https://calendly.com/fivetran-solutions-team/fivetran-solutions-team-office-hours) for guidance.
- [ ] No.

### Anything else?

N/A

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by inspecting the campaign_report model and its CTEs, focusing on filters for is_most_recent_record = True. Trace which related models also apply that filter and how campaign names join to CRM events. Done means campaign performance retains historical campaign names and supports the requested funnel metrics without requiring duplicated custom models.

Written by the indexing model from the issue text.

Assessment

Tech stack
sql
Domain
analytics, data
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.