Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature] Incorporate campaign_placement_report into campaign end model #22

Open
1 of 4 tasks
fivetran-jamie opened this issue Jan 29, 2025 · 0 comments
Open
1 of 4 tasks
Labels
type:enhancement New functionality or enhancement

Comments

@fivetran-jamie
Copy link
Contributor

Is there an existing feature request for this?

  • I have searched the existing issues

Describe the Feature

The connector is currently being updated to include campaign_id in the campaign_placement_report source table, which means we can easily join this with other campaign data here in the package. The placement identifies where the ad is placed -- at the top of the search page, elsewhere in the search page(s), in product or add-to-cart pages, or in Amazon Business? This could help guide marketers on where to best place campaign ads.

How would you implement this feature?

I suggest bringing this data into the amazon_ads__campaign_report model. We could also then aggregate to the account and portfolio level as well, but maybe we start with campaign first.

According to these docs, there are 4 possible placement classifications (though one is in Beta). To not mess up the grain of the end model(s), I suggest we add metrics for each classification. So something like

{% for placement in ['list', 'of', 'placement', 'values'] %}
, sum(case when placement = '{{ placement }}' then <metric> else 0 end as <metric>_{{ placement }}
{% endfor %}

This would add quite a few new columns however, so please feel free to push back on anything that doesn't seem valuable

Describe alternatives you've considered

Don't include placements!

Are you interested in contributing this feature?

  • Yes.
  • Yes, but I will need assistance.
  • No.

Anything else?

No response

@fivetran-jamie fivetran-jamie added the type:enhancement New functionality or enhancement label Jan 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:enhancement New functionality or enhancement
Projects
None yet
Development

No branches or pull requests

1 participant