We're evaluating PushWoosh and managed to get it going pretty quickly, 20 mins from start to finish which was nice.

One of the areas we are looking at is how PushWoosh handles device segmentation. Our servers can send out updates to user apps every few minutes, though it can often go hours and not send anything out to somebody.

The users we update are very dynamic, one minute we could have 2,000 users needing an update, five minutes later we could have a different 1,500 users needing an update, five minutes later it could be some combination of the first two updates and five minutes later it could be completely different again.

We actually have no difficulties doing this device segmentation ourselves, we've written all the code for this and we're comfortable it works quickly and well.

The PushWoosh documentation also talks about segmentation (http://docs.pushwoosh.com/docs/segmentation-tags-and-filters) and we want to make sure that our approach for device segmentation is acceptable. We are happy writing to the REST API and making sure that we don't have more than 1,000 devices in each of our REST API calls, but were nervous that this might not be the right way to do things.

Any advice or guidance welcomed.



asked 21 Dec '15, 17:58
rwillett's gravatar image


Be the first one to answer this question!
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here



Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:


question asked: 21 Dec '15, 17:58

question was seen: 2,481 times

last updated: 08 May, 10:11