Hi @pindelicato ,
Thanks for writing in! Denis here again, happy to help and provide some insight!
So I understand that the issue is Amplitude gets two events ingested, one for Loaded a Page and one for Viewed URL_Slug Page which created a hundred of event types. In this scenario, the best fix would be to block and delete these event types so you can get below the limit again. Alternatively, you could create a new project and start using that instead. You could export the data from the old project and import it using the HTTP Batch API to the new project.
It would seem the events are being sent to Amplitude from the code. I understand you have segment, correct? Are these events ingested from Segment? Or is it from the Amplitude SDK? Regardless, it would seem this is an implementation issue so you would need to look at these events and see what gets triggered to log two different ones of these events.
With regards to stopping this, the only way to do this is to look at the implementation and look into the part triggering both events in order to stop it from generating a whole new event each time there is a different URL. It would seem some code somewhere or some implementation logic is sending the slug as a separate event, as we know, and this is not ideal. I would instead look into the part of Viewed ___ Page and instead make this an event property such as Viewed_Page=somesite.com , for example. rather than a whole separate event.
Can we kill the "Viewed ____ Page" calls (historically and going forward)?
You can block them but it is specific to each, so once a new URL comes along, it will be ingested. I would look at the implementation and see the root cause of the double sending of events. I would spend time with your developers to see where the kink in the code is. If you cannot find a genuine reason, please PM Me your Org ID and Project ID along with a chart. Thank you!
Kind Regards,
Denis
