Skip to main content

Hey team.

 

Only part of the users in an amplitude cohort is being imported to hubspot.

Any idea why ?

Thanks for reaching out here @karthika88. My instinct is to try to reset the set up. Here are the details in our developer center. Let me know if that works and if not, I can get someone more savvy to dig deeper. 

  1. In Amplitude, open the cohort you want to sync.
  2. Click Sync and choose HubSpot.
  3. Specify the HubSpot account you want to send the cohort to.
  4. Set the sync cadence.
  5. Save your work.

Thank you for the feedback.

I did that, but only part of our data from a cohort synced into hubspot.

Could we get someone to hop on a call with us on Tuesday . Here is a link to my calendar https://calendly.com/karthika-8/gander-intro-calls?


Thanks for this note. We’ve forwarded your info to our support team who will get back to you.


Also, it looks like we have hit the limit on the number of syncs allowed (which is 5). I deleted some of the old hourly syncs, but I am not able to create a new one.

It is frustrating that there are so many issues with this integration and we are not getting any support from the team


Attaching the email here  --

 

A cohort sync has failed for cohort gander_active_users _hubspot (9xnssrn) for project Gander (438238). Scheduled syncs for this cohort have been disabled. If you continue to have issues, please reach out to us.
We have disabled your hourly sync. If you would like to sync this cohort again, set up a schedule on the cohort page here!

- The Amplitude Team

 


@karthika88 Do you also have some example User Ids that are not in Hubspot can you send me those values? We cannot see your Hubspot instance at all so if you can share those details that would be helpful! Feel free to proceed over email.


yes, the email ids that did not sync were 'admin@thirteenlune.com', 'customerservice@blackopalbeauty.com'. I managed to add them via api but could you please let me know why the sync failed for these two ?


@karthika88 We’ve sent this to our Engineering team to look into this further.


Reply