Drew
Product Manager, Marketing Analytics at Fivetran
- Total activity 736
- Last activity
- Member since
- Following 0 users
- Followed by 3 users
- Votes 1
- Subscriptions 341
Comments
Recent activity by Drew-
Official comment Hi Divya, Drew from the Product Team here! We have LinkedIn demographics data planned for our current quarter. I'll update the status here to Planned. Stay tuned for updates.
-
Official comment Hi Edwin, Drew from the Product Team here! Form data is definitely something we are looking into, but is not currently planned. We'll look to get it added to the roadmap for a future quarter.
-
Official comment Hi Jayanthan, Drew from Product Team here! I'm not entirely certain what information you are looking for. Is there any Google documentation you can point me to that would indicate the specific dime...
-
Official comment Hi Meera, Drew from the Product Team here! Thanks for this feature request! This is definitely a challenge with Iterable (and other event based platforms) that do not provide a primary key. Out of ...
-
Official comment Hi YuShih, Drew from the Product Team here! We currently don't provide the name of the campaign in campaign report tables because it goes against our principle of normalizing data. That said, campa...
-
Official comment Hi Tom, Drew from the Product Team here! Are you specifically asking for the `updated_at` field to become a primary key? This is a great request.I'll work on discussing this with the engineering te...
-
Official comment Sanoj Fonseka could you file a separate request? We are about a week from deploying this to production and will not be able to add your request to it.
-
Custom Objects support is now rolled out to all customers. You should see these tables available in your Hubspot connector schema tab.
-
Hi Stephen, Drew from the Product Team here! Thanks for making this suggestion, it's definitely something we'll look into for inclusion in a future quarter.
-
Hi Wei Wei, We've done some digging on our side and it appears that metrics tend to get calculated differently depending on the other metrics that are picked in a report (not an expected behavior)....