Why why why is this not a feature?
Picture this: we just built an entire integration with a partner for a client, that depends largely on shooting in custom event completions. So we did all our work scoping out event definitions, integration workflows, building on sandbox, testing completions and everything works swimmingly.
New scope item appears: importing historical event completions. Yeah, sure we can import those... oh wait, I can only import if I also create a new event along with it.
So now we have to either:
Delete the event definition, recreate it with the import of hundreds of thousands of events and just pray that the event gets the same name, basically importing all the historic event data before even testing the event completion API endpoint, potentially breaking all the event references. Whichever way I spin this, my workflow will always be: import all your legacy data first, thén start working with test/dev setups before you even know if you've finalized your event. That's the world upside down.
OR shove those same hundreds of thousands of event completions through the broker (again) so they can be pushed to HubSpot as event completions, which is the only other way to retroactively complete these events. Depending on the broker and volume of events, this can be quite resource intensive and costly.
Whatever I do, it's a lot of extra work that wasn't accounted for. Ugh I know we should've discovered this limitation beforehand, but HubSpot has a lot of these little "why doesn't it just work like that" drawbacks like this... honestly.
So: Please please please give us the option to first define an event and then import completions to that event independently!
... Afficher plus