@dan_george Thx for response. And I sort of agree:) We get significant data signals for easily millions of people/day - and while some signals are more significant than others, it's still going to be somewhat of a balancing game to determine what data gets sent, and how often. Depending on how strongly we rely on AS for martketing activation with various vendors, we'll want as real-time as we can get, which means in some cases sending a particular visitor's data (or updated data) multiple times a day. As an example: Once for a particular scoring change from batch scoring change because of yesterday's activity, then another for some kind of offline interaction in the morning, then another because of a non-online purchase in the afternoon. I don't think the current throttle of 100 events/sec will be limiting in any way for us in the short term. But just wanted to make sure you guys were able to scale relatively quickly if all of a sudden you had 5,10, 20, or 40 more clients with significant volume loading millions of events/day. (based the principle that for every instance of something you hear about, there's likely 8 or 10 instance you don't).
... View more