Depends how you doing it but, you could add each new transaction, as a new document.

Example of Path:

in_app / uid / list_transaction / addDoc

Hi ​@Brendan Rice, does the suggestion Ben provided above help at all? I’m not aware of a change to the Firestore extension to resolve this particular challenge, but we haven’t heard of developers exceeding the 1mb size limit either.

​@chris_perriam I don’t think so because I’m talking about the firebase extension for revenuecat. As far as I can tell it just makes a collection for customers and ever customer gets exactly 1 record which stores all of their transactions. I don’t think there is actually an option to tell the extension to breakout each customer’s transaction into a separate records? 

You can try few more things:

• using the webhook instead of the extension
• onUpdate on the document delete some data and add it to a collection etc

Not sure if it helps

​@Brendan Rice I’ve checked with the team and can confirm your understanding is correct on this. We don’t currently have a workaround to the 1mb limitation.