Skip to main content

We are using the Python SDK for revenue tracking purposes. We are currently tracking default revenue event provided by Amplitude in two of our environments : dev and staging. The events are sent by our backend application running in AWS Lambda execution environment.

The problem we are facing is that in each environment, the first few revenue events were logged in amplitude, sporadically, but successfully. Later, the revenue tracking just stops working; no new events are logged in amplitude. They don’t show up in User look-up (PFA 3rd image), and neither does the invocation count of the revenue event increase in the Event detail page (PFA 2nd image). Though sometimes, the invocation is shown in Ingestion Debugger under Sources as a successful request. We are passing all the required attributes, doing everything suggested in the SDK docs, and have added info logs to ensure that the events are successfully sent from our end.

Any help / guidance would be highly appreciated.

Revenue event provided by Amplitude accessed from Tracking Plan
Only 4 invocations were logged as can be seen in the “30 Day Volume” field. Rest of the event invocations are ignored
New revenue events not tracked in user look up tab

 

We are facing the same issue. Did you figure out what the problem was @Harris Irfan? Many thanks


Also seeing a similar issue. @Jose Lis were you able to find a solution?


Hi @Tyler. We were able to solve it. I am copying the reply we got from Amplitude support when we explained our situation. Not sure if this would apply to the problem you are facing or could give you any hint...

----

I wanted to share some information with you that I received from our Engineering team. They took a look at your instrumentation and provided some suggestions that might help you ingest more revenue events.
 
According to them, the flush method in python returns a list of futures. It would be best to wait for the future to return before shutting down the client. Additionally, creating new clients for every send event should not be necessary as the client is generally reusable.


Thanks @Jose Lis. The futures was definitely not mentioned at all in the docs. Appreciate the quick reply.


Reply