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] add conversion data to the hubspot__source table properties #71

Open
2 of 4 tasks
moreaupascal56 opened this issue Jun 17, 2022 · 3 comments
Open
2 of 4 tasks
Labels
type:enhancement New functionality or enhancement

Comments

@moreaupascal56
Copy link
Contributor

moreaupascal56 commented Jun 17, 2022

Is there an existing feature request for this?

  • I have searched the existing issues

Describe the Feature

Hi there!

I find useful to have the Conversion Information of a contact in a the hubspot__contact table (from dbt_hubspot package), these are the informations mentioned here (section Conversion Information):

  • First conversion date
  • First conversion
  • etc

I did not find any of this data in the tables created by the hubspot transform package, so for now I'm using directly the table contact_form_submission imported by Fivetran. (with an aggregation data is good)

Maybe I did not search enough and this is already somewhere 🤔
Thx and Have a great day!

Describe alternatives you've considered

Continue using directly the table contact_form_submission

Are you interested in contributing this feature?

  • Yes.
  • Yes, but I will need assistance and will schedule time during your office hours for guidance.
  • No.

Anything else?

I just set up this dbt hubspot source package and it's really well explained, liked it ! :)

@fivetran-joemarkiewicz
Copy link
Contributor

Hi @moreaupascal56 thanks so much for opening this feature request! I can see the addition of the conversion metrics as very beneficial to the end models.

I see you are interested in opening a PR. If so, I would be more than happy to help with any questions you may have 😄. Once you open a PR I will be happy to prioritize review. If you don't end up opening a PR, I can plan to scope this out for a future sprint.

@moreaupascal56
Copy link
Contributor Author

Hey, just some infos :)
I may be able to work on this but I don't know when, I've done some specific workaround for my use case for now, but I still think it would be better here so I'd love to come back on this when some time will free up.

@fivetran-joemarkiewicz
Copy link
Contributor

Hi @moreaupascal56 that sounds great! We will keep this feature open and feel free to come back when you have time available.

We really appreciate your continue contributions to this code base 😄. Let me know if you have any questions or need any support.

@fivetran-sheringuyen fivetran-sheringuyen added type:enhancement New functionality or enhancement and removed enhancement labels Dec 22, 2022
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

3 participants